Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o .

c o m

Cisco DCNM Fundamentals Guide, Release 6.x

July 2011

Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883

Text Part Number: OL-27525-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco DCNM Fundamentals Guide, Release 6.x 2010 Cisco Systems, Inc. All rights reserved.

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CONTENTS
New and Changed Information Preface
lxi lxix xxvii

Introduction to Cisco Data Center Network Manager

1

PART

Cisco Data Center Network Manager

1

CHAPTER

Cisco DCNM Fundamentals Overview 1-1 DCNM-SAN Server 1-1 DCNM-SAN Client 1-1 Device Manager 1-2 DCNM-SAN Web Client 1-2 Performance Manager 1-3 Authentication in DCNM-SAN Client 1-3 Cisco Traffic Analyzer 1-3 Network Monitoring 1-4 Performance Monitoring 1-4 Cisco DCNM Web Client
2-5

CHAPTER

Information About Cisco DCNM Web Client 2-5 Downloading Cisco DCNM-SAN Client 2-6 Launching DCNM Web Client 2-7 Adding a Security Exception 2-8 Cisco DCNM Web Client GUI 2-8 Navigating DCNM Web Client 2-10 Using DCNM Web Client with SSL 2-11 Creating a Local Certificate 2-11 Creating a Certificate Singing Request 2-12 Modifying DCNM Web Client to Use SSL 2-13 Viewing Hosts Information 2-14 Viewing Health Information 2-14 Viewing Accounting Information 2-14 Viewing Events Information 2-15 Viewing Syslog Information 2-15 Viewing Syslog Archives Information 2-15
Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

iii

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Viewing Performance Information 2-16 Viewing Switch CPU Information 2-17 Viewing Switch Memory Information 2-17 Viewing Switch Bandwidth and Errors Information 2-17 Viewing ISL Traffic and Errors Information 2-18 Viewing Performance Information on All the Ports 2-18 Viewing Performance Information on Host Ports 2-19 Viewing Performance Information on Storage Ports 2-19 Viewing Performance Information on Host Enclosures 2-19 Viewing Performance Information on Storage Enclosures 2-20 Viewing Performance Information on Port Groups 2-20 Viewing Performance Information for ISLs 2-21 Viewing Performance Information for NPV Links 2-21 Viewing Performance Information for Flows 2-22 Viewing Performance Information for Gigabit Ethernet and Ethernet Ports Viewing Other Statistics 2-23 Viewing Inventory Information 2-24 Viewing Inventory Information for VSANs 2-24 Viewing Inventory Information for Switches 2-25 Viewing License Information 2-25 Viewing Inventory Information for Modules 2-26 Viewing Inventory Information for All Ports on End Devices 2-26 Viewing Inventory Information for Host Ports on End Devices 2-26 Viewing Inventory Information for Storage Ports on End Devices 2-27 Viewing Detailed Information for ISLs 2-27 Viewing Inventory Information for NPV Links 2-28 Viewing Inventory Information for Regular Zones 2-28 Viewing Inventory Information for IVR Zones 2-28 Port Mapping 2-29 Viewing the Port Mapper 2-29 Viewing and Creating Custom Reports 2-30 Creating a Custom Report Template 2-31 Viewing a Custom Report Based on a Specific Template 2-33 Viewing a Custom Reports by a Specific User 2-33 Deleting a Report Template 2-33 Generating a Custom Report Based on a Template 2-34 Modifying a Custom Report Template 2-35 Deleting a Custom Report 2-35 Viewing Scheduled Jobs Based on a Report Template 2-35

2-23

Cisco DCNM Fundamentals Guide, Release 6.x

iv

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Administering DCNM Web Client 2-36 Starting, Restarting, and Stopping Services 2-37 Adding, Editing, and Removing Managed Fabrics 2-37 Discovering Devices Using Common LAN Discovery 2-38 Discovering a Cisco Device 2-39 Rediscovering a Device 2-40 Managing a LAN 2-41 Removing a LAN 2-41 Modifying a LAN 2-41 Viewing a vPC 2-42 Viewing vPC Inconsistencies 2-43 Resolving vPC Inconsistencies 2-43 Automatically Resolving vPC Inconsistencies 2-44 Viewing the vPC Utilization and Traffic Distribution 2-44 Searching a Device 2-47 Adding, Editing, and Removing VMware Servers 2-49 Managing a VMware Server 2-49 Removing a VMware Server 2-49 Modifying a VMware Server 2-49 Rediscovering a VMware Server 2-50 Adding and Removing Communities 2-50 Adding a Community Fabric 2-50 Removing a Community 2-50 Viewing Log Information 2-51 Configuring Cisco DCNM-SAN Server Properties 2-51 Configuring SFTP Credentials 2-51 Viewing Events and syslogs 2-52 Viewing the Accounting Events 2-52 Viewing the Events and Syslogs 2-52 Viewing Traps and Syslog Registration Information 2-53 Configuring Forwarding of Notifications for Events 2-53 Adding Notification Forwarding 2-53 Adding Notification Forwarding 2-54 Configuring EMC CallHome 2-54 Configuring AAA Properties 2-55 Adding and Removing Users 2-55 Removing a User 2-55 Adding and Removing Roles 2-56 Adding a Role 2-56 Removing a Role 2-56
Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Configuring LDAP for Remote AAA Server 2-56 LDAP Configuration for a Remote AAA Server 2-56 Viewing and Disconnecting Clients 2-58 Creating, Editing, and Removing Performance Collections Adding a Collection 2-59 Removing a Collection 2-59 Viewing the Performance Manager Collection 2-60 Configuring the RRD Database 2-61 Importing the RRD Statistics Index 2-62 Configuring Collection Thresholds 2-62 Configuring Other Statistics 2-63 Cisco DCNM Web Client Admin Group Scope 2-63 Adding Switch Groups 2-64 Adding a Member to a Group 2-66 Moving a Member 2-67 Renaming a Group 2-67 Deleting a Group or a Member of a Group 2-68 Cisco DCNM-SAN Web Search Engine 2-68 Using the Cisco DCNM-SAN Search Engine Configuring Backups Using DCNM Web Client Viewing a Configuration 2-69 Editing a Configuration 2-70 Deleting a Configuration 2-70 Copying a Configuration 2-71 Comparing Configurations 2-71 Creating Backups 2-71 Viewing Scheduled Jobs 2-72
2-68 2-69

2-59

Viewing Hosts and Virtual Hosts Information 2-72 Viewing Host Enclosures 2-72 Viewing Virtual Hosts 2-73 Viewing Virtual Machines 2-73 Viewing CPU and Memory Information of the Virtual Machines Viewing Disc I/O Information of the Virtual Machines 2-73 Viewing End Hosts 2-74 Viewing the End Hosts Summary 2-74 Troubleshooting Host Tracking 2-76 Viewing Dashboard Summary Information 2-77 Viewing Health Summary Information 2-77 Viewing Performance Summary Information 2-77
Cisco DCNM Fundamentals Guide, Release 6.x

2-73

vi

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Viewing Inventory Summary Information Viewing Switch Information 2-78
2
2-78

PART

Cisco DCNM for SAN

3

CHAPTER

Configuring Cisco DCNM-SAN Server

3-1 3-1

Information About Cisco DCNM-SAN Server DCNM-SAN Server Features 3-1

Licensing Requirements For Cisco DCNM-SAN Server

3-2

Installing and Configuring Cisco DCNM-SAN Server 3-2 Installing Cisco DCNM-SAN Server 3-3 Data Migration in Cisco DCNM-SAN Server 3-5 Verifying Performance Manager Collections 3-5 Managing a Cisco DCNM-SAN Server Fabric 3-6 Selecting a Fabric to Manage Continuously 3-6 Cisco DCNM-SAN Server Properties File 3-6 Modifying Cisco DCNM-SAN Server 3-8 Adding or Removing Cisco DCNM-SAN Server Users 3-8 Changing the Cisco DCNM-SAN Server Username and Password 3-9 Changing the DCNM-SAN Server Fabric Discovery Username and Password Changing the Polling Period and Fabric Rediscovery Time 3-9 Changing the IP Address of the Cisco DCNM-SAN Server 3-10 Using Device Aliases or FC Aliases 3-10 Server Federation 3-11 Restrictions 3-11 Mapping Fabric ID to Server ID 3-11 Opening the Fabric on a Different Server 3-12 Viewing the Sessions in a Federation 3-12 Viewing the Servers in a Federation 3-12 Additional References
4
3-13

3-9

CHAPTER

Configuring Authentication in Cisco DCNM-SAN Information About Cisco DCNM-SAN Authentication Best Practices for Discovering a Fabric 4-3 Setting Up Discovery for a Fabric 4-3 Performance Manager Authentication
4-4 4-4

4-1 4-1

Cisco DCNM-SAN Web Client Authentication

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

vii

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
CHAPTER

Configuring Cisco DCNM-SAN Client

5-1

Information About DCNM-SAN Client 5-1 Cisco DCNM-SAN Advanced Mode 5-2 Cisco DCNM-SAN Client Quick Tour: Server Admin Perspective Cisco DCNM-SAN Main Window 5-2 Menu Bar 5-4 Tool Bar 5-4 Logical Domains Pane 5-4 Physical Attributes Pane 5-4 Information Pane 5-5 Fabric Pane 5-6 Cisco DCNM-SAN Client Quick Tour: Admin Perspective Menu Bar 5-8 File 5-8 View 5-9 Zone 5-9 Tools 5-10 Performance 5-12 Server 5-12 Help 5-12 Toolbar 5-12 Logical Domains Pane 5-14 Filtering 5-15 Physical Attributes Pane 5-15 Context Menu for Tables 5-15 Information Pane 5-18 Detachable Tables 5-19 Fabric Pane 5-19 Context Menus 5-22 Saving the Map 5-22 Purging Down Elements 5-22 Multiple Fabric Display 5-23 Filtering by Groups 5-23 Status Bar 5-24
5-7 5-2

Launching Cisco DCNM-SAN Client 5-24 Launching Fabric Manager Client in Cisco SAN-OS Release 3.2(1) and Later Launching Cisco DCNM-SAN Client Using Launch Pad 5-27 Setting Cisco DCNM-SAN Preferences Network Fabric Discovery
Cisco DCNM Fundamentals Guide, Release 6.x

5-24

5-28

5-30

viii

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Network LAN Discovery 5-30 Viewing Ethernet Switches Removing a LAN 5-30

5-30

Modifying the Device Grouping 5-31 Using Alias Names as Enclosures 5-31 Using Alias Names as Descriptions 5-32 Controlling Administrator Access with Users and Roles Using Cisco DCNM-SAN Wizards
5-32 5-33 5-34 5-32

Cisco DCNM-SAN Troubleshooting Tools

Integrating Cisco DCNM-SAN and Data Center Network Management Software Launching a Switch from the Topology Map 5-34
6

CHAPTER

Device Manager

6-1

Information About Device Manager 6-1 Device Manager Features 6-2 Using Device Manager Interface 6-2 Menu Bar 6-3 Toolbar Icons 6-4 Dialog Boxes 6-5 Tabs 6-6 Legend 6-6 Supervisor and Switching Modules 6-8 Context Menus 6-8 Launching Device Manager
6-8 6-10

Setting Device Manager Preferences

7

CHAPTER

Configuring Performance Manager

7-1 7-1

Information About Performance Manager Data Interpolation 7-2 Data Collection 7-2 Using Performance Thresholds 7-2 Flow Statistics
7-3

Flow Setup Wizards 7-4 Creating a Flow Using Performance Manager Flow Wizard
7-5

7-4

CHAPTER

Monitoring the Network

8-1 8-1

Information About Network Monitoring

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

ix

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Monitoring Health and Events 8-1 DCNM-SAN Events Tab 8-2 Event Information in DCNM-SAN Web Server Reports 8-2 Events in Device Manager 8-2 SAN Discovery and Topology Mapping 8-2 Device Discovery 8-2 Topology Mapping 8-3 Using the Topology Map 8-3 Saving a Customized Topology Map Layout 8-3 Using Enclosures with DCNM-SAN Topology Maps 8-3 Mapping Multiple Fabrics 8-4 Inventory Management 8-4 Using the Inventory Tab from DCNM-SAN Web Server 8-4 Viewing Logs from Device Manager 8-4
8-5

CHAPTER

Monitoring Performance

9-1

Information About Performance Monitoring 9-1 Real-Time Performance Monitoring 9-1 Historical Performance Monitoring 9-2 Configuring Performance Manager 9-2 Creating a Flow with Performance Manager 9-2 Creating a Collection with Performance Manager 9-2 Using Performance Thresholds 9-3 Configuring the Summary View in Device Manager
9-4 9-4

Configuring Per Port Monitoring using Device Manager

Displaying DCNM-SAN Real-Time ISL Statistics 9-5 Using the Performance Manager Configuration Wizard Viewing Performance Statics Using DCNM-SAN 9-6

9-6

Displaying Performance Manager Reports 9-6 Displaying Performance Summary 9-7 Displaying Performance Tables and Details Graphs 9-7 Displaying Performance of Host-Optimized Port Groups 9-7 Displaying Performance Manager Events 9-7 Generating Performance Manager Reports 9-8 Generating Top10 Reports in Performance Manager 9-8 Generating Top10 Reports Using Scripts 9-8 Configuring Performance Manager for Use with Cisco Traffic Analyzer Exporting Data Collections
Cisco DCNM Fundamentals Guide, Release 6.x

9-9

9-11

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Exporting Data Collections to XML Files 9-11 Exporting Data Collections in Readable Format Analyzing SAN Health 9-12 Installing the SAN Health Advisor Tool
10
9-13

9-11

CHAPTER

Software Images

10-1

Information About Software Images 10-1 Software Upgrade Methods 10-2 Determining Software Compatibility 10-2 Automated Upgrades 10-3 Benefits of Using the Software Install Wizard Recognizing Failure Cases 10-4

10-3

Prerequisites for Installing Software Images 10-4 Selecting the Correct Software Images for Cisco MDS 9100 Series Switches Selecting the Correct Software Images for Cisco MDS 9200 Series Switches Selecting the Correct Software Images for Cisco MDS 9500 Family Switches Essential Upgrade Prerequisites 10-6 Default Settings
10-8

10-5 10-5 10-5

Using the Software Install Wizard 10-8 Upgrading Services Modules 10-10 Performing Nondisruptive Upgrades on Fabric and Modular Switches 10-11 Preparing for a Nondisruptive Upgrade on Fabric and Modular Switches 10-11 Performing a Nondisruptive Upgrade on a Fabric Switch 10-12 Maintaining Supervisor Modules 10-12 Replacing Supervisor Modules 10-12 Migrating from Supervisor-1 Modules to Supervisor-2 Modules 10-13 Setting Standby Supervisor Module Boot Variable Version 10-13 Setting Standby Supervisor Module Bootflash Memory 10-13 Standby Supervisor Module Boot Alert 10-14 Installing Generation 2 Modules in Generation 1 Chassis Replacing Modules
10-15 10-14 10-14

CHAPTER

11

Management Software FAQ

11-1

Installation Issues 11-3 When installing Cisco DCNM-SAN from windows, why does clicking install fail? Why do I have trouble launching Cisco DCNM-SAN on Solaris? 11-3 What do I do if my browser prompts to save JNLP files? 11-3

11-3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xi

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
What do I do if I see a "Java Web Start not detected" error? 11-4 How do I upgrade to a newer version of Cisco DCNM-SAN or Device Manager? 11-4 How do I downgrade Cisco DCNM-SAN or Device Manager? 11-4 What do I do if an upgrade is not working? 11-4 What do I do if Java Web Start hangs on the download dialog? 11-4 How do I manually configure a browser for Java Web Start? 11-5 How do I run Java Web Start from the command line? 11-5 How do I clear the Java Web Start cache? 11-5 What do I do if during a Cisco DCNM-SAN upgrade, the installer doesnt display a prompt to create a shortcut? 11-6 What do I do if my login does not work in Cisco DCNM-SAN or Device Manager? 11-6 What do I do if I cannot install Cisco DCNM-SAN or Device Manager, or run Java, when pcAnyWhere is running? 11-6 What do I do if the Cisco DCNM-SAN or Performance Manager service shows up as disabled in the Services menu? 11-6 What do I do if I am unable to install Cisco DCNM-SAN or Device Manager, or run Java, when McAfee Internet Suite 6.0 Professional is running? 11-7 General 11-7 What do I do if I see errors while monitoring Area chart graphing? 11-7 What do I do if I see "gen error" messages? 11-7 What do I do if disk images in the Device Manager Summary View are not visible? 11-7 What do I do if I am unable to set both the D_S_TOV and E_D_TOV timers in Device Manager? 11-7 What do I do if columns in Device Manager tables are too small? 11-8 What do I do if fabric changes are not propagated onto the map (for example, links don't disappear)? 11-8 What do I do if the PortChannel creation dialog becomes too small after several uses? 11-8 What do I do if I see errors after IPFC configuration? 11-8 What do I do if Cisco DCNM-SAN or Device Manager is using the wrong network interface? 11-8 What do I do if I see display anomalies in Cisco DCNM-SAN or Device Manager? 11-9 What do I do if most of my Physical Attributes catagories disappear? 11-9 What do I do if I cant see the Information pane? 11-9 Why is the active zone set in edit zone always shown in bold (even after successful activation)? 11-9 Can I create a zone with prefix IVRZ or a zone set with name nozonset? 11-9 What do I do when One-Click License Install fails, and I cannot connect to the Cisco website? 11-9 How do I increase the log window size in Cisco DCNM-SAN Client? 11-10 When do I do when the FM Server Database fails to start or has a file locking error? 11-10 How do I re-synchronize Cisco DCNM-SAN Client with Cisco DCNM-SAN Server? 11-10 How do I rediscover the current fabric? 11-10 How do I rediscover SCSI Targets? 11-10 Windows Issues
11-10

Cisco DCNM Fundamentals Guide, Release 6.x

xii

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
What do I do when text fields show up too small, and I cannot enter any data? 11-10 What do I do when printing causes an application crash? 11-11 What do I do when Windows XP hangs (or I see a blue screen)? 11-11 What do I do when Cisco DCNM-SAN and Device Manager Icons Disappear? 11-11 What do I do when Device Manager or Cisco DCNM-SAN window content disappears in Windows XP? 11-11 What do I do when SCP/SFTP fails when a file is copied from local machine to the switch? 11-11 UNIX Issues 11-12 What do I do when the parent Menus Disappear? 11-12 What do I do when the web browser cannot find web server even it is running? How do I fix a "too many open files" error? 11-12

11-12

Other 11-13 How do I set the map layout so it stays after Cisco DCNM-SAN restarted? 11-13 What do I do when two switches show on the map, but there is only one switch? 11-13 What does a red/orange/dotted line through the switch mean? 11-13 How do I upgrade without losing map settings? 11-19 How do I preserve historical data when moving Cisco DCNM-SAN server to new host? 11-19 Are there restrictions when using Cisco DCNM-SAN across FCIP? 11-19 How do I fix a "Please insure that FM server is running on localhost" message? 11-20 How do I run Cisco DCNM-SAN with multiple interfaces? 11-20 Manually specifying an interface for Cisco DCNM-SAN Server 11-21 Manually specifying an interface for Cisco DCNM-SAN Client or Device Manager 11-21 How do I configure an HTTP proxy server? 11-21 How do I clear the topology map? 11-22 How can I use Cisco DCNM-SAN in a mixed software environment? 11-22 How do I fix a "corrupted jar file" error when Launching Cisco DCNM-SAN? 11-22 How do I search for Devices in a Fabric? 11-23 How do I search in a table? 11-23 How do I manage Multiple Fabrics? 11-24 How can I clear an Orange X Through a Switch caused by license expiration? 11-24
3

PART

Cisco DCNM for LAN

12

CHAPTER

Overview of DCNM-LAN

12-1 12-1 12-2

DCNM-LAN Client and Server Platform Support

12-3

Features in Cisco DCNM-LAN, Release 5.2 Documentation About DCNM-LAN

12-3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xiii

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
CHAPTER

13

Installing and Launching the Cisco DCNM-LAN Client

13-1 13-1 13-2

Information About Installing and Launching the DCNM-LAN Client Prerequisites for Installing and Launching the DCNM-LAN Client Secure Client Communications
13-2 13-3

Default Administrator Credentials

Downloading and Launching the DCNM-LAN Client 13-3 Using a Web Browser to Download and Launch the DCNM-LAN Client 13-3 Using a Command Prompt to Download and Launch the DCNM-LAN Client 13-5 Using a Command Prompt to Download and Launch the DCNM-LAN Client without using Java Web Start Launcher 13-6 Restarting the DCNM-LAN Client Logging Into the DCNM-LAN Client Uninstalling the DCNM-LAN Client Additional References 13-9 Related Documents 13-9 Standards 13-9 Feature History for Installing and Launching the DCNM-LAN Client
14
13-10 13-7 13-7 13-8

CHAPTER

Using the Cisco DCNM-LAN Client

14-1 14-1

Information About the DCNM-LAN Client User Interface 14-2 Feature Selector Pane 14-2 Contents Pane 14-3 Summary Pane 14-3 Details Pane 14-3 Association Pane 14-4 Menus 14-5 Toolbars 14-6 Keyboard Commands 14-7 Multiple Platform Support 14-7 Opening the DCNM-LAN Client Closing the DCNM-LAN Client Deploying Changes
14-10 14-8 14-9

Working with Statistics and Charts 14-10 Information about Statistics and Charts 14-11 Licensing Requirements for Statistics and Charts 14-11 Accessing a Chart 14-11 Starting Statistical Monitoring for a Chart 14-12
Cisco DCNM Fundamentals Guide, Release 6.x

xiv

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Stopping Statistical Monitoring for a Chart Using a Chart 14-13 Using an Overview Chart 14-14 Exporting a Chart 14-15
14-12

Configuring Global Preferences 14-15 Configuring Monitoring Preferences 14-16 Configuring the Maximum Age of Events Fetched from the Server Configuring Preprovisioning 14-17 Using Online Help
14-18

14-16

Additional References 14-18 Related Documents 14-18 Standards 14-19 Feature History for Using the DCNM-LAN Client
15
14-19

CHAPTER

Administering DCNM-LAN Authentication Settings

15-1 15-1

Information About Administering DCNM-LAN Authentication Settings Users and User Roles 15-2 Local Authentication and DCNM-LAN Local Users 15-2 RADIUS and TACACS+ Authentication 15-2 User Role Assignment by RADIUS and TACACS+ 15-3 Fallback to Local Authentication 15-3 Password Recovery 15-3 Users and Device Credentials 15-4 Virtualization Support 15-4 Prerequisites for Administering DCNM-LAN Authentication Settings

Licensing Requirements for Administering DCNM-LAN Authentication Settings

15-4

15-4

Guidelines and Limitations for Administering DCNM-LAN Authentication Settings Configuring DCNM-LAN Authentication Settings 15-5 Configuring the Authentication Mode 15-5 Adding a DCNM-LAN Local User 15-6 Changing the Password of a DCNM-LAN Local User 15-7 Changing the Full Name, Role, or Description of a DCNM-LAN Local User Deleting a DCNM-LAN Server User 15-8 Adding Authentication Servers 15-9 Changing Authentication Server Settings 15-10 Removing an Authentication Server 15-11 Viewing DCNM-LAN Local Users
15-12 15-12

15-5

15-8

Verifying Authentication Server Settings

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xv

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Field Descriptions for DCNM-LAN Authentication Settings Authentication Mode Section 15-13 DCNM-LAN Local Users Section 15-13 Authentication Servers Section 15-14 Additional References 15-14 Related Documents 15-15 Standards 15-15 Feature History for DCNM-LAN Authentication Settings
16
15-15 15-13

CHAPTER

Administering Device Discovery

16-1

Information About Device Discovery 16-1 Device Discovery 16-2 Discovery Protocols 16-2 Cisco Discovery Protocol 16-2 Link Layer Discovery Protocol 16-3 Fibre Channel 16-3 Credentials and Discovery 16-3 Discovery Process 16-3 Cisco NX-OS System-Message Logging Requirements 16-4 Interface Link-Status Events Logging Requirement 16-4 Logfile Requirements 16-4 Logging Severity-Level Requirements 16-4 Automatic Logging-Level Configuration Support 16-5 During Device Discovery 16-5 At Feature Enablement in the DCNM-LAN Client 16-5 During Auto-Synchronization with Managed Devices 16-5 VDC Support 16-5 Licensing Requirements for Device Discovery Prerequisites for Device Discovery
16-7 16-7 16-6

Guidelines and Limitations for Device Discovery

Performing Device Discovery 16-8 Verifying the Discovery Readiness of a Cisco NX-OS Device Discovering Devices 16-10 Rediscovering Devices 16-11 Viewing the Status of Device Discovery Tasks Where to Go Next
16-12 16-12

16-8

Field Descriptions for Device Discovery 16-13 Device Discovery Content Pane 16-13

Cisco DCNM Fundamentals Guide, Release 6.x

xvi

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Related Fields
16-14

Device System-Message Logging Level Reference 16-14 Cisco Nexus 7000 NX-OS Logging Levels per DCNM-LAN Feature 16-15 Cisco Nexus 5000 NX-OS Logging Levels per DCNM-LAN Feature 16-16 Cisco Nexus 4000 NX-OS Logging Levels per DCNM-LAN Feature 16-17 Cisco Nexus 1000V NX-OS Logging Levels per DCNM-LAN Feature 16-18 Additional References for Device Discovery Related Documents 16-18 Standards 16-19 Feature History for Device Discovery
17
16-19 16-18

CHAPTER

Administering Devices and Credentials

17-1 17-1

Information About Devices and Credentials Devices 17-1 Credentials 17-2 Device Status 17-2 VDC Support 17-2

Licensing Requirements for Devices and Credentials Guidelines and Limitations for Devices and Credentials

17-2 17-3 17-3

Prerequisites for Administering Devices and Credentials Configuring Devices and Credentials 17-3 Adding a Device 17-3 Discovering a Device 17-4 Unmanaging a Device 17-5 Deleting a Device 17-5 Configuring Default Device Credentials 17-6 Clearing Default Device Credentials 17-7 Configuring Unique Credentials for a Device 17-7 Clearing Unique Credentials for a Device 17-8 Viewing Device Credentials and Status
17-9

Field Descriptions for Devices and Credentials 17-10 Device and Credentials Content Pane 17-10 Additional References for Devices and Credentials Related Documents 17-11 Standards 17-11 Feature History for Devices and Credentials
17-11 17-11

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xvii

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
CHAPTER

18

Administering DCNM-LAN Licensed Devices Information About DCNM-LAN Licensed Devices

18-1 18-1 18-2

Licensing Requirements for Administering DCNM-LAN Licensed Devices Prerequisites for Administering DCNM-LAN Licensed Devices Configuring DCNM-LAN Licensed Devices 18-2 Adding Devices to the Licensed Devices List 18-3 Removing Devices from the Licensed Devices List 18-3 Viewing DCNM-LAN Licensed Devices
18-4 18-2

Guidelines and Limitations for Administering DCNM-LAN Licensed Devices

18-2

Field Descriptions for DCNM-LAN Licensed Devices 18-4 DCNM-LAN Licensed Devices Content Pane 18-4 Additional References 18-5 Related Documents 18-5 Standards 18-5 Feature History for DCNM-LAN Licensed Devices
19
18-5

CHAPTER

Working with Topology

19-1

Information About Topology 19-1 Map Views 19-2 Physical View 19-2 PortChannel and vPC 19-3 Logical vPC View 19-4 L2 View 19-5 Layouts 19-5 vPC Support 19-6 DCNM-SAN Support 19-6 Common Topology 19-6 Access to DCNM-SAN Features FabricPath Support 19-6 Device Groups 19-7 Network Servers 19-7 Licensing Requirements for Topology Prerequisites for Topology Guidelines and Limitations
19-8 19-8 19-8

19-6

Using the Topology Feature 19-8 Opening the Topology Map 19-9 Understanding Device Icons and Links Using the Viewing Tools 19-12
Cisco DCNM Fundamentals Guide, Release 6.x

19-10

xviii

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Showing, Hiding, and Using the Details Pane 19-13 Moving Devices in the Topology Map 19-14 Loading a Layout 19-15 Reloading the Previously Saved Layout 19-16 Showing a Virtual or Physical Chassis 19-16 Showing or Hiding Network Servers 19-17 Managing a Network Server 19-17 Showing or Hiding Device Groups 19-18 Expanding or Collapsing Device Groups 19-18 Creating a Device Group 19-19 Moving a Device Between Device Groups 19-19 Removing a Device from a Device Group 19-20 Copy Run to Start 19-21 Deleting a Device Group 19-22 Exporting the Topology as a JPG Image 19-22 Accessing DCNM-LAN Features from the Topology Map 19-23 Accessing Cisco DCNM-SAN Features from the Topology Map 19-24 Accessing Cisco FabricPath Features from the Topology Map 19-25 Multi-destination 19-25 Device Reachability 19-25 Unicast 19-26 Multicast 19-27 Launching the vPC Wizard 19-28 Managing a vPC 19-28 Finding and Resolving vPC Configuration Inconsistencies 19-29 Accessing Remotely Connected CNAs from the Topology Map 19-29 Using VSAN Overlay 19-30 Related Documents
19-30 19-31

Feature History for Topology

20

CHAPTER

Configuring Network Servers

20-1

Information About Network Servers 20-1 Automatic Correlation of Adapters to Servers 20-2 Manual Correlation of Adapters to Servers 20-2 Licensing Requirements for Network Servers Prerequisites for Network Servers
20-3 20-3 20-2

Guidelines and Limitations for Network Servers Configuring Network Servers 20-3 Configuring Default Server Credentials
20-4

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xix

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Clearing Default Server Credentials 20-4 Configuring Unique Credentials for a Server 20-5 Clearing Unique Credentials for a Server 20-6 Correlating Servers 20-6 Correlating a Server to Adapters Automatically 20-9 Binding Adapters to a Server Manually 20-10 Unbinding an Adapter from a Server 20-10 Viewing Server Connectivity Information
20-11

Field Descriptions for Network Servers 20-11 Field Descriptions for Servers 20-11 Servers Summary Pane 20-12 Server: Server Details: LAN Connectivity Section Server: Server Details: SAN Connectivity Section Field Descriptions for Static Server-Adapter Mapping Field Descriptions for Server Credentials 20-13 Additional References 20-14 Related Documents 20-14 Standards 20-14 Feature History for Network Servers
21
20-15

20-12 20-12 20-13

CHAPTER

Configuring Device Groups

21-1 21-1 21-2

Information About Device Groups Prerequisites for Device Groups

Licensing Requirements for Device Groups

21-2

Guidelines and Limitations for Device Groups Configuring Device Groups 21-2 Creating a Device Group 21-2 Adding Devices to a Group 21-4 Removing Devices from a Group 21-5 Deleting a Device Group 21-5 Where to Go Next
21-6

21-2

Field Descriptions for Device Groups 21-6 Summary Pane 21-6 Device Group: Details: Global Settings Section 21-7 Device Group: Details: Membership Details Section 21-7 Additional References 21-7 Related Documents 21-7 Standards 21-7
Cisco DCNM Fundamentals Guide, Release 6.x

xx

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Feature History for Device Groups
22
21-8

CHAPTER

Working with Cluster Administration

22-1

Information About Cluster Administration 22-1 Cluster Administration 22-1 Clustered-Server Environment 22-2 Master Server Role 22-2 Distributed Server Tasks 22-2 Effect of Cluster Changes on Server Task Distribution Licensing Requirements for Cluster Administration Prerequisites for Cluster Administration Viewing Server Information
22-4 22-5 22-4 22-4 22-4

22-3

Guidelines and Limitations for Cluster Administration Field Descriptions for Cluster Administration Summary Pane 22-5 Server: Details Tab 22-5 Additional References 22-6 Related Documents 22-6 Standards 22-6 Feature History for Cluster Administration
23
22-6

CHAPTER

Administering Auto-Synchronization with Devices

23-1

Information About Auto-Synchronization with Devices 23-1 Automatic and Manual Purging of Event Data 23-2 Virtualization Support 23-2 Licensing Requirements for Auto-Synchronization with Devices Prerequisites for Auto-Synchronization with Devices
23-2 23-3 23-2

Guidelines and Limitations for Auto-Synchronization with Devices Configuring Device Auto-Synchronization 23-3 Starting and Stopping a Poller 23-3 Configuring the Polling Interval 23-4 Synchronizing with a Device 23-4 Deleting Data from the Events Database 23-5 Enabling and Disabling Automatic Event Purging 23-6 Configuring Automatic Event Purge Settings 23-6 Purging Events Now 23-8 Viewing the Status of Auto-Synchronization Pollers
23-8 23-9

Field Descriptions for Auto Synchronization with Devices

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xxi

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Poller Setting Tab 23-9 Events Database Administration Tab Additional References 23-10 Related Documents 23-10 Standards 23-11 Feature History for Auto-Synchronization with Devices
24
23-11

23-9

CHAPTER

Working With Threshold Rules

24-1

Information About Threshold Rules 24-1 Threshold Rules Overview 24-1 Rising Threshold 24-2 Falling Threshold 24-2 Threshold Rule Properties 24-2 Threshold Rule Actions 24-2 Threshold Rule Examples 24-2 Triggering an Action Each Time a Threshold is Crossed 24-2 Triggering an Action Only Once in a Period When a Threshold is Crossed 24-3 Triggering an Action Every Fourth Period When a Threshold is Crossed 24-4 Licensing Requirements for Threshold Rules Configuring Threshold Rules 24-5 Creating Threshold Rules 24-5 Deleting Threshold Rules 24-7 Editing Threshold Rules 24-7 Viewing Threshold Rules 24-8 Applying a Threshold Rule to a Chart Additional References 24-8 Related Documents 24-8 Standards 24-9 Feature History for Threshold Rules
25
24-9 24-5

24-8

CHAPTER

Administering Statistical Data Collection

25-1

Information About Statistical Data Collection 25-1 Automatic and Manual Purging of Statistical Data Virtualization Support 25-2 Licensing Requirements for Statistical Data Collection Prerequisites for Statistical Data Collection Configuring Statistical Data Collection
Cisco DCNM Fundamentals Guide, Release 6.x

25-2

25-2

25-2 25-3

Guidelines and Limitations for Statistical Data Collection

25-3

xxii

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Starting and Stopping Statistical Data Collection 25-3 Using Modes in Statistics Charts 25-4 Deleting Statistical Data from a Collection 25-5 Deleting a Collection 25-5 Deleting Data from the Statistics Database 25-6 Enabling and Disabling Automatic Statistical Data Purging 25-6 Configuring Automatic Statistical Data Purge Settings 25-7 Purging Statistical Data Now 25-8 Viewing the Status of Statistical Data Collectors
25-9

Field Descriptions for Statistical Data Collection 25-9 Summary Pane 25-9 Statistical Database Administration Tab 25-10 Additional References 25-11 Related Documents 25-11 Standards 25-11 Feature History for Statistical Data Collection
26
25-11

CHAPTER

Working with Network Analysis

26-1 26-1 26-2

Information About Network Analysis Prerequisites for Network Analysis

Licensing Requirements for Network Analysis

26-2

Guidelines and Limitations for Network Analysis Using the Network Analysis Feature 26-2 Using Network Analysis 26-2 Using the New Path Latency Session Wizard Viewing Session Statistics 26-7 Related Documents
26-8 26-8

26-2

26-4

Feature History for Network Analysis

27

CHAPTER

Administering DCNM-LAN Server Log Settings

27-1 27-1

Information About Administering DCNM-LAN Server Log Settings Logging Levels 27-2 Log File and Location 27-2 Virtualization Support 27-2 Prerequisites for Administering DCNM-LAN Server Log Settings Configuring DCNM-LAN Server Log Settings
27-3

Licensing Requirements for Administering DCNM-LAN Server Log Settings

27-2

27-2

Guidelines and Limitations for Administering DCNM-LAN Server Log Settings

27-3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xxiii

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Configuring the Default Logging Level 27-3 Configuring a Unique Logging Level for a Feature or Server Component 27-3 Configuring a Feature or Server Component to Use the Default Logging Level 27-4 Viewing DCNM-LAN Server Log Settings
27-4

Field Descriptions for DCNM-LAN Server Log Settings 27-5 DCNM-LAN Server Log Settings Contents Pane 27-5 Additional References 27-6 Related Documents 27-6 Standards 27-6 Feature History for DCNM-LAN Server Log Settings
28
27-7

CHAPTER

Starting and Stopping Cisco DCNM-LAN Servers

28-1 28-1 28-1

Information About Starting and Stopping DCNM-LAN Servers

Licensing Requirements for Starting and Stopping Cisco DCNM-LAN Servers Starting DCNM-LAN Servers 28-2 Starting a Single DCNM-LAN Server 28-2 Starting a Single DCNM-LAN Server (Microsoft Windows Server) Starting a Single DCNM-LAN Server (RHEL) 28-2 Starting a Cluster of DCNM-LAN Servers 28-3 Starting with Windows GUI or RHEL CLI 28-3 Starting with Install Manager 28-4 Stopping DCNM-LAN Servers 28-5 Stopping Single DCNM-LAN Servers 28-5 Stopping a Single DCNM-LAN Server (Microsoft Windows Server) Stopping a Single DCNM-LAN Server (RHEL) 28-6 Stopping a Cluster of DCNM-LAN Servers 28-6 Stopping with CLI 28-6 Example 28-7 Stopping with Install Manager 28-7 Related Documents
28-8 28-9

28-2

28-5

Feature History for Starting and Stopping a DCNM-LAN Server

29

CHAPTER

Maintaining the Cisco DCNM-LAN Database

29-1

Information About Database Maintenance 29-1 Automatic and Manual Purging of Data 29-1 Database Backup 29-2 Database Clean 29-2 Database Restore 29-2

Cisco DCNM Fundamentals Guide, Release 6.x

xxiv

OL-25174-02

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Licensing Requirements for Database Maintenance Prerequisites for Database Maintenance
29-3 29-3 29-3

Guidelines and Limitations for Database Maintenance

Performing Database Maintenance 29-4 Backing Up the DCNM-LAN Database 29-4 Cleaning a DCNM-LAN Database 29-5 Restoring a DCNM-LAN Database from a Backup File Additional References 29-9 Related Documents 29-9 Standards 29-9 Feature History for DCNM-LAN Database Maintenance
30

29-7

29-9

CHAPTER

Troubleshooting DCNM-LAN

30-1

Tips for Using DCNM-LAN 30-1 Events Tabs Show Fewer Events than the Event Browser 30-1 Event Browser Pie Chart May Be Inaccurate for Small Numbers Trouble with Starting the DCNM-LAN Server DCNM-LAN Server Fails to Start 30-2
30-2

30-2

Trouble with the DCNM-LAN Database 30-3 Trouble with a PostgreSQL Database 30-3 Updating DCNM-LAN Database Name and Username in pgAdmin III Trouble with an Oracle Database 30-4 Trouble with the DCNM-LAN Client 30-5 Cannot Download the DCNM-LAN Client from the Server 30-6 Cannot Install the DCNM-LAN Client 30-6 Cannot Start the DCNM-LAN Client 30-7 Cannot Log into the DCNM-LAN Client 30-8 Client Loses Connection to the DCNM-LAN Server 30-10 Trouble with Device Discovery or Device Status Trouble with Device Management Trouble with Topology
30-12 30-13 30-12 30-11

30-3

Trouble with Device OS Management Trouble with Event Browsing

4
30-13

PART

Appendices Launching Fabric Manager in Cisco SAN-OS Releases Prior to 3.2(1) Setting the Seed Switch in Cisco SAN-OS Releases 3.1(1) to 3.2(1)
A-1 A-1

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xxv

Contents

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Setting the Seed Switch in Releases Prior to Cisco SAN-OS Release 3.1(1) Cisco DCNM Unsupported Feature List Interface Nonoperational Reason Codes Managing Cisco FabricWare Fibre Channel Support Zone Configuration Security Events
D-2 D-2 D-3 D-1 D-1 D-1 B-1 C-1 A-3

Managing Cisco FabricWare with DCNM

Cisco DCNM Fundamentals Guide, Release 6.x

xxvi

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

New and Changed Information

The information in the new Cisco Fabric Manager Fundamentals Configuration Guide previously existed in Part 1:Getting Started, Part 8: Network and Switch Monitoring, and various Appendices of the Cisco MDS 9000 Family Fabric Manager Configuration Guide. Table 1 lists the New and Changed features for this guide.
Table 1 New and Changed Features for Cisco DCNM Release 6.x

Feature

New or Changed Topics

Changed in Release 6.1(2) 6.1(2) 6.1(2)

Where Documented Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client

Templates Configuration Configuring vPC, FCoE and FIP templates Common LAN Discovery Host Dashboard Summary Dashboard Discover various Cisco devices from a sngle interface. Information about SAN and virtual hosts.

Details about Datacenter 6.1(2) switches, selected SAN and LAN switches, or a group of LAN and SAN switches. Monitor MDS switch events, performance and memory from a remote location Generate the Web client page report Searching a LAN or SAN device by its name, IP address, world wide name (WWN), alias, or serial number. 6.1(1a)

Configuration Archive Web Client Page Report Web Client Page Enhanced Search Capabilty

Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client

6.1(1a) 6.1(1a)

Events and Syslogs Groups Host Tracking and Host Screens

Viewing all events and syslogs on 6.1(1a) the Events window. Configuring switch groups Tracking end hosts and screens 6.1(1a) 6.1(1a)

Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xxvii

New and Changed Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 1 New and Changed Features for Cisco DCNM Release 6.x (continued)

Feature Improved Cisco Prime Look and Feel Performace Manager Collection Port Mapper Remote AAA LDAP Configuration vPC Inconsistency vPC Utilization and Traffic Distribution Device Discovery Summary Dashboard Hosts Dashboard Integrating FM and DCNM Search Engine Switch Configuration Management SAN Health Analyzer Tool Software Upgrade Wizard Enhancement Web Client Report Enhancement Scoped Discovery Federated Server Cisco Discovery Protocol - FM - DM Enhancements FM Web Client: Report Enhancements

New or Changed Topics Improved look and feel of Cisco DCNM Web Client Viewing Performance Manager collections Viewing the port mapper Configuring LDAP for a remote AAA server Resolving vPC inconsistency Viewing the relationship among vPCs Supports F2 module Viewing Dashboard Summary Information Viewing Hosts and Virtual Hosts Information Integrating Fabric Manager and Data Center Network

Changed in Release 6.1(1a) 6.1(1a) 6.1(1a) 6.1(1a) 6.1(1a) 6.1(1a) 5.2(2a) 5.2(1a) 5.2(1a) 5.0(1)

Where Documented Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 16, Administering Device Discovery Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 5, Configuring Cisco DCNM-SAN Client Chapter 2, Cisco DCNM Web Client Chapter 2, Cisco DCNM Web Client Chapter 9, Monitoring Performance Chapter 10, Software Images Chapter 2, Cisco DCNM Web Client Chapter 5, Configuring Cisco DCNM-SAN Client Chapter 3, Configuring Cisco DCNM-SAN Server Chapter 5, Configuring Cisco DCNM-SAN Client Chapter 2, Cisco DCNM Web Client

Fabric manager Webclient Search 5.0(1) Engine Configuration Backups using Fabric Manager Webclient Analyzing SAN Health 5.0(1) 5.0(1)

Using the Software Install Wizard 5.0(1) Reports VSAN Scoped Discovery Server Federation 5.0(1) 5.0(1) 4.2(1)

Launching Fabric Manager Client 4.2(1)

Viewing Custom Reports by Template. Generating Custom Reports by Template.

4.2(1)

Cisco DCNM Fundamentals Guide, Release 6.x

xxviii

OL-25174-02

New and Changed Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 1 New and Changed Features for Cisco DCNM Release 6.x (continued)

Feature Fabric Manager Launch Pad

New or Changed Topics

Changed in Release

Where Documented Chapter 5, Configuring Cisco DCNM-SAN Client Chapter 5, Configuring Cisco DCNM-SAN Client Chapter 9, Monitoring Performance

Launching Fabric Manager Client 4.2(1) Using Launch Pad. 4.2(1) 4.2(1)

Populate Device Alias to Using Alias Names as Device Description Descriptions. FM Historical and Real Time Charts Viewing Statics Using Fabric Manager

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

xxix

New and Changed Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

xxx

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Preface
This preface describes the audience, organization, and conventions of the Cisco DCNM Fundamentals Configuration Guide. It also provides information on how to obtain related documentation.

Audience
This guide is for experienced network administrators who are responsible for configuring and maintaining the Cisco MDS 9000 Family of multilayer directors and fabric switches.

Organization
This guide is organized as follows: Chapter Part 1 Chapter i Chapter 1 Title Cisco Data Center Network Manager Introduction to Cisco Data Center Network Manager Cisco DCNM Fundamentals Overview Cisco DCNM Web Client Cisco DCNM for SAN Configuring Cisco DCNM-SAN Server Configuring Authentication in Cisco DCNM-SAN Configuring Cisco DCNM-SAN Client Device Manager Description Provides information about Cisco DCNM. Provides a brief overview of Cisco DCNM Fundamentals. Provides a brief overview of Cisco DCNM-SAN. Provides in-depth descriptions of GUI and capabilities of Cisco DCNM Web Client. Provides information about Cisco DCNM for SAN. Provides in-depth descriptions of GUI and capabilities of Cisco DCNM-SAN Server. Describes the authentication schemes between Cisco DCNM-SAN components and fabric switches. Provides in-depth descriptions of GUI and capabilities of Cisco DCNM-SAN. Provides in-depth descriptions of GUI and capabilities of Device Manager.

Chapter 2 Part 2 Chapter 3 Chapter 4

Chapter 5 Chapter 6

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

lxi

Preface

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Chapter Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Title Configuring Performance Manager Monitoring the Network Monitoring Performance Software Images Management Software FAQ Description Provides overview of the Performance Manager architecture. Provides details on monitoring the network. Provides details on using Performance Manager. Provides details on installing and upgrading software on switches. Provides answers to some of the most frequently asked questions about Cisco Fabric Manager and Device Manager. Provides information about Cisco DCNM for LAN. Provides an overview of what you need to do to start using Cisco Data Center Network Manager for LAN (DCNM-LAN). Describes how to install and set up the Cisco DCNM-LAN client. Introduces the Cisco DCNM-LAN client and explains how to use it. Describes how to administer the Cisco DCNM-LAN server user accounts. Describes how to use the Device Discovery feature. Describes how to use the Devices and Credentials feature.

Part 3 Chapter 12

Cisco DCNM for LAN Overview of DCNM-LAN

Chapter 13 Chapter 14 Chapter 15 Chapter 16 Chapter 17 Chapter 18 Chapter 19 Chapter 20 Chapter 21 Chapter 22 Chapter 23 Chapter 24 Chapter 25 Chapter 26 Chapter 27

Installing and Launching the Cisco DCNM-LAN Client Using the Cisco DCNM-LAN Client Administering DCNM-LAN Authentication Settings Administering Device Discovery Administering Devices and Credentials

Administering DCNM-LAN Licensed Describes how to use the DCNM-LAN Licensed Devices feature. Devices Working with Topology Configuring Network Servers Configuring Device Groups Describes how to use the Topology feature. Describes how to use the Network Servers feature. Describes how to use the Device Groups feature.

Working with Cluster Administration Describes how to use the Cluster Administration feature. Administering Auto-Synchronization Describes how to use the Auto-Synchronization with Devices feature. with Devices Working With Threshold Rules Administering Statistical Data Collection Working with Network Analysis Administering DCNM-LAN Server Log Settings Describes how to configure threshold rules. Describes how to control statistical data collection. Describes how to track and monitor the latency between two specified switches. Describes how to control Cisco DCNM-LAN server logs.

Cisco DCNM Fundamentals Guide, Release 6.x

lxii

OL-25174-02

Preface

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Chapter Chapter 28 Chapter 29 Chapter 30 Part 4 Appendix A Title Starting and Stopping Cisco DCNM-LAN Servers Maintaining the Cisco DCNM-LAN Database Troubleshooting DCNM-LAN Appendices Launching Fabric Manager in Cisco SAN-OS Releases Prior to 3.2(1) Cisco DCNM Unsupported Feature List Interface Nonoperational Reason Codes Managing Cisco FabricWare Provides instructions for launching Fabric Manager Client in Cisco SAN-OS releases prior to 3.2(1). Provides a list of features and functions not supported by Cisco Fabric Manager or Device Manager. Provides the nonoperational reason codes for why an interface is up and the operational state is down. Provides information on the Cisco FabricWare software running on the MDS 9020 Switch which offers Fibre Channel switching services that realize maximum performance. Description Describes how to start and stop the Cisco DCNM-LAN server. Describes how to maintain the Cisco DCNM-LAN database. Explains how to resolve problems that you might encounter with Cisco DCNM-LAN.

Appendix B

Appendix C

Appendix D

Document Conventions
Command descriptions use these conventions: boldface font italic font [ ] [x|y|z] Commands and keywords are in boldface. Arguments for which you supply values are in italics. Elements in square brackets are optional. Optional alternative keywords are grouped in brackets and separated by vertical bars.

Screen examples use these conventions:

screen font boldface screen font

Terminal sessions and information the switch displays are in screen font. Information you must enter is in boldface screen font. Arguments for which you supply values are in italic screen font. Nonprinting characters, such as passwords, are in angle brackets. Default responses to system prompts are in square brackets. An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

italic screen font

< > [ ] !, #

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

lxiii

Preface

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
This document uses the following conventions:

Note

Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.

Caution

Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. In this document, the following shortened names are used:

Cisco Data Center Network Manager for SAN is also referred to as DCNM-SAN. Cisco Data Center Network Manager for LAN is also referred to as DCNM-LAN.

Related Documentation
This section contains information about the documentation available for Cisco DCNM and for the platforms that Cisco DCNM manages. This section includes the following topics:

Cisco DCNM Documentation, page lxiv Cisco Nexus 1000V Series Switch Documentation, page lxv Cisco Nexus 2000 Series Fabric Extender Documentation, page lxv Cisco Nexus 3000 Series Switch Documentation, page lxv Cisco Nexus 4000 Series Switch Documentation, page lxvi Cisco Nexus 5000 Series Switch Documentation, page lxvi Cisco Nexus 7000 Series Switch Documentation, page lxvi

Cisco DCNM Documentation

The Cisco DCNM documentation is available at the following URL: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_series_home.html The documentation set for Cisco DCNM includes the following documents:

Release Notes
Cisco DCNM Release Notes, Release 5.x

Cisco DCNM
The following publications support both Cisco DCNM for LAN and DCNM for SAN, and address the new licensing model, the new installation process, and the new features of Cisco DCNM:

Cisco DCNM Fundamentals Guide, Release 6.x

Cisco DCNM Fundamentals Guide, Release 6.x

lxiv

OL-25174-02

Preface

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Installation Guide, Release 6.x

Cisco DCNM for LAN Configuration Guides

FabricPath Configuration Guide, Cisco DCNM for LAN, Release 5.x Interfaces Configuration Guide, Cisco DCNM for LAN, Release 5.x Layer 2 Switching Configuration Guide, Cisco DCNM for LAN, Release 5.x Security Configuration Guide, Cisco DCNM for LAN, Release 5.x System Management Configuration Guide, Cisco DCNM for LAN, Release 5.x Unicast Configuration Guide, Cisco DCNM for LAN, Release 5.x Virtual Device Context Configuration Guide, Cisco DCNM for LAN, Release 5.x Virtual Device Context Quick Start, Cisco DCNM for LAN, Release 5.x Web Services API Guide, Cisco DCNM for LAN, Release 5.x

Cisco DCNM for SAN Configuration Guides

System Management Configuration Guide, Cisco DCNM for SAN, Release 5.x Interfaces Configuration Guide, Cisco DCNM for SAN, Release 5.x Fabric Configuration Guide, Cisco DCNM for SAN, Release 5.x Quality of Service Configuration Guide, Cisco DCNM for SAN, Release 5.x Security Configuration Guide, Cisco DCNM for SAN, Release 5.x IP Services Configuration Guide, Cisco DCNM for SAN, Release 5.x Intelligent Storage Services Configuration Guide, Cisco DCNM for SAN, Release 5.x High Availability and Redundancy Configuration Guide, Cisco DCNM for SAN, Release 5.x Inter-VSAN Routing Configuration Guide, Cisco DCNM for SAN, Release 5.x SMI-S and Web Services Programming Guide, Cisco DCNM for SAN, Release 5.x

Cisco Nexus 1000V Series Switch Documentation

The Cisco Nexus 1000V Series switch documentation is available at the following URL: http://www.cisco.com/en/US/products/ps9902/tsd_products_support_series_home.html

Cisco Nexus 2000 Series Fabric Extender Documentation

The Cisco Nexus 2000 Series Fabric Extender documentation is available at the following URL: http://www.cisco.com/en/US/products/ps10110/tsd_products_support_series_home.html

Cisco Nexus 3000 Series Switch Documentation

The Cisco Nexus 3000 Series switch documentation is available at the followingURL: http://www.cisco.com/en/US/products/ps11541/tsd_products_support_series_home.html

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

lxv

Preface

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco Nexus 4000 Series Switch Documentation

The Cisco Nexus 4000 Series switch documentation is available at the following URL: http://www.cisco.com/en/US/products/ps10596/tsd_products_support_series_home.html

Cisco Nexus 5000 Series Switch Documentation

The Cisco Nexus 5000 Series switch documentation is available at the following URL: http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.html

Cisco Nexus 7000 Series Switch Documentation

The Cisco Nexus 7000 Series switch documentation is available at the following URL: http://www.cisco.com/en/US/products/ps9902/tsd_products_support_series_home.html

Additional Related Documentation for Cisco MDS 9000

The documentation set for the Cisco MDS 9000 Family includes the following documents. To find a document online, use the Cisco MDS NX-OS Documentation Locator at: http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/roadmaps/doclocater.htm

Release Notes

Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Releases Cisco MDS 9000 Family Release Notes for MDS SAN-OS Releases Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images

Regulatory Compliance and Safety Information

Regulatory Compliance and Safety Information for the Cisco MDS 9000 Family

Compatibility Information

Cisco Data Center Interoperability Support Matrix Cisco MDS 9000 NX-OS Hardware and Software Compatibility Information and Feature Lists Cisco MDS 9000 Family Switch-to-Switch Interoperability Configuration Guide

Hardware Installation

Cisco MDS 9500 Series Hardware Installation Guide

Cisco DCNM Fundamentals Guide, Release 6.x

lxvi

OL-25174-02

Preface

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco MDS 9200 Series Hardware Installation Guide Cisco MDS 9100 Series Hardware Installation Guide Cisco MDS 9124 and Cisco MDS 9134 Multilayer Fabric Switch Quick Start Guide

Software Installation and Upgrade

Cisco MDS 9000 NX-OS Software Upgrade and Downgrade Guide

Cisco NX-OS

Cisco MDS 9000 Family NX-OS Licensing Guide Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide Cisco MDS 9000 Family NX-OS System Management Configuration Guide Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide Cisco MDS 9000 Family NX-OS Fabric Configuration Guide Cisco MDS 9000 Family NX-OS Quality of Service Configuration Guide Cisco MDS 9000 Family NX-OS Security Configuration Guide Cisco MDS 9000 Family NX-OS IP Services Configuration Guide Cisco MDS 9000 Family NX-OS Intelligent Storage Services Configuration Guide Cisco MDS 9000 Family NX-OS High Availability and Redundancy Configuration Guide Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide Cisco MDS 9000 Family Cookbook for Cisco MDS SAN-OS

Command-Line Interface

Cisco MDS 9000 Family Command Reference

Intelligent Storage Networking Services Configuration Guides

Cisco MDS 9000 Family I/O Acceleration Configuration Guide Cisco MDS 9000 Family SANTap Deployment Guide Cisco MDS 9000 Family Data Mobility Manager Configuration Guide Cisco MDS 9000 Family Storage Media Encryption Configuration Guide

Troubleshooting and Reference

Cisco MDS 9000 Family and Nexus 7000 Series System Messages Reference Cisco MDS 9000 Family SAN-OS Troubleshooting Guide Cisco MDS 9000 Family NX-OS MIB Quick Reference

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

lxvii

Preface

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM for SAN Database Schema Reference

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly Whats New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Subscribe to the Whats New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Cisco DCNM Fundamentals Guide, Release 6.x

lxviii

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Introduction to Cisco Data Center Network Manager

Cisco Data Center Network Manager (DCNM) is a management system for the Cisco Unified Fabric. It enables you to provision, monitor, and troubleshoot the data center network infrastructure. It provides visibility and control of the unified data center so that you can optimize for the quality of service (QoS) required to meet service-level agreements. Cisco DCNM increases overall data center infrastructure uptime and reliability, thereby improving business continuity. It provides a robust framework and comprehensive feature set that meets the routing, switching, and storage administration needs of data centers. Cisco DCNM streamlines the provisioning for the unified fabric and monitors the SAN and LAN components. Cisco DCNM provides a high level of visibility and control through a single web-based management console for Cisco Nexus, Cisco MDS, and Cisco Unified Computing System products. Cisco DCNM also supports the installation of the Cisco DCNM for SAN and Cisco DCNM for LAN components with a single installer. The following documentation changes support the merged Cisco DCNM product:

Cisco DCNM product documentation for Cisco DCNM Release 5.2 is retitled with the name Cisco DCNM for LAN. Cisco Fabric Manager product documentation for Cisco DCNM Release 5.2 is retitled with the name Cisco DCNM for SAN.

All Cisco DCNM for SAN and Cisco DCNM for LAN product documentation is now published to the Data Center Network Manager listing page on Cisco.com: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_configure.html

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

lxix

Introduction to Cisco Data Center Network Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

lxx

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

PA R T

Cisco Data Center Network Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

Cisco DCNM Fundamentals Overview

This chapter provides an overview of the basic Cisco DCNM-SAN components and includes the following sections:

DCNM-SAN Server, page 1-1 Authentication in DCNM-SAN Client, page 1-3 DCNM-SAN Client, page 1-1 Device Manager, page 1-2 DCNM-SAN Web Client, page 1-2 Performance Manager, page 1-3 Cisco Traffic Analyzer, page 1-3 Network Monitoring, page 1-4 Performance Monitoring, page 1-4

DCNM-SAN Server
DCNM-SAN Server is a platform for advanced MDS monitoring, troubleshooting, and configuration capabilities. DCNM-SAN Server provides centralized MDS management services and performance monitoring. SNMP operations are used to efficiently collect fabric information. The Cisco DCNM-SAN software, including the server components, requires about 60 MB of hard disk space on your workstation. Cisco DCNM-SAN Server runs on Windows 2000, Windows 2003, Windows 2008, Windows XP, Windows 7, Solaris 9 and 10, and Red Hat Enterprise Linux AS Release 5. Each computer configured as a Cisco DCNM-SAN Server can monitor multiple Fibre Channel SAN fabrics. Up to 16 clients (by default) can connect to a single Cisco DCNM-SAN Server concurrently. The Cisco DCNM-SAN Clients can also connect directly to an MDS switch in fabrics that are not monitored by a Cisco DCNM-SAN Server, which ensures that you can manage any of your MDS devices from a single console.

DCNM-SAN Client
Cisco DCNM-SAN Client is a Java and SNMP-based network fabric and device management tool with a GUI that displays real-time views of your network fabric, including Cisco Nexus 5000 Series switches, Cisco MDS 9000 Family switches and third-party switches, hosts, and storage devices.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

1-1

Chapter 1

Cisco DCNM Fundamentals Overview

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DCNM-SAN Client provides Fibre Channel troubleshooting tools, in addition to complete configuration and status monitoring capabilities for Cisco MDS 9000 Family switches and Cisco Nexus 5000 Series switches. You can use these health and configuration analysis tools on the MDS 9000 Family switch or Cisco Nexus 5000 Series switch to perform Fibre Channel ping and traceroute. Fabric Manager Release 4.1(1b) and later releases provide a multilevel security system by adding a server admin role that allows access to limited features. The configuration capabilities of a server admin is limited to configuring FlexAttach and relevant data. Advanced mode option is available only for network administrators and provides all of the DCNM-SAN features, including security, IVR, iSCSI, and FICON.

Device Manager
Device Manager provides a graphical representation of a Cisco MDS 9000 Family switch chassis or Cisco Nexus 5000 Series switch chassis, including the installed switching modules, the supervisor modules, the status of each port within each module, the power supplies, and the fan assemblies. The tables in the DCNM-SAN Information pane basically correspond to the dialog boxes that appear in Device Manager. However, while DCNM-SAN tables show values for one or more switches, a Device Manager dialog box shows values for a single switch. Device Manager also provides more detailed information for verifying or troubleshooting device-specific configuration than DCNM-SAN. Device Manager provides two views: Device View and Summary View. Use Summary View to monitor interfaces on the switch. Use Device View to perform switch-level configurations including the following configurations:

Configuring virtual Fibre Channel interfaces Configuring Fibre Channel over Ethernet (FCoE) features Configuring zones for multiple VSANs Managing ports, PortChannels, and trunking Managing SNMPv3 security access to switches Managing CLI security access to the switch Managing alarms, events, and notifications Saving and copying configuration files and software image Viewing hardware configuration Viewing chassis, module, port status, and statistics

DCNM-SAN Web Client

With DCNM-SAN Web Client you can monitor Cisco MDS switch events, performance, and inventory from a remote location using a web browser.

Performance Manager Summary reportsThe Performance Manager summary report provides a high-level view of your network performance. These reports list the average and peak throughput and provides hot-links to additional performance graphs and tables with additional statistics. Both tabular and graphical reports are available for all interconnections monitored by Performance Manager.

Cisco DCNM Fundamentals Guide, Release 6.x

1-2

OL-25174-02

Chapter 1

Cisco DCNM Fundamentals Overview

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Performance Manager drill-down reportsPerformance Manager can analyze daily, weekly, monthly and yearly trends. You can also view the results for specific time intervals using the interactive zooming functionality. These reports are only available if you create a collection using Performance Manager and start the collector. Zero maintenance database for statistics storageNo maintenance is required to maintain Performance Managers round-robin database, because its size does not increase over time. At prescribed intervals the oldest samples are averaged (rolled-up) and saved. A full two days of raw samples are saved for maximum resolution. Gradually the resolution is reduced as groups of the oldest samples are rolled up together.

Performance Manager
The primary purpose of DCNM-SAN is to manage the network. A key management capability is network performance monitoring. Performance Manager gathers network device statistics historically and provides this information graphically using a web browser. Performance Manager presents recent statistics in detail and older statistics in summary. Performance Manager also integrates with external tools such as Cisco Traffic Analyzer. Performance Manager has three operational stages:

DefinitionThe Flow Wizard sets up flows in the switches. CollectionThe Web Server Performance Collection screen collects information on desired fabrics. PresentationGenerates web pages to present the collected data through DCNM-SAN Web Server.

Performance Manager can collect statistics for ISLs, hosts, storage elements, and configured flows. Flows are defined based on a host-to-storage (or storage-to-host) link. Performance Manager gathers statistics from across the fabric based on collection configuration files. These files determine which SAN elements and SAN links Performance Manager gathers statistics for. Based on this configuration, Performance Manager communicates with the appropriate devices (switches, hosts, or storage elements) and collects the appropriate information at fixed five-minute intervals.

Authentication in DCNM-SAN Client

Administrators launch DCNM-SAN Client and select the seed switch that is used to discover the fabric. The user name and password are passed to DCNM-SAN Server and are used to authenticate to the seed switch. If this user name and password are not a recognized SNMP user name and password, either DCNM-SAN Client or DCNM-SAN Server opens a CLI session to the switch (SSH or Telnet) and retries the user name and 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 DCNM-SAN Client and DCNM-SAN Server.

Cisco Traffic Analyzer

Cisco Traffic Analyzer provides real-time analysis of SPAN traffic or analysis of captured traffic through a Web browser user interface. Traffic encapsulated by one or more Port Analyzer Adapter products can be analyzed concurrently with a single workstation running Cisco Traffic Analyzer, which is based on ntop, a public domain software enhanced by Cisco for Fibre Channel traffic analysis.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

1-3

Chapter 1

Cisco DCNM Fundamentals Overview

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Cisco Traffic Analyzer monitors round-trip response times, SCSI I/Os per second, SCSI read or traffic throughput and frame counts, SCSI session status, and management task information. Additional statistics are also available on Fibre Channel frame sizes and network management protocols.

Network Monitoring
DCNM-SAN provides extensive SAN discovery, topology mapping, and information viewing capabilities. DCNM-SAN collects information on the fabric topology through SNMP queries to the switches connected to it. DCNM-SAN recreates a fabric topology, presents it in a customizable map, and provides inventory and configuration information in multiple viewing options such as fabric view, device view, summary view, and operation view. Once DCNM-SAN is invoked, a SAN discovery process begins. Using information polled from a seed Cisco MDS 9000 Family switch, including Name Server registrations, Fibre Channel Generic Services (FC-GS), Fabric Shortest Path First (FSPF), and SCSI-3, DCNM-SAN automatically discovers all devices and interconnects on one or more fabrics. All available switches, host bus adapters (HBAs), and storage devices are discovered. The Cisco MDS 9000 Family switches use Fabric-Device Management Interface (FMDI) to retrieve the HBA model, serial number and firmware version, and host operating-system type and version discovery without host agents. DCNM-SAN gathers this information through SNMP queries to each switch. The device information discovered includes device names, software revision levels, vendor, ISLs, PortChannels, and VSANs.

Performance Monitoring
DCNM-SAN and Device Manager provide multiple tools for monitoring the performance of the overall fabric, SAN elements, and SAN links. These tools provide real-time statistics as well as historical performance monitoring. Real-time performance statistics are a useful tool in dynamic troubleshooting and fault isolation within the fabric. Real-time statistics gather data on parts of the fabric in user-configurable intervals and display these results in DCNM-SAN and Device Manager. Device Manager provides an easy tool for monitoring ports on the Cisco MDS 9000 Family switches. This tool gathers statistics at a configurable interval and displays the results in tables or charts. These statistics show the performance of the selected port in real-time and can be used for performance monitoring and troubleshooting. For a selected port, you can monitor any of a number of statistics including traffic in and out, errors, class 2 traffic, and FICON data. You can set the polling interval from ten seconds to one hour, and display the results based on a number of selectable options including absolute value, value per second, and minimum or maximum value per second.

Cisco DCNM Fundamentals Guide, Release 6.x

1-4

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

Cisco DCNM Web Client

This chapter describes various Cisco MDS and Nexus family switch features such as performance and inventory that you can monitor from a remote location using a web browser. This chapter includes the following sections:Information About Cisco DCNM Web Client, page 2-1 Discovering Switches, page 2-9 Licensing Advanced Features, page 1-13 Viewing Health Information, page 2-22 Viewing Performance Information, page 2-23 Viewing Inventory Information, page 2-32 Configuring Backups Using Cisco DCNM Web Client, page 2-36 Administering Cisco DCNM Web Client, page 2-43

Information About Cisco DCNM Web Client

Using Cisco DCNM Web Client, you can monitor Cisco MDS and Nexus family switch events, performance, and inventory, and perform minor administrative tasks. Cisco DCNM Web Client provides the following features:

Downloading Cisco DCNM-SAN Client, page 2-5. Cisco DCNM Web Client GUI, page 2-5. Discovering Switches, page 2-9. Licensing Advanced Features, page 2-12. Viewing Health Information, page 2-22. Viewing Performance Information, page 2-23. Viewing Inventory Information, page 2-32. Configuring Backups Using Cisco DCNM Web Client, page 2-36. Viewing and Creating Custom Reports, page 2-39. Administering Cisco DCNM Web Client, page 2-43. Using Cisco DCNM Web Client with SSL, page 2-66.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-1

Chapter 2 Information About Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Summary dashboard
The summary dashboard provides a quick view of Inventory, Health, Daily Performance, Top Hosts, Top Storage, Federation and Topology in separate windows. It provides performance trading of switches with visibility into traffic fluctuations and helps to establish baseline traffic patterns. You can double-click the dashboard to expand a window for a detailed view of individual network components. The dashboard also summarizes the information needed to manage the virtual environment including performance charts, inventory information, events, and virtual machine, and VMware ESX utilization information. From the tooltips link, click the icon to view the 24-hour performance chart of the link.

Host dashboard
The host dashboard provides you with all the information related to the discovered SAN and LAN hosts. The host dashboard provides detailed information related to the network, such as I/O traffic, disk latency, CPU, memory statistics, topology, and events about each individual host and virtual machines that are configured on top of the virtual host. The host dashboard consists of four panels:
Host panelList the hosts and their network attributes. Chart panelProvides the I/O statistics, CPU and memory information, and disk latency of

individual hosts or virtual machines.

Topology panelProvides end-to-end topology layout and path information between host

enclosures and storage enclosures. The discovered virtual machines are displayed and when you select the virtual machine, the path to the SAN data source is displayed. You can toggle this view to list all data paths.
Event panelProvides information about events of all of the switch ports that are configured

with a specific host enclosure.

Switch Dashboard
The switch dashboard enables you to view the details of the switch including the system information, switch capacity, modules, interfaces, and licenses.

Summary and drill-down reports

The Performance Manager summary report provides a high-level view of your network performance. These reports list the average and peak throughput and provides links to additional performance graphs and tables with additional statistics. Both tabular and graphical reports are available for all interconnections monitored by Performance Manager. Performance Manager also analyzes daily, weekly, monthly, and yearly trends. You can also view the results for specific time intervals using the interactive zooming functionality. These reports are only available if you create a collection using Performance Manager and start the collector.

Cisco DCNM Fundamentals Guide, Release 6.x

2-2

OL-25174-02

Chapter 2

Cisco DCNM Web Client Information About Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Zero maintenance database for statistics storage

No maintenance is required to maintain Performance Managers round-robin database, because its size does not grow over time. At prescribed intervals, the oldest samples are averaged (rolled-up) and saved. By default, full two days of raw samples are saved for maximum resolution. The resolution gradually is reduced as groups of the oldest samples are rolled up together. This section includes the following topics:

Navigating DCNM Web Client, page 2-3 Launching Cisco DCNM Web Client, page 2-4 Downloading Cisco DCNM-SAN Client, page 2-5 Cisco DCNM Web Client GUI, page 2-5 Viewing Dashboard Summary Information, page 1-5 Cisco DCNM Web Search Engine, page 2-8

Navigating DCNM Web Client

With most screens, DCNM Web Client has standardized certain navigation conventions.

Scope Menu
You can use the scope menu to filter network information as follows:

Choose SAN to view information for the contained fabrics. You can organize your fabrics and LAN switches in the Admin > Groups page.

The features accessible from the tabs are limited to the areas that you choose in the filter tree.

Table Filtering and Navigation

You can filter the display of some tables to view subsets of the information. Either choose the filter menu or click Filter. An editable row at the top of the table appears. Enter values into the table cells and click Return to display matching rows.

Printing
Click Print to view the table in a printer-friendly format. You can then print the page from the browser.

Exporting to a File
An Export icon is in the lower right corner of some tables. Click this icon to export the data to Microsoft Excel.

Sorting Columns
On some table columns, you can click a column head to sort the information for that column.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-3

Chapter 2 Information About Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Launching Cisco DCNM Web Client

Before you can use Cisco DCNM Web Client to monitor a switch, the service must be started on the server you are connecting through. The browser does not have to be on the same workstation where DCNM Web Client is installed.
Step 1

DETAILED STEPSIf you are on the same workstation where you installed Cisco DCNM Web Client, open
your browser and in the Location field, enter http://localhost:PORT. Enter your port number if you specified a different port during installation. You can omit the port number if you used port 80 by default. If you are on a different workstation from where you installed Cisco DCNM Web Client, open your browser and in the Location field, enter http://yourServerAddress:PORT, where yourServerAddress is the address where you installed Cisco DCNM Web Client, and PORT is 80 by default. Enter your port number if you specified a different port during installation.

Tip

On Microsoft windows, choose Start > Control Panel > Administrative Tools > Services to verify that Cisco DCNM Web Client has started. To start Cisco DCNM Web Client, use a browser to go to the location of the service. You can also view this information by using the Admin > Status menu of Cisco DCNM Web Client. On a UNIX workstation, enter the following command:
$ /usr/local/cisco_mds9000/bin/FMServer.sh status

You see the Cisco DCNM Web Client Login dialog box. The text field at the bottom shows the Message of the Day from the server that you logged into.

Step 2 Step 3

Enter your username and password. Click Login.

Note

If you have a new installation of Cisco DCNM-SAN, the default user ID and password is admin/password. We recommend that you change your password the first time that you use Cisco DCNM-SAN Server. If you do not have a new installation, you can use any existing passwords.

You see the Cisco DCNM Web Client window.

Note

If you are using FireFox to access Cisco DCNM Web Client, you might receive a warning message indicating a problem with the security certificate of the website. To resolve this issue, you might need to add the security exception that is described in the next procedure.

Cisco DCNM Fundamentals Guide, Release 6.x

2-4

OL-25174-02

Chapter 2

Cisco DCNM Web Client Downloading Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Downloading Cisco DCNM-SAN Client

You must use Cisco DCNM Web Client to launch Cisco DCNM-SAN Client.
Step 1 Step 2 Step 3

DETAILED STEPSLog on to Cisco DCNM Web Client.

From the top right corner, choose Download. Click the link for Cisco DCNM-SAN client. If you are launching Cisco DCNM-SAN Client for the first time, you see a message asking whether you want to create shortcuts for Cisco DCNM-SAN.

Step 4

Click Yes to create shortcuts for Cisco DCNM-SAN.

Note

This message appears only the first time that you launch Cisco DCNM-SAN Client.

Adding a Security Exception

Step 1 Step 2

DETAILED STEPSOn the warning page, click Or you can add an exception.
Click Add Exception. The Add Security Exception dialog box appears. Click Get Certificate. Read the text that describes the problems with this site. Click Confirm Security Exception.

Step 3

Step 4

Cisco DCNM Web Client GUI

Beginning with Cisco NX-OS Release 6.x, Cisco DCNM Web Client has a few graphical user interface (GUI)-related changes. The new Cisco DCNM Web Client is user experience (UX) 1.7 compliant. See Figure 2-1.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-5

Chapter 2 Cisco DCNM Web Client GUI

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-1 Cisco DCNM Web Client

Viewing Dashboard Summary Information

The Summary Dashboard displays a set of context-dependent pods. You can view the details about data center switches, selected SAN switches, selected LAN switches, a group of SAN switches or LAN switches, or a group of LAN and SAN switches.

Note

The content in each pod depends upon the selected scope. This section includes the following topics:

Viewing Health Summary Information, page 2-6 Viewing Performance Summary Information, page 2-7 Viewing Inventory Summary Information, page 2-7 Viewing Switch Information, page 1-6

Viewing Health Summary Information

Step 1

DETAILED STEPSFrom the menu bar, choose Dashboard > Summary and then double-click the Health
Summary view. You see the Summary window. In the left side of the window, you see a summary table of problems and in the right side of the window, you see a summary table of events for the last 24 hours .

Step 2

Click the warnings next to Switches, ISLs, Hosts, or Storage (other than 0) to see an inventory of switches, ISLs, or end devices for that fabric.

Cisco DCNM Fundamentals Guide, Release 6.x

2-6

OL-25174-02

Chapter 2

Cisco DCNM Web Client Cisco DCNM Web Client GUI

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 3

Choose the number of events next to the event severity levels (Emergency, Alert, Critical, Error, Warning, Notice, Info, or Debug) to see a summary of events and descriptions for that fabric.

Viewing Performance Summary Information

BEFORE YOU BEGIN
To view performance information, you must activate performance collector.
Step 1

DETAILED STEPSFrom the menu bar, choose Dashboard > Summary and then click Daily Performance
view. You see the Summary information.

Viewing Inventory Summary Information

Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Dashboard > Summary.

Double-click the Inventory summary pane. You see the Summary window.

Viewing Switch Information

Cisco DCNM Web Client enables you to view the details of the switch including the system information, switch capacity, modules, interfaces, and licenses.
Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Dashboard > Switches.

An inventory of all the switches that are discovered by Cisco DCNM Web Client appear. Click on a switch in the Name column. The switch dashboard displays the details of the selected switch. The system information area includes the logical name of the switch, the group where the switch belongs,model number of the switch, serial number of the switch, the switch version, the location of the switch, IP address, model, world wide name (WWN), uptime, DCNM license, status of the switch, indicators to determine whether the switch is sending traps and syslog information, current central processor unit (CPU) and memory utilization.

Step 3 Step 4 Step 5 Step 6 Step 7

(Optional) Click ssh to access the switch through Secure Shell (SSH). (Optional) Click Device Manager to access the switch through Hypertext Transfer Protocol (HTTP) for that switch. (Optional) Click Accounting to go to the Accounting page for that switch. (Optional) Click Backup to go to the Configuration view page. (Optional) Click Events to go to the Fabric Events page.

Note

This physical port capacity feature is available for Cisco DCNM licensed switches only.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-7

Chapter 2 Cisco DCNM Web Client GUI

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The physical port capacity area includes the available ports in each tier, such as 40G, 10G, 8G, 4G, 2G, and 1G and also the predicted number of days remaining to reach the maximum (100%) utilization.
Step 8 Step 9 Step 10

Click a number under the Days left column to view the capacity trend. Choose the Modules tab to display all the modules that are discovered on the switch. Choose the Interfaces tab to display all the interfaces that are discovered for the switch. Click the icon next to the interface name to view the 24-hour performance data of the interface. When you click on a link in the ConnectedTo column, you see the other end of where the the interface is connected. For example, if the other end of the interface is a switch interface, then it launches the Interfaces tab of the switch that the interface is connected. If the interface is connected to a end device, then it lauches the host or storage dashboard. If it is connectedto another switch interface, then it launches the Switch dashboard->Interfaces tab of the switch that it is connected to. If connected to end device then it launches the Host or Storage dashboard filtered by the connected Enclosure. Choose the Licenses tab to display all the licenses installed on the switch. Choose the Features tab to display a list of all the features installed on the switch.

Step 11

Step 12 Step 13

Note

The features tab is displayed only on Cisco DCNM-SAN switches.

Cisco DCNM Web Search Engine

The search engine helps you to locate records that match a specific criteria. The search entity is divided into two categories: inventory and performance. In the inventory type, you can search by the switch (name of the switch, IP address of the switch, and WWN), Endport (alias, IP address of the switch and WWN) and VSANs (name of the VSAN, IP address of the principal switch, and WWN). In the performance type, you can search by the end device (Endport alias, Endport WWN), MAC address, serial number, Flow (name of the flow), and ISLs (name of the ISL, and WWN of the ISL). You can also use wildcard characters in the search.

Using the Cisco DCNM Search Engine

Step 1

DETAILED STEPSClick Search box on the top-right corner of the main window.
You see the search text box. In the text box, enter the name to search. Click the search icon on the right side of the text box to start searching, and choose the appropriate radio button. A window appears with your results. Click the entity type to see the details. You see the details of the selected entity in the right pane.

Step 2 Step 3

Step 4

Cisco DCNM Fundamentals Guide, Release 6.x

2-8

OL-25174-02

Chapter 2

Cisco DCNM Web Client Discovering Switches

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Discovering Switches
This feature enables you to discover the various Cisco devices (Cisco MDS Family switches, Cisco NX-OS devices, and Catalyst switches) from a single interface. When a discovery task succeeds, Cisco DCNM retrieves the running configuration and status information of the discovered Cisco NX-OS devices. Use this procedure for the following purposes:

To discover the Cisco LAN and SAN devices. To view the task details for the common LAN discovery. To discover devices that are not currently managed by Cisco DCNM. For example, you should use this procedure when Cisco DCNM has not yet discovered any devices, such as after a new installation. To discover devices that you have added to your network without rediscovering devices that Cisco DCNM already has discovered. To rediscover the topology when Cisco Discovery Protocol (CDP) links have changed, without rediscovering devices that Cisco DCNM has already discovered. To move the discovered LAN task to a different Cisco DCNM server in the federation.

Note

You must successfully discover a Cisco NX-OS device before you can use Cisco DCNM to configure the device. This section includes the following topics:

Discovering a Cisco Device, page 2-9 Rediscovering a Device, page 1-11Rediscovering a Device, page 2-11 Managing LAN Devices, page 2-11 Removing LAN Devices, page 2-11 Modifying LAN Devices, page 2-12 Moving LAN Devices, page 2-12

Discovering a Cisco Device

BEFORE YOU BEGIN
Ensure that you have configured the Cisco NX-OS device so that the Cisco DCNM server can connect to it and successfully discover it. Create an SNMP user. Determine the IPv4 address of the device that you want Cisco DCNM to connect to when it starts the discovery task. This is the seed device for the discovery. Determine whether you want to discover devices that are CDP neighbors of the seed device. If so, determine the maximum number of hops from the seed device that the discovery process can make.

Note

The discovery process can perform a complete discovery of neighbors only if the neighboring devices are configured with the same credentials as the seed device.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-9

Chapter 2 Discovering Switches

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 1

DETAILED STEPSFrom the Feature Selector pane, choose Admin > General > Data Sources.
The discovery tasks appear in the Fabric and LAN panes. Discover the LAN devices, and click on the + icon on the top right corner. The Add LAN Data Source window appears. In the Add LAN Data Source window, click Hops from seed switch in the Discovery Type field to set the common LAN discovery by hops, click Switch List to set the common LAN discovery by switch range, click FWSM to choose the firewall service module, or click FWSM to set the common LAN discovery for FireWall task. If you click the Hops from seed switch radio button, enter the seed switch IP in the Seed Switch field. If you click the Switch List radio button, enter the list of switch IP addresses or range in the Seed Switch field. For example, 172.22.31.111, 172.22.34.100-105. If you choose the Max Hops from Seed or Switch List, enter the user credentials with the option of SNMPV1 or SNMPV3. If you choose FWSM, choose the group.

Step 2

Step 3

Step 4

Step 5

Note

For a deep discovery of DCNM-LAN devices, choose SNMPV3. To enable a deep discovery for individual LAN devices, use the Edit LAN Task dialog box. From the discovery timeout drop-down, choose the time in seconds, enter the user credentials, and choose Group. Click Next. The Shallow LAN Discovery window appears. In the Shallow LAN Discovery window, choose one or more switches for LAN discovery.

Step 6 Step 7

Step 8

Note

Unknown, unsupported, unreachable, or failed authentication switches are displayed but you cannot choose them. (Optional) You can click Previous to run the discovery again with an increased timeout, or to increase or decrease the number of hops. Click Add. The selected switches are added to the new LAN discovery. Wait until the status for the task is Successful. This step might take several minutes. After the status is Successful, you can use Cisco DCNM to configure and monitor the discovered devices. At this state, DCNM-SAN has completed the shallow discovery for the LAN devices. You do not need to save your changes. The discovered switches are added to the group. View the added device under each switch by expanding the entry. The group for each Ethernet switch can be viewed and changed individually. View the status of the discovery tasks by choosing the Discovery Task and Device Credentials tab in the task pane.

Step 9 Step 10 Step 11

Step 12 Step 13

Cisco DCNM Fundamentals Guide, Release 6.x

2-10

OL-25174-02

Chapter 2

Cisco DCNM Web Client Discovering Switches

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
RELATED TOPICS
Rediscovering a Device, page 2-11Rediscovering a Device You can rediscover one or more devices.

Note

Rediscovery replaces any configuration data that Cisco DCNM has for a Cisco NX-OS device with new configuration data that is retrieved during the rediscovery. If you need to discover one or more devices without retrieving configuration and status information for already discovered devices, see the Discovering a Cisco Device section on page 2-9. You must successfully discover a Cisco NX-OS device before you can use Cisco DCNM to configure the device.

BEFORE YOU BEGIN

Ensure that you have configured the Cisco NX-OS device so that the Cisco DCNM server can connect to it.
Step 1

DETAILED STEPSFrom the Feature Selector pane, choose Admin > General > Data Sources.
The discovery tasks and their status appear in the Discovery Tasks area of the Discovery Tasks pane. Select the discovery task that needs to be rediscovered. Click Rerun to start the rediscovery process.

Step 2 Step 3

Managing LAN Devices

You can manage a LAN from Cisco DCNM Web Client.
Step 1

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
You see the list of LANs (if any) that are managed by Cisco DCNM-SAN. Click Add. You see the Add LAN CDP Seed dialog box. Enter the CDP seed switch IP address. (Optional) Check the SNMPV3 check box. If you check SNMPV3, the Community field changes to Username and Password. You must enter your username and password. Enter the username and password for this LAN. Click Add to begin managing this LAN.

Step 2

Step 3 Step 4 Step 5 Step 6

Removing LAN Devices

You can remove a LAN from Cisco DCNM Web Client.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-11

Chapter 2 Licensing Advanced Features

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
Check the check box next to the LAN that you want to remove and click Remove to discontinue data collection for that LAN.

Modifying LAN Devices

You can modify a LAN from Cisco DCNM Web Client.
Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
Check the check box next to the LAN that you want to edit and click Edit. You see the Edit LAN CDP Seed dialog box. Enter a new LAN name, username and password, privacy settings and specify how you want Cisco DCNM Web Client to manage the fabric by selecting one of the status options. Click Apply to save the changes.

Step 3 Step 4

Moving LAN Devices

You can move LAN devices to a different server using Cisco DCNM Web Client.
Step 1 Step 2 Step 3

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
Choose the fabrics from the fabric table. Click Move Fabrics to another Federation Server or Move LAN Tasks to another DCNM Server. Choose the fabrics that need to be moved and click Move Fabric. In the Move Fabrics to another Federation server dialog box, choose the DCNM server where the fabrics will be moved. The server drop-down list will list only the active servers. In the Move LAN Tasks to another DCNM Server dialog box, enter the LAN tasks that need to be moved and specify the DCNM server. Note the following:

Step 4

This feature is available on the federation setup and the Move Fabric is displayed in the federation setup screen. You can move the fabrics from a sever that is down to an active server. The management state remains the same.

Licensing Advanced Features

This section includes the following topics:

Cisco DCNM-LAN Features, page 2-13 Cisco DCNM-SAN Features, page 2-15 Cisco DCNM Server-Based Licenses, page 2-17 Installing Cisco DCNM Licenses, page 1-18 Viewing Licenses Using the Cisco DCNM Wizard, page 2-18

Cisco DCNM Fundamentals Guide, Release 6.x

2-12

OL-25174-02

Chapter 2

Cisco DCNM Web Client Licensing Advanced Features

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Managing Licenses, page 1-21

Cisco DCNM-LAN Features

Table 2-1 displays the Cisco DCNM-LAN features. .
Table 2-1 Cisco DCNM-LAN Features

Feature Port/port channel Static port pinning Link Aggregation Control Protocol (LACP) VLAN 802.1q/P VLAN Spanning Tree Protocol (STP) (Multiple Spanning Tree (MST), Rapid per VLAN Spanning Tree (RPSVT) Access control list (ACL) (MAC, IP, VLAN) Port security Traffic storm control IGMP snooping AAA Environmental (HwRes Utilization with ternary content addressable memory (TCAM) statistics) Module temperature Switched Port Analyzer (SPAN) Discovery and inventory

DCNM Advanced DCNM Essential Edition (Licensed) Edition (Free)

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-13

Chapter 2 Licensing Advanced Features

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 2-1 Cisco DCNM-LAN Features (continued)

Feature Fault management (filtering, TCA, and actions) Traffic statistics reports Role-based Access Control (RBAC) Port profile Template center Web services and Java API Virtual port channels (vPCs) 802.1X Gateway Load-Balancing Protocol (GLBP) Object tracking Keychain management DHCP snooping Dynamic ARP Inspection ARP access control lists (ACLs) IP Source Guard Traffic storm control Port security

DCNM Advanced DCNM Essential Edition Edition (Free) (Licensed)

Cisco DCNM Fundamentals Guide, Release 6.x

2-14

OL-25174-02

Chapter 2

Cisco DCNM Web Client Licensing Advanced Features

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 2-1 Cisco DCNM-LAN Features (continued)

Feature IP tunnels Virtual device contexts (VDCs) Logical vPC view of the Topology feature Display of historical statistical data FabricPath Host tracking

DCNM Advanced DCNM Essential Edition Edition (Free) (Licensed)

Note

Cisco DCNM requires licenses only for Cisco Nexus 7000, 5000, and 3000 Series switches and do not require licenses for Cisco Nexus 4000, 1000V, and Cisco Catalyst 6500 series switches. To purchase licenses for all the advanced edition features, see Cisco DCNM Release Notes, Release 6.x.

Cisco DCNM-SAN Features

Table 2-2 displays the Cisco DCNM-SAN features that are free and licensed.
Table 2-2 Cisco DCNM-SAN Features

Feature FC/FCoE/FICON/iSCSI topology view Fabric, device, and summary views Port, switch, and fabric-level configuration MDS event and secuity management

DCNM Essential Edition (Free)

DCNM Advanced Edition (Licensed)

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-15

Chapter 2 Licensing Advanced Features

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 2-2 Cisco DCNM-SAN Features (continued)

Feature Configuration wizards MDS configuration analysis tool Network diagnostic and troubleshooting tools Real-time performance monitoring Multiple fabric management (concurrently) Centralized management server with discovery Web Client for operational view Continuous health and event monitoring Historical performance monitoring and reporting Event forwarding Cisco DCNM proxy services Cisco Fabric Analyzer integration Roaming user profiles VMpath analytics Dashboards (Summary, host, switch, network)

DCNM Essential Edition (Free)

DCNM Advanced Edition (Licensed)

Note

Cisco DCNM requires licenses only for Cisco Nexus 7000, 5000, and 3000 Series switches and do not require licenses for Cisco Nexus 4000, 1000V, and Cisco Catalyst 6500 series switches. To purchase licenses for all the advanced edition features, see Cisco DCNM Release Notes, Release 6.x.

Cisco DCNM Fundamentals Guide, Release 6.x

2-16

OL-25174-02

Chapter 2

Cisco DCNM Web Client Licensing Advanced Features

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Server-Based Licenses

Table 2-3 displays the Cisco DCNM server-based licenses.
Table 2-3 Cisco DCNM Server-Based Licenses

Platform MDS 9200 MDS 9100 MDS 9500 Nexus 7000 SAN Nexus 5000 SAN Nexus 7000 LAN Nexus 5000 L/S Nexus 5000 LAN Nexus 3000 LAN

Paper PIDs (comes in envelope) DCNM-SAN-M92-K9= DCNM-SAN-M91-K9= DCNM-SAN-M95-K9= DCNM-SAN-N7K-K9= DCNM-SAN-N5K-K9= DCNM-N7K-K9= DCNM-LS-N5K-K9= DCNM-LAN-N5K-K9= DCNM-LAN-N3K-K9=

eDelivery PIDs (email) L-DCNM-S-M92-K9= L-DCNM-S-M91-K9= L-DCNM-S-M95-K9= L-DCNM-S-N7K-K9= L-DCNM-S-N5K-K9= L-DCNM-N7K-K9= L-DCNM-LS-N5K-K9= L-DCNM-L-N5K-K9= L-DCNM-L-N3K-K9=

Services PIDs (yearly subscription) CON-SAU-SM92K9 CON-SAU-SM91K9 CON-SAU-SM95K9 CON-SAU-N7SDCN M CON-SAU-N5SDCN M CON-SAU-N7DCNM CON-SAU-N5LSDC NM CON-SAU-N5DCNM CON-SAU-N5DCNM

Installing Cisco DCNM Licenses

BEFORE YOU BEGIN
You must have network administrator privileges to complete the following procedure.
Step 1 Step 2

DETAILED STEPSChoose Admin > License to start the license wizard.

Choose the Server License Files tab (see Figure 2-2). The valid Cisco DCNM-LAN and DCNM-SAN license files appears.

Note

Ensure that the security agent is disabled when you load licenses.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-17

Chapter 2 Licensing Advanced Features

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-2 Installing Cisco DCNM Licenses

Download the license pack file that you received from Cisco into a directory on the server system.
Step 3

Click Add License File.

Note

Ensure that you do not edit the contents of the .lic file or the Cisco DCNM software ignores any features that are associated with that license file. The contents of the file are signed and must remain intact. When you accidentally copy, rename, or insert the license file multiple times, the duplicate files are ignored, but the original will be counted.

Viewing Licenses Using the Cisco DCNM Wizard

You can view the existing Cisco DCNM licenses.
Step 1

DETAILED STEPSChoose Admin > License to start the license wizard.

Figure 2-3 displays the license information.

Cisco DCNM Fundamentals Guide, Release 6.x

2-18

OL-25174-02

Chapter 2

Cisco DCNM Web Client Licensing Advanced Features

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-3 Cisco DCNM Licenses

Note

By default, the Switch Licenses tab appears.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-19

Chapter 2 Licensing Advanced Features

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 2-4 displays the Cisco DCNM server license fields.
Table 2-4 Cisco DCNM Server License Files

Field File Name Feature

Description Name of the license file. Describes the feature name specified in the license file. The following values are supported:

DCNM-LAN DCNM-SAN DCNM-SAN-LAN LAN-ENT-N7K

PID

Describes the product ID found in the vendor string of the license file. For example, DCNM-N7K-K0 is an enterprise license for Cisco Nexus 7000 Series switches. Lists the number of SAN licenses used and that are available. Lists the number of LAN licenses used and that are available. Displays the expiry date of the license.

SAN (Free or Total) LAN (Free or Total) Eval Expiration

Note

Text in the eval expiration field will be in red for licenses that expire in seven days.

Table 2-5 displays the Cisco DCNM switch license fields.

Table 2-5 Cisco DCNM Switch Licenses

Field Group Switch Name Model License State

Description Displays if it is a fabric or a LAN group. Displays the name of the switch. Displays the model of the device. For example, DS-C9124 or N5K-C5020P-BF. Displays the license state of the switch that can be one of the following:

Permanent Eval Unlicensed License Not Supported Expired Invalid

Cisco DCNM Fundamentals Guide, Release 6.x

2-20

OL-25174-02

Chapter 2

Cisco DCNM Web Client Licensing Advanced Features

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 2-5 Cisco DCNM Switch Licenses (continued)

Field License Type Eval Expiration

Description Displays if the license is a switch-based embedded license or a server-based license. Displays the expiry date of the license.

Note

Text in the eval expiration field will be in Red for licenses that expires in seven days.

Managing Licenses
This section includes the following topics:

Adding Cisco DCNM Licenses, page 2-21 Assigning Licenses, page 2-21 Unassigning Licenses to a Switch, page 2-22

Adding Cisco DCNM Licenses

BEFORE YOU BEGIN
You must have network administrator privileges to complete the following procedure.
Step 1

DETAILED STEPSChoose Admin > License to start the license wizard.

You see the licenses table. Click on the Server License File tab. Click Add License File. Browse to the directory where you have stored the license file and add the license file. After the licenses are added, assign the licenses to existing switches. For switches that are yet to be discovered, licenses are automatically assigned.

Step 2 Step 3

Assigning Licenses
BEFORE YOU BEGIN
You must have network administrator privileges to complete the following procedure.
Step 1

DETAILED STEPSChoose Admin > License to start the license wizard.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-21

Chapter 2 Viewing Health Information

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
You see the licenses table.
Step 2 Step 3

From the table, choose the switch that you want to assign the license to. Click Assign License.

Unassigning Licenses to a Switch

BEFORE YOU BEGIN
You must have network administrator privileges to complete the following procedure.
Step 1

DETAILED STEPSChoose Admin > License to start the license wizard.

You see the licenses table. From the table, choose the switch that you want to unassign the license. Click Unassign License.

Step 2 Step 3

Viewing Health Information

The Health menu shows events and issues for the selected items that are persistent across user sessions. The Health menu contains the following submenus:

EventsShows a detailed list of data center events. You can filter these events by scope, date, and type of event. AccountingShows a list of accounting events. Virtual Port Channels (LAN only) Viewing Accounting Information, page 2-22 Viewing Events Information, page 2-22

This section includes the following topics:

Viewing Accounting Information

Step 1

DETAILED STEPSFrom the menu bar, choose Health > Accounting.

You see the accounting window. Expand a fabric and choose one of the switches to display accounting information for that switch.

Step 2

Viewing Events Information

Step 1

DETAILED STEPSFrom the menu bar, choose Health > Events.

You see the Events window. Expand a fabric to display event information for that fabric.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x

2-22

OL-25174-02

Chapter 2

Cisco DCNM Web Client Viewing Performance Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Performance Information

The Performance option shows an overview of the average and peak throughput and link utilization of SAN components. The Filter drop-down list at the top right of the screen allows you to filter the data based on various periods of time. The Performance menu contains the following submenus:

SwitchShows the CPU, memory, and traffic information. End DevicesShows a detailed list of end devices (host or storage), port traffic, and errors. ISLsShows a detailed list of ISL traffic and errors. NPV Links Shows a detailed list of traffic between NPV devices and ports. FlowsShows a detailed list of host-to-storage traffic. EthernetShows a detailed list of Ethernet interfaces. OthersShows a detailed list of other statistics. Virtual Port ChannelsShows a list of vPC utilization. Viewing Switch CPU Information, page 2-23 Viewing Switch Memory Information, page 2-24 Viewing Switch Traffic and Errors Information, page 2-24 Viewing ISL Traffic and Errors Information, page 2-24 Viewing Performance Information on All the Ports, page 2-25 Viewing Performance Information on Host Ports, page 2-25 Viewing Performance Information on Storage Ports, page 2-25 Viewing Performance Information on Host Enclosures, page 2-25 Viewing Performance Information on Storage Enclosures, page 2-25 Viewing Performance Information on Port Groups, page 2-26 Viewing Performance Information for NPV Links, page 2-26 Viewing Performance Information for Flows, page 2-27 Viewing Performance Information for Ethernet Ports, page 2-28 Viewing Other Statistics, page 2-28 Viewing Performance Information for Virtual Port Channels, page 1-30

This section includes the following topics:

Viewing Switch CPU Information

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > Switch > CPU.
You see the CPU pane. This pane displays the CPU information for the switches in that scope. Reduce or expand the scope of what is displayed by using the scope tree on the top of the CPU pane. Click the chart icon in the Switch column to see a graph of the traffic on that device for the past 24 hours.

Step 2 Step 3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-23

Chapter 2 Viewing Performance Information

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Switch Memory Information

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > Switch > Memory.
You see the memory pane. This pane displays the memory information for the switches in that scope. Reduce or expand the scope of what is displayed by using the scope tree on the top of the CPU pane. Click the chart icon in the Switch column to see a graph of the bandwidth information for the end devices in that VSAN.

Step 2 Step 3

Viewing Switch Traffic and Errors Information

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > Switch > Traffic.
You see the Switch Traffic and Errors pane. This pane displays the traffic on that device for the past 24 hours.

Viewing ISL Traffic and Errors Information

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > ISLs/Trunks.

You see the ISL Traffic and Errors pane. This pane displays the ISL information for the end devices in that scope. You can reduce or expand the scope of what is displayed by using the the scope menu. Click the chart icon in the Name column to see a graph of the traffic on that device for the past 24 hours. You see the ISL traffic information window.

Note

Notation NaN (Not a Number) in the data grid means that it is a negative value.

Note

There are variations to this procedure. In addition to these basic steps, you can perform the following steps to view detailed information for ISLs:

To change the time range for this graph, select it from the drop-down list in the upper-right corner. To view the detailed information for a specific period, drag the slider control to choose the time interval for which you need the information. To view information in a grid format, click the grid icon in the bottom right corner. To export the data into a spreadsheet, choose the grid format, and then click on the export to excel link.

Note

By default, numbers are exported in raw, unformatted style. If you want to export numbers as displayed, set the export.unitless=false in the server.properties (or edit Admin > Server Properties) file. Restart the Cisco DCNM server after you export the numbers.

To view real-time information, choose Real Time from the drop-down list in the upper right corner. The real-time data is updated in every 10 seconds.

Cisco DCNM Fundamentals Guide, Release 6.x

2-24

OL-25174-02

Chapter 2

Cisco DCNM Web Client Viewing Performance Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Performance Information on All the Ports

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > End Devices > All Ports.
You see the End Devices window. Reduce or expand the scope of what is displayed by using the scope menu. Click the chart icon in the Name column to see a graph of the traffic on that device for the past 24 hours.

Step 2 Step 3

Viewing Performance Information on Host Ports

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > End Devices > Host Ports.
You see the End Devices window. Reduce or expand the scope of what is displayed by using the scope menu. Click the chart icon in the Name column to see a graph of the traffic on that device for the past 24 hours.

Step 2 Step 3

Viewing Performance Information on Storage Ports

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > End Devices > Storage Ports.
You see the End Devices window. Reduce or expand the scope of what is displayed by using the scope menu. Click the chart icon in the Name column to see a graph of the traffic on that device for the past 24 hours.

Step 2 Step 3

Viewing Performance Information on Host Enclosures

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > End Devices > Host Enclosure.
You see the End Devices window. Reduce or expand the scope of what is displayed by using the scope menu. Click the chart icon in the Name column to see a graph of the traffic on that device for the past 24 hours.

Step 2 Step 3

Viewing Performance Information on Storage Enclosures

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > End Devices > Storage Enclosure.
You see the End Devices window. Reduce or expand the scope of what is displayed by using the scope menu. Click the chart icon in the Name column to see a graph of the traffic on that device for the past 24 hours.

Step 2 Step 3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-25

Chapter 2 Viewing Performance Information

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Performance Information on Port Groups

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > End Devices > Port Groups.
You see the End Devices window. Reduce or expand the scope of what is displayed by using the scope menu. Click the name port group to see the members of that port group.

Step 2 Step 3

Note

There are variations to this procedure. In addition to these basic steps, you can also perform the following steps to view detailed information for the port groups:

To change the time range for this graph, select it from the drop-down list in the upper right corner. To view the detailed information for a specific period, drag the slider control to choose the time interval for which you need the information. To view information in a grid format, click the grid icon in the bottom right corner. To export the data into a spreadsheet, click the excel icon in the upper right corner and then click Save. To view real-time information, choose Real Time from the drop-down list in the upper right corner. The real-time data is updated in every 10 seconds.

Viewing Performance Information for NPV Links

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > NPV Links.
You see the NPV Link and Traffic Errors window. This window displays the NPV links in that scope. Reduce or expand the scope of what is displayed by using the scope menu. Click the chart icon in the Name column to see a list of the traffic for the past 24 hours.

Step 2 Step 3

Note

There are variations to this procedure. In addition to these basic steps, you can also perform the following steps to view detailed information for NPV links:

You can change the time range for this information by selecting it from the drop-down list in the upper-right corner. To view the detailed information for a specific period, drag the slider control to choose the time interval for which you need the information. To view information in a grid format, click the grid icon in the bottom-right corner. To export the data into a spreadsheet, click the excel icon in the upper-right corner and then click Save. To view real-time information, choose Real Time from the drop-down list in the upper right corner. The real-time data is updated in every 10 seconds.

Cisco DCNM Fundamentals Guide, Release 6.x

2-26

OL-25174-02

Chapter 2

Cisco DCNM Web Client Viewing Performance Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Performance Information for Flows

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > Flows.

You see the Flows window. Reduce or expand the scope of what is displayed by using the scope menu. Click the chart icon in the Name column to see a list of the traffic for the past 24 hours.

Step 2 Step 3

Note

There are variations to this procedure. In addition to these basic steps, you can also perform the following steps to view detailed information for flows:

To change the time range for this graph, select it from the drop-down list in the upper right corner. To view the detailed information for a specific period, drag the slider control to choose the time interval for which you need the information. To view information in a grid format, click the grid icon in the bottom right corner. To export the data into a spreadsheet, click the excel icon in the upper right corner and then click Save. To view real-time information, choose Real Time from the drop-down list in the upper right corner. The real-time data is updated in every 10 seconds.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-27

Chapter 2 Viewing Performance Information

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Performance Information for Ethernet Ports

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > Ethernet.

You see the Ethernet window. Reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Note

There are variations to this procedure. In addition to these basic steps, you can also perform the following steps:

Select the time range, and click Filter to filter the display. Select the name of a Ethernet port from the Name column to see a graph of the traffic across that Ethernet port for the past 24 hours. You can change the time range for this graph by selecting it from the drop-down list in the upper right corner.

Viewing Other Statistics

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > Others.

You see the Others window. Reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Note

There are variations to this procedure. In addition to these basic steps, you can also do the following:

Select the time range, and click Filter to filter the display. Select the IP address of a switch from the Name column to see a graph of the traffic across that switch for the past 24 hours. You can change the time range for this graph by selecting it from the drop-down list in the upper right corner.

Note

To configure other statistics, follow the instructions described in the Configuring Other Statistics section on page 2-60.

Viewing Performance Information for Virtual Port Channels

Step 1

DETAILED STEPSFrom the menu bar, choose Performance > Virutal Port Channel (vPC).
You see the vPC window. This window displays the vPC information. Click the print Click the Excel spreadsheet. icon to print the vPC information of the selected device. icon to export the vPC information of the selected device to a Microsoft Excel

Step 2 Step 3

Cisco DCNM Web Client enables you to view the relationship among virtual port channels (vPCs). You can view the statistics of all member interfaces and the aggregate of the statistics at the port channel level.
Step 1

DETAILED STEPSFrom the menu bar, choose Performance > Virtual Port Channel (vPC).

Cisco DCNM Fundamentals Guide, Release 6.x

2-28

OL-25174-02

Chapter 2

Cisco DCNM Web Client Viewing Performance Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The vPC performance statistics appears and the aggregated statistics of all vPCs are displayed in a tabular manner. See Figure 2-4.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-29

Chapter 2 Viewing Performance Information

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-4 Aggregated vPC Statistics View

Step 2 Step 3 Step 4

(Optional) Click the (Optional) Click the

icon to print the vPC performance statistics. icon to export the vPC performance statistics to a Microsoft Excel spreadsheet.

Click on a device name in the Primary vPC Peer or Secondary vPC peer column to view its member interfaces. A popup window displays the member interfaces of the selected device. See Figure 2-5.

Cisco DCNM Fundamentals Guide, Release 6.x

2-30

OL-25174-02

Chapter 2

Cisco DCNM Web Client Viewing Performance Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-5 Member Interfaces Popup Window

Step 5

Click the

icon of the corresponding interface to view its historical statistics.

The traffic distribution statistics appears at the bottom of the vPC window. By default, the Cisco DCNM Web Client displays the historical statistics for 24 hours. See Figure 2-6.
Figure 2-6 Traffic Utilization View

Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12

From the drop-down list, choose a time period, 24 Hours, Week, Month, or Year to view the historical statistics of the selected interface. Click the Click the Click the Click the Click the Click the icon to display the traffic data in the grid view. icon to display the traffic statistics in the line-chart view. icon to display the traffic statistics in the stacked-chart view. icon to predict the traffic statistics. icon to interpolate missing data. icon to close the Traffic area of the selected interface.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-31

Chapter 2 Viewing Inventory Information

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Inventory Information

The Inventory menu shows an inventory of the selected SAN, fabric, or switch. You can export this information to Microsoft Excel. The Inventory menu includes the following submenus:

VSANsShows details about VSANs. SwitchesShows details about switches. LicensesShows details about the licenses in use in the fabric. ModulesShows details for MDS switching and services modules, fans, and power supplies. End DevicesShows the host and storage ports. ISLsShows the Inter-Switch Links. NPV LinksShows the links between NPV devices and ports. Active ZonesShows regular zones and IVR zones.

Note

Beginning with Cisco DCNM release 6.x, you can view the inventory and the performance for both LAN and LAN switches by using the global Scope pane. You can select LAN, SAN, or both to view the inventory information. You can also export and prin t the inventory information. This section includes the following topics:

Viewing Inventory Information for VSANs, page 2-32 Viewing Inventory Information for Switches, page 2-33 Viewing License Information, page 2-33 Viewing Inventory Information for Modules, page 2-33 Viewing Inventory Information for All Ports on End Devices, page 2-33 Viewing Inventory Information for Host Ports on End Devices, page 2-34 Viewing Inventory Information for Storage Ports on End Devices, page 2-34 Viewing Detailed Information for ISLs, page 2-34 Viewing Inventory Information for NPV Links, page 2-34 Viewing Inventory Information for Regular Zones, page 2-34 Viewing Inventory Information for IVR Zones, page 2-35 Viewing Information About Port Mapping, page 1-37

Viewing Inventory Information for VSANs

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > VSANs.

You see the VSAN window. Select one of the fabrics to display VSAN inventory information for that fabric.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x

2-32

OL-25174-02

Chapter 2

Cisco DCNM Web Client Viewing Inventory Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

There are variations to this procedure. In addition to these basic steps, you can also do the following:

Select the status level and then click Filter to filter the display to show all VSANs or only those with errors.

Viewing Inventory Information for Switches

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > Switches.

You see the Switches window. Do one of the following actions:

Step 2

Select a SAN to display switch inventory information for all fabrics in the SAN. Reduce or expand the scope of what is displayed by using the scope menu.

Viewing License Information

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > Licenses.

You see the Switch Licenses window. Reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Note

There are variations to this procedure. In addition to these basic steps, you can also do the following:

Select the status level, and click Filter to filter the display to show all licenses or only those with licenses errors.

Viewing Inventory Information for Modules

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > Modules.

You see the Modules window. Do one of the following:

Step 2

Select a SAN to display module inventory information for all fabrics in the SAN. Reduce or expand the scope of what is displayed by using the scope menu.

Viewing Inventory Information for All Ports on End Devices

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > End Devices > All Ports.
You see the End Devices window. Reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-33

Chapter 2 Viewing Inventory Information

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Inventory Information for Host Ports on End Devices

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > End Devices > Host Ports.
You see the End Devices window. Reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Viewing Inventory Information for Storage Ports on End Devices

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > End Devices > Storage Ports.
You see the End Devices window. You can reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Viewing Detailed Information for ISLs

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > ISLs.

You see the ISLs window. Reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Note

There are variations to this procedure. In addition to these basic steps, you can also perform the following step:

Select the status level, and click Filter to filter the display to show all ISLs or only those ISLs with errors.

Viewing Inventory Information for NPV Links

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > NPV Links.
You see the NPV Links window. Reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Viewing Inventory Information for Regular Zones

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > Active Zones > Regular Zones.
You see the Regular Zones window. Reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x

2-34

OL-25174-02

Chapter 2

Cisco DCNM Web Client Viewing Inventory Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

There are variations to this procedure. In addition to these basic steps, you can also do the following:

Select the status level, and click Filter to filter the display to show all zones or only those zones with errors.

Viewing Inventory Information for IVR Zones

Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > Active Zones > IVR Zones.
You see the IVR Zones window. Reduce or expand the scope of what is displayed by using the scope menu.

Step 2

Note

There are variations to this procedure. In addition to these basic steps, you can also do the following:

Select the status level, and click Filter to filter the display to show all zones or only those with zones errors.

Port Mapping
Beginning with Cisco NX-OS Release 6.x, you can view information about all the logical and physical Ethernet interfaces of all the devices that are discovered by Cisco DCNM Web Client.

Viewing the Port MapperYou can view the Port Mapper report from Cisco DCNM Web Client.
Step 1

DETAILED STEPSFrom the menu bar, choose Inventory > Port Mapper.
You see the Port Mapper window. See Figure 2-7.
Figure 2-7 Port Mapper Window

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-35

Chapter 2 Configuring Backups Using Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
In the Port Mapper window, you see the following details listed in Table 2-6.
Table 2-6 Port Mapper

Column Device Interfaces Type Admin Status Operation status Speed Duplex STP Protocol

Description Name of the device to which the interface belongs to. Name of the interface. Type of the port mode: switched or routed. Single port channel that is connected to two single chassis vPC end points. Operational model for the port. Speed for the interface. It is not the configured speed. Single port channel that is connected to two single chassis vPC end points. Spanning Tree Protocol (STP) whether or not the Per-VLAN Spanning Tree (PVST), Multiple Spanning Tree (MST), and rapid-PVST is configured. Access VLAN if the port mode is access or displays allowed VLAN if the port mode is trunk. MAC address for the port. IP address that is configured on the port and the IP mask. Serial number of the Small Form-Factor Pluggable (SFP) if it is attached on the port.

Access/Allowed VLANs Built-in MAC Address IP Address/Mask SFP Serial Number

Step 2

Click the filter

icon to filter the port mapping report.

The filter options in the Device, Interface Name, Description, Access/Allowed VLANs, Built-in MAC Address, IP Address/Mask, and SFP Series Number column allows you to enter text inputs in the respective field and search. In addition, you can use the drop-down list in the Mode, Admin Status, Operation Status, Speed, Duplex, and STP Protocol column to limit the objects that appear in the report.
Step 3 Step 4 Step 5

Click the print Click the Excel spreadsheet.

icon to print the port mapping report of the selected device. icon to export the port mapping report of the selected device to a Microsoft Excel

Click on a cell in the STP Protocol column to view the STP status of the specific port of the VLAN. A popup window displays the STP status of the port.

Configuring Backups Using Cisco DCNM Web Client

Using Cisco DCNM Web Client, you can periodically back up startup and running configurations of the switch. You can also view backed-up configurations, schedule configuration backups, compare two backed-up configurations, and restore a configuration onto a switch.

Note

Beginning with Cisco DCNM Release 6.x, the backup for the LAN configuration are also supported and the backup is skipped for the all the switches where there are no configuration changes.

Cisco DCNM Fundamentals Guide, Release 6.x

2-36

OL-25174-02

Chapter 2

Cisco DCNM Web Client Configuring Backups Using Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
This section includes the following topics:

Viewing a Configuration, page 2-37 Editing a Configuration, page 2-37 Deleting a Configuration, page 2-38 Copying a Configuration, page 1-40 Comparing Configurations, page 2-38 Creating Backups, page 2-39 Viewing Scheduled Jobs, page 2-39

Viewing a Configuration
Step 1

DETAILED STEPSFrom the menu bar, choose Config> View.

You see the configuration information. Choose a fabric name from the Scope pane.

Step 2

Note

The scope pane displays the global view with SAN, LAN, and Default LAN groups. Depending upon the value selected in the Scope pane, the switches and their configurations are listed.

Step 3 Step 4 Step 5 Step 6

From the Switch drop-down list, select a switch. From the Configuration file drop-down list, select a configuration filename. Check the Show All checkbox to display all the configurations present, irrespective of the options selected in the global Scope pane. Click View.

Editing a Configuration
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

DETAILED STEPSFrom the menu bar, choose Config > View.

From the Scope pane, select a fabric name. From the Switch drop-down list, select a switch. From the Configuration file drop-down list, select a configuration filename. Click View to view the configuration file. Check the Edit checkbox to edit the configuration file. Click Save to Local file to save the modified configuration file on your computer.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-37

Chapter 2 Configuring Backups Using Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Deleting a Configuration
Step 1

DETAILED STEPSFrom the menu bar, choose Config > View.

Note

The Scope pane displays the global view with SAN, LAN, and Default LAN groups. Depending upon the value that you select in the Scope pane, the switches and their configurations are listed.

Step 2 Step 3 Step 4 Step 5

From the Scope pane, select a fabric name. From the Switch drop-down list, select a switch. From the Configuration file drop-down list, select a configuration filename. Click Delete.

Copying a Configuration
Step 1

DETAILED STEPSFrom the menu bar, choose Config > copy.

Note

The Groups pane displays the global view with SAN, LAN, and Default LAN groups. Depending upon the value that you select in the Scope pane, the switches and their configurations are listed.

Step 2 Step 3 Step 4 Step 5

From the Groups pane, select a fabric name. From the Eligible Switch(es) drop-down list, select a switch. From the Configuration file drop-down list, select a configuration file name. Click Copy.

Comparing Configurations
Step 1

DETAILED STEPSFrom the menu bar, choose Backup > Compare.

You see the compare configuration information. From the Scope drop-down list, select a fabric name. From the Switch drop-down list, select a switch. (Optional) Click the Archive, Running, or Startup radio button. Click Compare.

Step 2 Step 3 Step 4 Step 5

Configuring Templates
Step 1

DETAILED STEPSFrom the menu bar, choose Config > Templates.

You see the name of the template along with its description, Platforms and Tags. Use the checkbox to select an existing template.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x

2-38

OL-25174-02

Chapter 2

Cisco DCNM Web Client Viewing and Creating Custom Reports

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 3 Step 4 Step 5

You can also Add a new template or Import an existing template. Enter a Template Name, Description, Tags and select the Supported Platforms. Click Save to save the template.

Creating Backups
Prerequisites
You must make sure that the bootflash has enough unused space to accommodate configuration backup jobs.
Step 1

DETAILED STEPSFrom the menu bar, choose Backup > Create.

You see the backup options page. From the Fabric drop-down list, select a fabric name. Click to select the frequency (Once, Daily, Weekly, Monthly) at which you want to perform backup. Click the calendar icon to select a start date. Click the calendar icon to select a end date. Enter the start time. Click to select a configuration type (Archive, Running, Startup). Click Create to save this backup schedule.

Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8

Viewing Scheduled Jobs

Step 1

DETAILED STEPSFrom the menu bar, choose Config > Jobs.

You see the scheduled jobs information. Double-click one of the listed jobs to view them.

Step 2

Viewing and Creating Custom Reports

The Reports menu allows you to create customized reports based on historical performance, events, and inventory information gathered by Cisco DCNM. You can create aggregate reports with summary and detailed views. You can also view previously saved reports.

Note

Beginning with Cisco DCNM Release 6.x versions, reports can be generated for SAN and LAN. The global view Scope pane will contain SAN, LAN, and Default LAN configurations. You can select any one of these configurations, and generate reports. The Report menu includes the following submenus:

ViewDisplays previously saved reports. GenerateGenerates a custom report based on the selected report template.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-39

Chapter 2 Viewing and Creating Custom Reports

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CustomCreates a custom report template, which allows you to select any combination of events, performance categories, and inventory. The reports contain memory information for all the selected switches. JobsDisplays scheduled jobs based on the selected report template. Creating a Custom Report Template, page 2-40 Viewing a Report Based on a Specific Template, page 2-41 Viewing a Reports by a Specific User, page 2-41 Deleting a Report Template, page 2-41 Generating a Report Based on a Template, page 2-41 Modifying a Custom Report Template, page 2-42 Deleting a Report, page 2-43 Viewing Scheduled Jobs Based on a Report Template, page 2-43

This section includes the following topics:

Creating a Custom Report Template

You can create custom reports from all or any subset of information obtained by Cisco DCNM-SAN. You create a report template by selecting events, performance, and inventory statistics that you want in your report and set the desired SAN, fabrics or VSAN to limit the scope of the template. You can generate and schedule a report of your fabric based on this template immediately or at a later time. DCNM Web Client saves each report based on the report template used and the time you generate the report. As of Cisco MDS NX-OS Release 5.0, the report template design has changed to resolve the limitations of the earlier versions. With the new design model, you can perform add, delete, and modify functionalities in a single page. You can choose multiple fabrics and VSANs using the new navigation system, which will allow you to add new items and categories in the future. The new design model has three panels:

Customs panel Configuration panel User selection panel

The Customs panel allows you to add new templates, modify existing templates and delete existing templates. The Configuration panel allows you to configure a new template when it is added and modify an existing template. The options in the configuration panel are disabled until you either add a new template or select an existing template. The upper portion of the configuration panel contains many categories that you can choose and configure. The User Selection panel displays your configuration options in real time. While the configuration panel can display information pertaining to one category at a time, the User Selection panel displays all of your selections or configurations.
Step 1

DETAILED STEPSFrom the menu bar, choose Report > Create SAN User Defined.
You see the Report Configuration window. Click CLICK TO ADD NEW CUSTOM in the Customs panel to create a new name for your report.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x

2-40

OL-25174-02

Chapter 2

Cisco DCNM Web Client Viewing and Creating Custom Reports

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 3 Step 4 Step 5 Step 6

Click Scope in the Configuration panel to define the scope. The global Scope panel will have SAN, LAN, and Default LAN configurations. Indicate the information you want in the report by navigating to each category such as Health, Performance, and Inventory in the Configuration panel. (Optional) Choose Severity for events, Status for inventory information, or Type of end devices for performance information and inventory information. Click Save to save this report template.

Viewing a Report Based on a Specific Template

Step 1

DETAILED STEPSFrom the menu bar, choose Reports > View.

You see the Report table window. In the left pane, expand Templates. Select the report that you want to view. You can view the report in the main screen or you can view the report in a new browser window if you click the report in the report table. To delete a specific report, check the check box and then click Remove. To delete all reports, check the check box in the header, and then click Remove.

Step 2 Step 3 Step 4 Step 5

Viewing a Reports by a Specific User

Step 1

DETAILED STEPSFrom the menu bar, choose Reports > View.

You see the Report Table window. In the left pane, click to expand Users. Double-click the username. Select the report that you want to view. You can view the report in the main window or you can view the report in a new browser window if you click the report in the report table. To delete a specific report, check the check box and then click Remove. To delete all reports, check the check box in the header and then click Remove.

Step 2 Step 3 Step 4 Step 5 Step 6

Deleting a Report Template

Step 1 Step 2 Step 3

DETAILED STEPSIn the Template panel, click the report template that you want to delete.
Drag the selected report template to the trash at the right-bottom corner of the Template panel. Click Yes to delete the template.

Generating a Report Based on a Template

You can generate reports based on a selected template or you can schedule the report to run at a specified time.
Step 1

DETAILED STEPSSelect a SAN, fabric, or VSAN on which to base the report.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-41

Chapter 2 Viewing and Creating Custom Reports

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2

From the menu bar, choose Reports > Generate. You see the Generate Custom Report window. Click Scope in the configuration panel to define the scope. The global Scope panel has SAN, LAN, and Default LAN configurations. Choose a report template from the available drop-down list. (Optional) Change the name of the report. By default, report names are based on the date and time generated. (Optional) Check the Report is only visible to the Owner check box to change the attribute of the report. If selected, the report can be viewed only by the specific user and network administrator. (Optional) Check the Export to CSV check box to export the report in text. (Optional) In the Email Report option, do one of the following actions:

Step 3 Step 4 Step 5 Step 6 Step 7 Step 8

Choose No to not to receive an e-mail notification. Choose Link Only to receive the link in an e-mail. Choose Contents to receive an e-mail notification.

Step 9 Step 10

(Optional) In the user selection option, check the Embed Charts in Reports checkbox to view the reports weekly. Click Create to generate a report based on this template. You see the report results in a new browser window. Alternatively, you can view the report by choosing Report > View and selecting the report name from the report template that you used in the navigation pane.

Step 11

Click Schedule to schedule a report based on this template. You see the schedule panel. You see the Generate Custom Report window. In the Schedule panel, specify the scheduled run time and how often you want the report to run. Click the calendar next to Start Date or End Date to modify the date settings. Choose the Start Time or End Time drop-down list to modify time settings. Select the frequency at which you need the report to be generated. Enter a name for the report in the Job Name field and click Create to save the report. You can view the scheduled reports on the Jobs page but once the scheduled jobs have started running, they are removed from the Scheduled Job table.

Step 12 Step 13 Step 14 Step 15 Step 16

Note

The End Date must be at least five minutes earlier than the Start Date.

Modifying a Custom Report Template

Step 1

DETAILED STEPSFrom the menu bar, choose Reports > Create SAN User Defined.
You see the Customs, Configuration and User Selection panels. Double-click to select a report from the customs panel. You see the current information about this report in the Configuration panel. Indicate the information that you want to gather in the report by clicking the Health, Performance, and Inventory tabs in the Configuration panel.

Step 2

Step 3

Cisco DCNM Fundamentals Guide, Release 6.x

2-42

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 4 Step 5

(Optional) Select a severity level for events, status for inventory information, or type of end device for performance information and inventory information. Click Save to save this report template.

Note

You cannot change the SAN, fabric, or VSAN that the report is based on. Generate a new report for a new SAN, fabric, or VSAN.

Deleting a Report
BEFORE YOU BEGIN
Reports you generate are saved by DCNM Web Client. To delete a custom report, you need to first select the report that you want to delete.
Step 1 Step 2 Step 3 Step 4

DETAILED STEPSFrom the menu bar, choose Reports > View.

In the left pane, expand By User. Double-click the username. In the right pane, select the report that you want to delete, and then click Remove.

Viewing Scheduled Jobs Based on a Report Template

Step 1

DETAILED STEPSFrom the menu bar, choose Reports > Jobs.

You see the Scheduled Jobs Table window. Click a report template in the navigation pane to view the scheduled jobs based on the selected template.

Step 2

Administering Cisco DCNM Web Client

The Admin options allows you to perform minor administrative and configuration tasks on the Cisco DCNM-SAN Server. The Admin options contains the following submenus:

StatusDisplays the status of the Database Server and allows you to start and stop Performance Collector services on your server. You should restart services only if something is not working properly or if too large a percentage of system resources are being consumed.

Note

You cannot start or stop the Database Server services using DCNM Web Client. If you are using the Microsoft Windows operating system, you need to use Microsoft Management Console to stop, start, or restart the Database Server. LogsAllows you to view all the logs from the various services running on the Cisco DCNM-SAN Server. Data SourcesAllows you to view all the data sources such as Fabric, LAN, VMware, and so on. ClientsAllows you to view all the clients connected to the Cisco DCNM-SAN Server

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-43

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Server PropertiesAllows you to view all the fields defined in the server properties config file. SFTP CredentialsAllows you to view the SFTP credentials.

Note

If you see a database file lock error in the database log, you can fix it by shutting down and restarting the database server using the Web Client.

Note

Only network administrators can access the DCNM Web Client Admin options. Network operators cannot view the Admin options.

This section includes the following topics:

Adding, Editing, and Removing Managed Fabrics, page 2-44 Adding, Editing, and Removing VMware Servers, page 2-46 Starting, Restarting, and Stopping Services, page 2-47 Viewing a vPC, page 2-47 Resolving vPC Inconsistencies, page 2-48 Searching for a Device, page 2-49 Viewing Log Information, page 2-51 Configuring Cisco DCNM-SAN Server Properties, page 2-51 Configuring SFTP Credentials, page 2-51 Viewing Events, page 2-51

Adding, Editing, and Removing Managed Fabrics

Cisco DCNM Web Client reports information obtained by the Cisco DCNM-SAN on any fabric known to the Cisco DCNM-SAN.

Creating a SNMP User

You can discover new fabric and start managing a fabric from Cisco DCNM Web Client. Before you discover a new fabric, ensure you create a SNMP user on the switch first.
Step 1

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
You see the list of fabrics (if any) managed by Cisco DCNM-SAN in the Opened column. Click Add. You see the Add Fabric dialog box. Enter the seed switch IP address for this fabric. Enter the SNMP username and password for this fabric. (Optional) Check the SNMPV3 check box. If you check SNMPV3, the fields Read Community and Write Community change to Username and Password. You must enter your username and password. Select the privacy settings from the Auth-Privacy drop-down list.

Step 2

Step 3 Step 4 Step 5 Step 6

Cisco DCNM Fundamentals Guide, Release 6.x

2-44

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 7 Step 8 Step 9

(Optional) Check the Limit Discovery by VSAN checkbox to specify the included VSAN list or excluded VSAN list from the VSANs provided to discover a new fabric. (Optional) Check the Enable NPV Discovery in all Fabrics check box. If you check enable NPV discovery in all fabrics, the changes are applied to all the fabrics that are previously discovered. Click Add to begin managing this fabric.

Removing FabricsYou can remove single or multiple fabrics from the Cisco DCNM Web Client.
Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
Check the check box next to the fabric that you want to remove and click Remove to discontinue data collection for that fabric.

Editing a Fabric You can edit a fabric from Cisco DCNM Web Client.
Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
Check the check box next to the fabric that you want to edit and click Edit. You see the Edit Fabric dialog box. Enter a new fabric name, username and password, privacy and specify how you want DCNM Web Client to manage the fabric by selecting one of the status options. (Optional) Check the SNMPV3 check box. If you check SNMPV3, the Community field change to Username and Password. You must enter your username and password. Change the fabric management state to Managed, Unmanaged, or Managed Continuously. Click Apply to save the changes.

Step 3 Step 4 Step 5 Step 6

Note

You can edit only one fabric at a time.

Moving a FabricYou can move a fabric from Cisco DCNM Web Client.
Step 1 Step 2 Step 3

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
Select the fabrics from the fabric table. Click Move Fabrics to another Federation Server or Move LAN Tasks to another DCNM Server. Select the fabrics that need to be moved and click Move Fabric. In the Move Fabrics to another Federation server dialog box, select the DCNM server where the fabrics will be moved. The server drop-down list will list only the active servers. In the Move LAN Tasks to another DCNM Server dialog box, enter the LAN tasks that need to be moved and specify the DCNM server. Note the following:

Step 4

This feature is only available on the federation setup and the Move Fabric is only displayed in the federation setup screen. You can move the fabrics from a sever that is down to an active server. The management state will remains the same.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-45

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Adding, Editing, and Removing VMware Servers

DCNM Web Client reports information gathered by Cisco DCNM-SAN on any VMware servers supported by Cisco DCNM-SAN.

Managing a VMware Server

You can managing a VMware server from Cisco DCNM Web Client.
Step 1

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
You see the list of VMware servers (if any) that are managed by Cisco DCNM-SAN in the table. Click Add. You see the Add VMware dialog box. Enter the seed switch IP address for this VMware server. Enter the username and password for this VMware server. Click Add to begin managing this VMware server.

Step 2

Step 3 Step 4 Step 5

Removing a VMware Server

You can remove a VMware server from the Cisco DCNM Web Client.

DETAILED STEPS
Step 1 Step 2

From the menu bar, choose Admin > General > Data Sources. Check the check box next to the VMware server that you want to remove and click Remove to discontinue data collection for that VMware server.

Modifying a VMware Server

You can modify a VMware server from Cisco DCNM Web Client.
Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
Check the check box next to the VMware server that you want to edit and click Edit. You see the Edit VMware dialog box. Enter a new VMware name, username and password, privacy and specify how you want DCNM Web Client to manage the fabric by selecting one of the status options. Click Apply to save the changes.

Step 3 Step 4

Rediscovering a VMware Server

You can rediscover a VMware server from Cisco DCNM Web Client.

Cisco DCNM Fundamentals Guide, Release 6.x

2-46

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 1 Step 2 Step 3

DETAILED STEPSFrom the menu bar, choose Admin > General > Data Sources.
Check the check box next to the VMware that you want to rediscover. Click Rediscover.

Starting, Restarting, and Stopping Services

Step 1

DETAILED STEPSFrom the menu bar, choose Admin > General > Status.
You see a table of services per server and the status of each. Select the services that you want to start, restart, or stop. Click Start or Stop. The selected services are started, restarted, or stopped.

Step 2 Step 3

Viewing Server Federation

From the menu bar, choose Admin > General > Federation. The list of Servers along with the Status, Local Time and Data Sources are displayed.

Viewing a vPC
The virtual port channel (vPC) feature enables you to view the links that are physically connected to different devices as a single port channel. A vPC is an extended form of a port channel. A vPC allows you to create redundancy and increase bisectional bandwidth by enabling multiple parallel paths between nodes and allowing load balancing traffic. Traffic is distributed among two single device vPC end points. If there is an inconsistency in the vPC configurations, the vPC does not function correctly. The Cisco DCNM Web Client helps you to identify the inconsistent vPCs and resolve the inconsistencies in each vPC or in all vPCs.
Step 1

DETAILED STEPSFrom the menu bar, choose Health> Virtual Port Channels (vPC).
Cisco DCNM Web Client displays both the consistent and inconsistent vPCs.

Note

The vPC inconsistency page displays inconsistencies only for the devices that have required Cisco DCNM licenses installed on them. The devices that do not have Cisco DCNM LAN license installed on them do not appear on this page. Table 2-7 displays the following vPC configuration details in the data grid view.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-47

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Table 2-7

vPC Configuration Details

Column vPC ID Domain ID

Description vPC ID. You can view all the multichassis vPC end points and corresponding peer switches for each vPC ID. Domain ID of the vPC peer switches.

Multi-chassis vPC End- Point Device Details of the corresponding to peer single chassis primary vPC end point. Port Channel ID Primary vPC peer link Device Port Channel ID Device Name Secondary vPC peer link Device Consistency Single port channel that is connected to two single chassis vPC end points. Details of the corresponding multichassis vPC end points. Single port channel that is connected to two single chassis vPC end point. Hostname of the vPC peer switches. Details that correspond to the peer single chassis secondary vPC end points. Configuration consistency between vPC peer port channels and vPC port channels. The valid values are Consistent and Inconsistent. Configuration consistency between vPC peer switches that form a peer link. Configuration consistency between vPC peer port channels.

Global vPC

You can view the vPC inconsistencies from Cisco DCNM Web Client.
Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Health > Virtual Port Channels (vPC).
Click on the specific cell to view the global or vPC inconsistencies. A popup window displays the inconsistencies between the parameters. All the conflicts in the configuration for the vPC primary device and the secondary device are displayed in red.

Resolving vPC Inconsistencies

You can resolve vPC inconsistencies from Cisco DCNM Web Client.
Step 1 Step 2 Step 3

DETAILED STEPSClick Resolve All Conflicts on the top right.

Click Print to print the page. Click Excel to export the data to a Microsoft Excel spreadsheet.

Cisco DCNM Fundamentals Guide, Release 6.x

2-48

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Automatically Resolving vPC Inconsistencies

Cisco DCNM Web Client enables you to automatically resolve all vPC inconsistencies.
Step 1 Step 2 Step 3

DETAILED STEPSFrom the menu bar, choose Health > Virtual Port Channels (vPC).
Click on the specific cell to view the global or vPC inconsistencies. Click Auto Resolve Conflicts. The configuration parameters on the secondary device are synchronized with the primary vPC device.

Searching for a Device

You can search for a device by using Cisco DCNM Web Client. Cisco DCNM Web Client enables you to search either a LAN or SAN device by name, IP address, world wide name (WWN), alias, or serial number.
Step 1

DETAILED STEPSIn the Search

display the drop-down list for search options. See Figure 2-8.
Figure 2-8 Search Options

field, click the down arrow icon to

Step 2

Choose a search option by clicking on an option. By default, Cisco DCNM Web Client searches for a device by name.

Note

The Search Indexer automatically runs every two hours. If you discover a new device by using Cisco DCNM, the newly discovered device is reflected in the search result only after two hours from the time of discovery. To manually run the Search Indexer, go to Admin > General > Status and click the (Re) start Service icon in the Actions column.

Step 3

Enter a keyword and click the right arrow or press Enter. The Search window appears. See Figure 2-9.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-49

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-9 Search Window

Search results are of two types: Inventory and Performance. For more information about the search types, see Table 2-8.
Table 2-8 Search Types

Search Result Category Inventory Inventory Inventory Inventory Inventory Inventory Inventory Inventory Inventory Performance Performance Performance
Step 4

Search Result Entity Type Switch: SAN/LAN Switch module: SAN/LAN Inter-Switch Link (ISL) Enclosure: host Enclosure: storage VSAN Zone End device Virtual machine (VM) ISL End device Flow

Search Landing Page Switch Dashboard (a SAN or LAN Switch) Switch Dashboard Inventory ISL Page Host Dashboard Storage Dashboard Inventory VSAN page Inventory Zone Page Inventory End Device Page Host Dashboard Performance ISL Page Performance End Device Page Performance Flow Page

From the Search window, click on the device that you want to view. The Cisco DCNM Web Client navigates you to the corresponding page.

Cisco DCNM Fundamentals Guide, Release 6.x

2-50

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
If you click the Performance button, and choose an item, Cisco DCNM Web Client navigates you to the Performance page.

Viewing Log Information

You may occasionally want to view logs such as the Cisco DCNM Web Client log. These processes have no corresponding GUI to allow you to view information about these log files. If you see errors, preserve these two files for viewing.
Step 1

DETAILED STEPSFrom the menu bar, choose Admin > General > Logs.
You see a list of viewable logs in the left column. Click a log file to view it.

Step 2

Configuring Cisco DCNM-SAN Server Properties

To configure Cisco DCNM-SAN Server properties, from the menu bar, choose Admin > General > Server Properties. Follow the on-screen instructions.

Configuring SFTP Credentials

Step 1

DETAILED STEPSFrom the menu bar, choose Admin > General > SFTP Credentials.
You see the SFTP credentials page. In the SFTP Username field, enter the username. In the SFTP Password field, enter the password. In the Root Directory field, enter the root directory path. From the Verification Switch field, select the switch. Click Apply to apply the configuration. Click Apply and Verify to apply and verify the configuration.

Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

Viewing Events
Beginning with Cisco NX-OS Release 6.x, you can view the events and syslogs in Cisco DCNM Web Client.

Note

Beginning with Cisco NX-OS Release 6.x, all events and syslogs are displayed on the events page.

Viewing Accounting Events

You can view the accounting events from Cisco DCNM Web Client.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-51

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 1

DETAILED STEPSFrom the menu bar, choose Health > Accounting.

Viewing Events
You can view the events and syslog from Cisco DCNM Web Client.
Step 1

DETAILED STEPSFrom the menu bar, choose Health > Events.

The Count column displays the number of times that the same event has occurred during the time period that is shown in the Last Seen column. If you click on a switch name that is displayed in the Switch column, Cisco DCNM Web Client displays the switch dashboard. If you click on the IP address that is displayed in the Description column, the search feature displays all search results that pertains to the device. From here, you can choose the results that you wish to view. For more information, see Table 2-9.
Table 2-9 Event Table

Icon

Description Mark selected row(s) as Acknowledged. Mark selected row(s) as Unacknowledged. Delete selected row(s). Show or Hide column search filters. Prints selected row(s). Exports selected row(s)

To delete all events from the server database, right-click on the event table and choose Delete All Events from the menu. To copy row(s) from the event table, right-click on the event table row and choose Copy Row Selection from the menu. To copy a cell from the event table row, right-click on the cell and choose Copy Current Cell from the the menu. To display the column filters of the event page, click the Show Filter icon. You can view events by the acknowledgment, switch, severity, facility, type, first-last seen, and descriptive text. Any new or updated events are displayed as a message in the Events panel. Refresh the page to view the new or updated event.

Cisco DCNM Fundamentals Guide, Release 6.x

2-52

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Traps and Syslog Registration Information

Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Admin > Events > Registration.
Select a fabric to display registration information for that fabric. You see the Registration window showing the registration information for the selected fabric. (Optional) Click the Print icon or the Export Report icon for a copy of the information.

Step 3

Configuring Forwarding of Notifications for Events

This section includes the following topics:

Adding Notification Forwarding, page 2-53 Removing Notification Forwarding, page 2-54

Adding Notification Forwarding

You can use Cisco DCNM Web Client to add and remove notification forwarding for system messages.

Note

DETAILED STEPSCisco DCNM Web Client forwards fabric events through e-mail or SNMPv1 traps.
From the menu bar, choose Admin > Events > Forwarding. Click Add. You see the Add Notification dialog box . In the Forwarding Method, choose either E-Mail or Trap. If you choose Trap, a Port field is added to the dialog box. In the Address field, enter the IP address. From the Scope drop-down list, choose the fabric or LAN group for notification. In the VSAN Scope, choose either All or List. From the Event Type drop-down list, choose an event type or choose Syslog Facility and Type. Check the Storage Ports Only check box to select storage ports only. From the Minimum Severity drop-down list, select the severity level of the messages to receive. Click Add to add the notification.

Step 1 Step 2

Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10

Note

The minimum Severity option is available only if the Event Type is set to All.

Note

The traps sent by Cisco DCNM correspond to the severity type followed by a text description:
trap type(s) = 40990 (emergency) 40991 (alert) 40992 (critical) 40993 (error) 40994 (warning) 40995 (notice) 40996 (info) 40997 (debug)textDescriptionOid = 1, 3, 6, 1, 4, 1, 9, 9, 40999, 1, 1, 3, 0

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-53

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Removing Notification Forwarding

You can remove notification forwarding.
Step 1 Step 2 Step 3

DETAILED STEPSFrom the menu bar, choose Admin > Events > Forwarding.
Check the check box in front of the notification that you want to remove. Click Remove.

Configuring EMC CallHome

You can configure EMC Callhome from the Cisco DCNM Web Client for EMC supported SAN switches.
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6

DETAILED STEPSFrom the menu bar, choose Admin > Events > EMC CallHome.
Check the Enable check box to enable this feature. Check the check box to select the fabrics next to the fabric you want to select. Enter the general e-mail information. Click the Apply to update the e-mail options. Click Apply and Test to update the e-mail options and test the results.

Configuring AAA Properties

To configure AAA properties, from the menu bar, choose Admin > Management Users > Remote AAA Properties. Follow the instructions that appear in the window.

Adding and Removing Users

You can use Cisco DCNM Web Client to add and remove Web Client users.
Step 1

DETAILED STEPSFrom the menu bar, choose Admin > Management Users > Local.
You see the Local Database page. Click Add. You see the Add User dialog box. Enter the username in the Username field.

Step 2

Step 3

Note

The username guest is a reserved name (case insensitive). The guest user can only view reports. The guest user cannot change the guest password, or access the Admin options in DCNM Web Client.

Step 4 Step 5

From the Role drop-down list, select a role for the user. In the Password field, enter the password.

Cisco DCNM Fundamentals Guide, Release 6.x

2-54

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 6 Step 7 Step 8

In the Confirm Password field, enter the password again. Click Add to add the user to the database. Repeat Steps 3 through 7 to continue adding users.

Removing a User
Step 1 Step 2

DETAILED STEPSFrom the menu bar, choose Admin > Management Users > Local.
Check the check box next to the user(s) that you want to remove and click Remove.

Configuring LDAP for Remote AAA Server

Beginning with Cisco NX-OS Release 6.x, Cisco DCNM Web Client provides an option for configuring the Lightweight Directory Access Protocol (LDAP) for a remote AAA server.

LDAP Configuration for a Remote AAA Server

You can configure the LDAP for a remote AAA server from Cisco DCNM Web Client.
Step 1

DETAILED STEPSFrom the menu bar, choose Admin > Management Users> Remote AAA.
The AAA properties configuration page appears. See Figure 2-10.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-55

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-10 LDAP Configuration for the Remote AAA

Step 2 Step 3 Step 4

Click LDAP from the options that are given for the Auth Mode. In the Host field, enter the DNS address of the host. Click Test to test the AAA server. A dialog box prompts you to enter your username and password. See Figure 2-11.
Figure 2-11 Test AAA Server Authentication

Step 5 Step 6

Enter a valid username and password and then click Test. Click Close to cancel the test. The dialog box appears if the AAA server test is successful. See Figure 2-12.

Cisco DCNM Fundamentals Guide, Release 6.x

2-56

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-12 AAA Server Test Successful

The LDAP Authentication Failed dialog box appears if the AAA server test fails. See Figure 2-13.
Figure 2-13 LDAP Authentication Failure

Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14

In the Port field, enter a port number. (Optional) Check the SSL Enabled check box. In the Base DN field, enter the base domain name (DN). In the Filter field, enter filters. Choose an option for determination of role by either Attribute or Admin Group Name to determine a role. In the Role Admin Group field, enter the name of the role. In the Map To DCNM Role field, enter the name of role that is be mapped. Click Apply to apply the LDAP configuration.

Viewing and Disconnecting Clients

Step 1

DETAILED STEPSFrom the menu bar, choose Admin > Management Users > Clients.
You see the Clients page. Check the check box next to the client that you want to disconnect. Click Disconnect.

Step 2 Step 3

Creating, Editing, and Removing Performance Collections

If you are managing your fabrics with Performance Manager, you must set up an initial set of flows and collections on the fabric. You can use Cisco DCNM Web Client to add and remove performance collections. The fabric has to be licensed and in the Managed Continuously state before a collection for the fabric can be created.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-57

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing the Performance Manager Collection

Beginning with Cisco NX-OS Release 6.x, by using the Cisco DCNM Web Client, you can view the Performance Manager (PM) Collection page for SAN and LAN in a single window and globally apply the same settings to both SAN and LAN. You can view the PM Collection page from Cisco DCNM Web Client.
Step 1

DETAILED STEPSFrom the main menu bar, choose Admin > Performance > Collection.
The PM Collection page appears. See Figure 2-14.
Figure 2-14 Performance Collection

You can globally turn on or off the threshold and change the threshold from this page. In addition, from the performance collection page, you can do the following:

Enable or disable the threshold. By default, the threshold is disabled. Enable or disable the threshold ISL-only flag. By default, the threshold ISL is enabled. Change the critical and warning threshold. Add or remove the SAN fabric information. Change the SAN performance collection policy for each fabric. By default, ISLs, hosts and storage are enabled. Add or remove the LAN switches into or from the collection. Change the LAN PM collection policy. By default, trunks are enabled.

SAN Collection

For the LAN, click the Check All check box to add all fabrics. When you select a fabric, the default settings of the fabric are displayed. In the default view, ISLs, hosts storage, FC Flows, and FC Ethernet are displayed. You can select a fabric and modify the settings.

Cisco DCNM Fundamentals Guide, Release 6.x

2-58

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
LAN Collection

For the LAN, you can change the LAN PM policy for all DCNM licensed Ethernet switches. Click on a group node to select all Ethernet switches.
Fabric Extender

If a Cisco Nexus 2000 Series switch is attached to a Cisco Nexus 5000 Series switch or Cisco Nexus 7000 Series switch as a Fabric Extender (FEX) and the attached switch is DCNM licensed, the PM collects tx, rx, and error discard information for all FEX interfaces that are functional. Figure 2-15 displays how the PM collects information about a FEX interface.
Figure 2-15 The FEX Interface

For more information on Cisco DCNM Licensing, see the Cisco DCNM Installation and Licensing Guide, Release 6.x.

Configuring the RRD Database

Configuring the Round Robin Database (RRD) allows you to set the intervals at which data samples are collected. After applying the configuration, the database storage format is converted to a new format at those intervals. Because database formats are incompatible with each other, you must copy the old data (before the conversion) to the $INSTALLDIR/pm directory. See the Importing the RRD Statistics Index section on page 2-60.
Step 1

DETAILED STEPSFrom the menu bar, choose Admin > Performance > Databases.
You see the Performance Database (collection interval) page. In the top row of the Days column, enter the number of days to collect samples at 5-minute intervals. In the second row of the Days column, enter the number of days to collect samples at 30-minute intervals. In the third row of the Days column, enter the number of days to collect samples at 2-hour intervals. In the bottom row of the Days column, enter the number of days to collect samples at 1-day intervals.

Step 2 Step 3 Step 4 Step 5

Note

As of Cisco SAN-OS Release 3.1(1) and later releases, you can configure the sampling interval for ISLs. Select a sampling interval from the ISLs drop-down list.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-59

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 6

Click Apply to apply your changes, or click Defaults to reset the file sizes to the default values. If you are applying new values, or if the current values are not the default values, you see a message indicating that the conversion of the RRD files take a certain amount of time and that the database is unavailable until then. The time that it takes depends on the difference between the old and new values.

Note

The system allows you to convert data, one process at a time. When you start converting the data, the Apply and Default buttons change to Refresh and Cancel so that another process cannot be inadvertently started. The display is the same for all browsers that access the server during this time. Click Refresh to view the latest progress. Click Cancel to cancel the process of converting the data. If the job is successfully canceled, you see the Apply and Default buttons again. If the cancel job is not successful, you see a message indicating that the cancellation has failed. If you want to perform this procedure, perform it before collecting a lot of data because data conversion can take a long time.

Importing the RRD Statistics Index

Step 1 Step 2 Step 3 Step 4

DETAILED STEPSStop Cisco DCNM-SAN Server.

Copy the original RRD file into $INSTALLDIR/pm/db. Run $INSTALLDIR/bin/pm.bat s. Restart Cisco DCNM-SAN and add the fabric.

Configuring Collection Thresholds

Step 1

DETAILED STEPSFrom the menu bar, choose Admin > Performance > Thresholds.
You see the Thresholds page . Follow these steps to configure thresholds using absolute values:
a.

Step 2

To configure conditions for sending Critical notifications, check the Generate Critical check box. In the ...when traffic exceeds field, enter a number (from 5 to 95) to indicate the percentage at which the Critical notification is sent. For example, entering 10 causes a notification to be sent when traffic at any given time exceeds 10 percent of the capacity. To configure conditions for sending Warning notifications, check the Generate Warning check box. In the ...when traffic exceeds field, enter a number (from 5 to 95) to indicate the percentage at which the Warning notification is sent. For example, entering 9 causes a notification to be sent when traffic at any given time exceeds 9 percent of the capacity.

b.

Step 3

Click Apply.

Configuring Other Statistics

Step 1

DETAILED STEPSFrom the menu bar, choose Admin > Performance > Others.
You see the Others page.

Cisco DCNM Fundamentals Guide, Release 6.x

2-60

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2

Click Add. You see the Add SNMP Statistic dialog box. From the Switch table, select the switch for which you want to add other statistics. From the SNMP OID drop-down list, select the OID. In the Display Name box, enter a new name. From the Type drop-down list, select the type. Click Add to add this statistic.

Step 3 Step 4 Step 5 Step 6 Step 7

Cisco DCNM Web Client Admin Group Scope

Beginning with Cisco NX-OS Release 6.x, a new drop-down list called Scope is added to Cisco DCNM Web Client that applies to all pages except the Admin pages. When you choose a group from the Scope drop-down list, different devices appear when you choose Inventory > Switches. See Figure 2-16.
Figure 2-16 Scope Drop-Down List

This section includes the following topics:

Adding Switch Groups, page 1-67 Adding a Member to a Group, page 2-63 Moving a Member, page 2-64 Renaming a Group, page 2-64 Deleting a Group or a Member of a Group, page 2-64

Adding Switch Groups

Beginning with Cisco NX-OS Release 6.x, you can configure switch groups by using Cisco DCNM Web Client.
Step 1

DETAILED STEPSFrom the menu bar, choose Admin > General > Switch Groups. See Figure 2-17.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-61

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-17 Admin > General > Switch Groups

Step 1 Step 2

Click the Add Group icon or press the Insert key. A field appears that allows you to enter the name for the switch group. See Figure 2-18.
Figure 2-18 Naming a Switch Group Field

Note Step 3

The Insert key does not work unless you highlight the group table first.

Enter the name of the switch group and click outside the text field or press the Return key to complete adding the switch group. Press the Esc key to discard the text input and exit.

Note

The switch group name validation and the maximum tree depth is 10.

Cisco DCNM Fundamentals Guide, Release 6.x

2-62

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

If you do not choose a parent group before adding a new switch group, the new group is added on the top of the hierarchy.

Adding a Member to a Group

You can add members to an existing group from Cisco DCNM Web Client.

Note

In the Add Member dialog, all fabrics and the Ethernet switches are displayed under SAN and LAN radio buttons. You can select a range or multiple devices by pressing the Ctrl-Click or Shift-Click.

Step 1

DETAILED STEPSChoose the switch group to which you want to add the selected members and then click
the Move Switch/Fabric to Selected Group icon. The Add Member to..dialog box appears. See Figure 2-19.
Figure 2-19 The Add Member to... Dialog Box

Note

The members listed in the Add Member to... dialog box depends on the type of the group that you select. For example, if a LAN domain is selected, the dialog box lists the Ethernet switches only. Choose the members from the Default_LAN or the Default_SAN and click Add. Selected members are added to the group. Highlight the switch group to which you want to add the selected members to and click Apply. The selected member(s) are added to the group.

Step 2

Step 3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-63

Chapter 2 Administering Cisco DCNM Web Client

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 4

Click Close to exit from the Move (LAN/SAN) Member dialog box.

Moving a Member
You can move the fabrics or Ethernet switches from one switch group to another from the Cisco DCNM Web Client.
Step 1

DETAILED STEPSChoose the members that you want to move out of a group and click the Move Selected
Switch/Fabric to group icon. The Move LAN/SAN Member dialog box appears.

Note

You must select members from the same domains. For example, LAN domains. If you select members from different domains, the Move Selected Switch/Fabric to group icon remains grayed out. You can move the members from different groups to only one target group at a time.

Step 2

Highlight the target group that you want the members to move in to and click Apply.

Renaming a Group
You can rename a switch group from Cisco DCNM Web Client.
Step 1 Step 2

DETAILED STEPSDouble-click on the switch group name that you want to rename.
Enter a new name to rename the group.

Note Step 3

The name of the group cannot contain any of these special characters: ()<>,;:\\\[]`~!#$% *=}|/?. Press the Return key to apply changes or press the Esc key to discard the modification.

Deleting a Group or a Member of a Group

You can delete a group(s) and/or a member(s) of a group from the Cisco DCNM Web Client. When you delete a group, the associated group(s) is deleted and the fabrics or Ethernet switches of the deleted group are moved back to the default SAN or default LAN.
Step 1 Step 2

DETAILED STEPSChoose the switch group or a member of a group that you want to remove.
Click the Delete icon or press the Delete key. A dialog box prompts you to confirm the deletion of the switch group or the member of the group. See Figure 2-20.

Cisco DCNM Fundamentals Guide, Release 6.x

2-64

OL-25174-02

Chapter 2

Cisco DCNM Web Client Administering Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 2-20 Deleting Switch Group Dialog Box

Step 3

Click Yes to delete or No to cancel the action.

Viewing Hosts and Virtual Hosts Information

This section contains the following topics:

Viewing Host Enclosures, page 2-65 Viewing Hosts, page 2-65 Viewing the Host Summary, page 2-66

Viewing Host Enclosures

Step 1

DETAILED STEPSFrom the menu bar, choose Dashboard > Hosts.

You see the list of hosts in the host enclosures table. Click the show details icon next to the host enclosure to view more details. You see details such as topology, SAN traffic, and events information in the dashboard.

Step 2

Viewing Hosts
Beginning with Cisco NX-OS Release 6.x, you can view and search the network servers that are connected to the Cisco NX-OS devices. Cisco DCNM extends the fabric visibility up to the server and allows you to discover and search the end devices that are attached to the network.

Note

Beginning with Cisco NX-OS Release 6.x, Server Credentials, Servers, and Static Server-Adapter Mapping are no longer available.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-65

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing the Host Summary

Step 1

DETAILED STEPSFrom the menu bar, choose Dashboard > Hosts.

You see the list of hosts in the host enclosures table. Create or modify the device alias names for host ports in any fabric. After you make the changes, click the commit icon to see the changes.

Step 2

Note

If you filter by hosts or enclosures, you can click a host in the resulting table to see host enclosure performance, a list of hosts, a list of hosts to which your device is connected, and the connection paths. This action allows you to see performance statistics for hosts and enclosures. You can also filter by end devices or by port groups to view aggregate information for those port groups, such as peak and average usage.

Viewing Storage
Step 1

DETAILED STEPSFrom the menu bar, choose Dashboard > Storage.

You see the storage enclosures table. Click the show details icon next to the storage name to view more details. Click the events icon next to the storage name to view the topology and event details.

Step 2 Step 3

Using Cisco DCNM Web Client with SSL

By default, Cisco DCNM Web Client uses HTTP. If you want to install SSL certificates and use Cisco DCNM Web Client over HTTPS (using TCP port 443 or another custom port), you need a certificate for each external IP address that accepts secure connections. You can purchase these certificates from a well-known Certificate Authority (CA). To enable SSL, you must set up the keystore to use either a self-signed certificate or a certificate from a trusted third-party company such as VeriSign. This section includes the following topics:

Creating a Local Certificate, page 2-66 Creating a Certificate Request, page 2-67 Modifying Cisco DCNM Web Client to Use SSL, page 2-69

Creating a Local Certificate

Step 1

DETAILED STEPSSet up a keystore to use a self-signed certificate (local certificate). From the command
line, enter the following command:
%JAVA_HOME%/bin/keytool -genkey -alias tomcat -keyalg RSA -keystore "C:\Program Files\Cisco Systems\dcm\jboss-4.2.2.GA\server\fm\conf\fmserver.jks"

Cisco DCNM Fundamentals Guide, Release 6.x

2-66

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2

Enter your name, organization, state, and country. Enter change it when prompted for a keystore password. If you prefer to use your own password, do not forget to change the keystorepass attribute in the server.xml file. When prompted for a key password, press Enter or use the same password as the keystore password.

Note

You can now follow the steps in the next section for modifying DCNM Web Client to use SSL.

To obtain a certificate from the Certificate Authority of your choice, you must create a Certificate Signing Request (CSR). The CSR is used by the certificate authority to create a certificate that identifies your website as secure.

Creating a Certificate Request

Step 1

DETAILED STEPSCreate a local certificate (as described in the previous section).

Note

You must enter the domain of your website in the field first and last name in order to create a working certificate.

Step 2

Create the CSR with this command:

keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore " C:\Program Files\Cisco Systems\dcm\jboss-4.2.2.GA\server\fm\conf\fmserver.jks"

Now you have a file called certreq.csr. The file is encoded in PEM format. You can submit it to the certificate authority. You can find instructions for submitting the file on the Certificate Authority website. You will receive a certificate.
Step 3 Step 4

After you have your certificate, you can import it into your local keystore. You must first import a Chain Certificate or Root Certificate into your keystore. You can then import your certificate. Download a Chain Certificate from the Certificate Authority where you obtained the certificate:

For Verisign.com commercial certificates, go to this URL: http://www.verisign.com/support/install/intermediate.html

For Verisign.com trial certificates, go to this URL: http://www.verisign.com/support/verisign-intermediate-ca/Trial_Secure_Server_Root/index.html

For Trustcenter.de, go to this URL: http://www.trustcenter.de/certservices/cacerts/en/en.htm#server

For Thawte.com, go to this URL: http://www.thawte.com/certs/trustmap.html

Import the Chain Certificate into your keystore by entering the keytool -import -alias root -keystore " C:\Program Files\Cisco Systems\dcm\jboss-4.2.2.GA\server\fm\conf\fmserver.jks" -trustcacerts -file filename_of_the_chain_certificate command.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-67

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Import the new certificate in X509 format by entering the keytool -import -alias tomcat -keystore " C:\Program Files\Cisco Systems\dcm\jboss-4.2.2.GA\server\fm\conf\fmserver.jks" -trustcacerts -file your_certificate_filename command.

Cisco DCNM Fundamentals Guide, Release 6.x

2-68

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Modifying Cisco DCNM Web Client to Use SSL

Step 1

DETAILED STEPSStop Cisco DCNM Web Client if you have already launched it. If you have installed the
Cisco DCNM Web Client on Windows, you can stop the service using Windows Services under Administrative Tools.

Step 2

Use a text editor to open \jboss-4.2.2.GA\server\fm\deploy\jboss-web.deployer\server.xml from the directory where DCNM Web Client is installed. You see the following lines in the beginning after some copyright information:
<Connector className="org.apache.catalina.connector.http.HttpConnector" port="80" minProcessors="5" maxProcessors="75" enableLookups="false" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="60000"/> <!-- Define an SSL HTTP/1.1 Connector on port 8443 --> <!-<Connector className="org.apache.catalina.connector.http.HttpConnector" port="8443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="10" debug="0" scheme="https" secure="true"> <Factory className="org.apache.catalina.net.SSLServerSocketFactory" clientAuth="false" protocol="TLS"/> </Connector> -->

Step 3

Comment the first <Connector> element and uncomment the second one. Note that the port changes from 8443 to 443 and keystore and keypass are added. Your file should look like the following example:
<!-- A HTTP/1.1 Connector on port 8080 <Connector port="80" maxThreads="250" protocol="HTTP/1.1" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" server="Apache" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" allowTrace="false"/> --> <!-- Add this option to the connector to avoid problems with .NET clients that don't implement HTTP/1.1 correctly restrictedUserAgents="^.*MS Web Services Client Protocol 1.1.4322.*$" --> <!-- A AJP 1.3 Connector on port 9009 --> <Connector port="9009" emptySessionPath="true" enableLookups="false" redirectPort="8443" protocol="AJP/1.3"/> <!-- SSL/TLS Connector configuration using the admin devl guide keystore --> <Connector port="443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="100" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" server="Apache" scheme="https" secure="true" clientAuth="false" sslProtocol = "TLS" securityDomain="java:/jaas/encrypt-keystore-password" SSLImplementation="org.jboss.net.ssl.JBossImplementation" allowTrace="false"/>

Step 4 Step 5

Save this file. Create a keyword password from the command line by navigating to C:\Program Files\Cisco Systems\dcm\fm\bin, entering Encrypter.bat ssl, and then entering changeit as the password.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-69

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 6

Restart Cisco DCNM Web Client.

Note

If you restart Cisco DCNM-SAN Server with SSL enabled, you must restart Cisco DCNM Web Client. If you want to stop and restart Cisco DCNM-SAN Server with SSL disabled, you must restart Cisco DCNM Web Client.

Viewing Hosts Information

The hosts dashboard shows the details of the selected host such as topology, events, and SAN traffic. You can export this information to an ASCII file in a comma-separated value format that can be read by applications such as Microsoft Excel. The Filter drop-down list at the top left of the table view allows you to search for hosts.

Cisco DCNM Fundamentals Guide, Release 6.x

2-70

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-71

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-72

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-73

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-74

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-75

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-76

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-77

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-78

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-79

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-80

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-81

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-82

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-83

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-84

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-85

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-86

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-87

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-88

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-89

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-90

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-91

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-92

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-93

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-94

OL-25174-02

Chapter 2

Cisco DCNM Web Client Using Cisco DCNM Web Client with SSL

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

2-95

Chapter 2 Using Cisco DCNM Web Client with SSL

Cisco DCNM Web Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

2-96

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

PA R T

Cisco DCNM for SAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

Configuring Cisco DCNM-SAN Server

This chapter describes Cisco DCNM-SAN Server, which is a platform for advanced MDS monitoring, troubleshooting, and configuration capabilities. No additional software needs to be installed. The server capabilities are an integral part of the Cisco DCNM-SAN software. This chapter contains the following sections:

Information About Cisco DCNM-SAN Server, page 3-1 Licensing Requirements For Cisco DCNM-SAN Server, page 3-2 Installing and Configuring Cisco DCNM-SAN Server, page 3-2 Managing a Cisco DCNM-SAN Server Fabric, page 3-6 Modifying Cisco DCNM-SAN Server, page 3-8 Server Federation, page 3-11 Additional References, page 3-13

Information About Cisco DCNM-SAN Server

Install Cisco DCNM-SAN Server on a computer that you want to provide centralized MDS management services and performance monitoring. SNMP operations are used to efficiently collect fabric information. The Cisco DCNM-SAN software, including the server components, requires about 60 MB of hard disk space on your workstation. Cisco DCNM-SAN Server runs on Windows 2000, Windows 2003, Windows XP, Solaris 9 and 10, and Red Hat Enterprise Linux AS Release 5. Each computer configured as a Cisco DCNM-SAN Server can monitor multiple Fibre Channel SAN fabrics. Up to 16 clients (by default) can connect to a single Cisco DCNM-SAN Server concurrently. The Cisco DCNM-SAN Clients can also connect directly to an MDS switch in fabrics that are not monitored by a Cisco DCNM-SAN Server, which ensures you can manage any of your MDS devices from a single console.

DCNM-SAN Server Features

Cisco DCNM-SAN Server has the following features:

Multiple fabric management DCNM-SAN Server monitors multiple physical fabrics under the same user interface. This facilitates managing redundant fabrics. A licensed DCNM-SAN Server maintains up-to-date discovery information on all configured fabrics so device status and interconnections are immediately available when you open the DCNM-SAN Client.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

3-1

Chapter 3 Licensing Requirements For Cisco DCNM-SAN Server

Configuring Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Continuous health monitoringMDS health is monitored continuously, so any events that occurred since the last time you opened the DCNM-SAN Client are captured. Roaming user profilesThe licensed DCNM-SAN Server uses the roaming user profile feature to store your preferences and topology map layouts on the server, so that your user interface will be consistent regardless of what computer you use to manage your storage networks.

Note

You must have the same release of Cisco DCNM-SAN Client and Cisco DCNM-SAN Server.

Note

You will not be able to manage a SAN fabric if the DCNM-SAN Server is going through a IP NAT firewall to access the SAN fabric. All the IP addresses that are discovered in a SAN fabric must be directly reachable by the DCNM-SAN Server.

Licensing Requirements For Cisco DCNM-SAN Server

When you install DCNM-SAN, the basic unlicensed version of Cisco DCNM-SAN Server is installed with it. To get the licensed features, such as Performance Manager, remote client support, and continuously monitored fabrics, you need to buy and install the Cisco DCNM-SAN Server package. However, trial versions of these licensed features are available. To enable the trial version of a feature, you run the feature as you would if you had purchased the license. You see a dialog box explaining that this is a demo version of the feature and that it is enabled for a limited time.

Installing and Configuring Cisco DCNM-SAN Server

Note

Prior to running Cisco DCNM-SAN Server, you should create a special Cisco DCNM-SAN administrative user on each switch in the fabric or on a remote AAA server. Use this user to discover your fabric topology.

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4 Step 5

Install Cisco DCNM-SAN Client and Cisco DCNM-SAN Server on your workstation. See the Installing Cisco DCNM-SAN Server section on page 3-3. Log in to DCNM-SAN. Set Cisco DCNM-SAN Server to continuously monitor the fabric. See the Managing a Cisco DCNM-SAN Server Fabric section on page 3-6. Repeat Step 2 through Step 3 for each fabric that you want to manage through Cisco DCNM-SAN Server. Install DCNM-SAN Web Server. See the Verifying Performance Manager Collections section on page 3-5.

Cisco DCNM Fundamentals Guide, Release 6.x

3-2

OL-25174-02

Chapter 3

Configuring Cisco DCNM-SAN Server Installing and Configuring Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 6

Verify Performance Manager is collecting data. See the Verifying Performance Manager Collections section on page 3-5.

Installing Cisco DCNM-SAN Server

When you install DCNM-SAN, the basic version of the Cisco DCNM-SAN Server (unlicensed) is installed with it. After you click the DCNM-SAN icon, a dialog box opens and you can enter the IP address of a computer running the Cisco DCNM-SAN Server component. If you do not see the Cisco DCNM-SAN Server IP address text box, click Options to expand the list of configuration options. If the server component is running on your local machine, leave localhost in that field. If you try to run DCNM-SAN without specifying a valid server, you are prompted to start the Cisco DCNM-SAN Server locally. On a Windows PC, you install the Cisco DCNM-SAN Server as a service. This service can then be administered using Services in the Administrative Tools. The default setting for the Cisco DCNM-SAN Server service is that the server is automatically started when the Windows PC is rebooted. You can change this behavior by modifying the properties in Services. For switches running Cisco MDS 9000 FabricWare, you must install DCNM-SAN from the CD-ROM included with your switch, or you can download DCNM-SAN from Cisco.com.

Note

You can have only one instance of Cisco DCNM-SAN Server running on a computer. If you have a DCNM-SAN Standalone version on your computer, you may need to uninstall it before you install Cisco DCNM-SAN Server. To download the software from Cisco.com, go to the following website: http://cisco.com/cgi-bin/tablebuild.pl/mds-fm

Note

If you are upgrading from an earlier version to 5.0(1a) or later, that is configured with HTTPS to use your own self-provisioned or a third-party issued SSL certificate, make sure that you set the keystore password and then restart the DCNM-SAN Server. To set the keystore password, run $INSTALLDIR/dcm/fm/bin encrypter.bat ssl.

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4

Click the Install Management Software link. Choose Management Software > Cisco DCNM-SAN. Click the Installing DCNM-SAN link. Click the FM Installer link. You see the welcome message in the Cisco DCNM-SAN Installer window. Click the Custom radio button, and then click Next to begin installation. Check the I accept the terms of the License Agreement check box, and then click Next. You see the Install Options dialog box.

Step 5 Step 6

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

3-3

Chapter 3 Installing and Configuring Cisco DCNM-SAN Server

Configuring Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 7 Step 8

Click the Cisco DCNM-SAN Server (Licensed) radio button to install the server components for Cisco DCNM-SAN Server. Click Add server to an existing server federation to add the server to a federation.

Note

You may need to add the following line in the pg-hba.conf file under # IPv4 local connections in order to allow remote hosts to connect to PostgreSQL database: host all all 0.0.0.0/0 md5

After adding, save the configuration file, restart the PostgreSQL database before you install the second server node.

Note

If you are joining more then three DCNM-SAN Servers in a federation, you need to use an Oracle database with the following settings.

C:\Documents and Settings\Administrator>sqlplus /nolog SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jan 6 17:19:32 2010 Copyright (c) 1982, 2005, Oracle. All rights reserved. SQL> connect / as sysdba; Connected. SQL> alter system set processes=150 scope=spfile; System altered. SQL> alter system set open_cursors=500 scope=spfile; System altered. SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup; ORACLE instance started. Total System Global Area 805306368 Fixed Size 1453836 Variable Size 218714356 Database Buffers 583008256 Redo Buffers 2129920 Database mounted. Database opened. SQL> show parameter processes; Total System Global Area 805306368 Fixed Size 1453836 Variable Size 218714356 Database Buffers 583008256 Redo Buffers 2129920 Database mounted. Database opened. SQL> show parameter processes; NAME -----------------------------------aq_tm_processes db_writer_processes gcs_server_processes job_queue_processes log_archive_max_processes

bytes bytes bytes bytes bytes

bytes bytes bytes bytes bytes

TYPE ----------integer integer integer integer integer

VALUE -----------------------------0 4 0 4 2

Cisco DCNM Fundamentals Guide, Release 6.x

3-4

OL-25174-02

Chapter 3

Configuring Cisco DCNM-SAN Server Installing and Configuring Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
processes integer 100

Step 9 Step 10

Select an installation folder on your workstation for Cisco DCNM-SAN. On Windows, the default location is C:\Program Files\Cisco Systems. Click Next. You see the Database Options dialog box.

Step 11

Click the radio button for either Install PostgreSQL or Use existing DB to specify which database you want to use. If you choose Install PostgreSQL, accept the defaults and enter a password. The PostgreSQL database will be installed.

Note

If you choose to install PostgreSQL, you must disable any security software you are running, because PostgreSQL may not install certain folders or users.

Note

Before you install PostgreSQL, remove the cygwin/bin from your environment variable path if Cygwin is running on your system.

Step 12 Step 13

If you select Use existing DB, click the radio button for either PostgreSQL 8.1/8.2 or Oracle10g. Click Next in the Database Options dialog box. You see the Configuration Options dialog box. Click Install to install Cisco DCNM-SAN Server.

Step 14

If you are evaluating one of these Cisco DCNM-SAN Server features and want to stop the evaluation period for that feature, you can do that using Device Manager.

Data Migration in Cisco DCNM-SAN Server

The database migration should be limited to the existing database. Data collision can occur when you merge the data between the several databases. When you upgrade a non federation mode database to a federation mode database for the first time, the cluster sequence table is filled with the values larger than the corresponding ones in the sequence table and conforming to the cluster sequence number format for that server ID.

Verifying Performance Manager Collections

Once Performance Manager collections have been running for five or more minutes, you can verify that the collections are gathering data by choosing Performance Manager > Reports in DCNM-SAN. You see the first few data points gathered in the graphs and tables.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

3-5

Chapter 3 Managing a Cisco DCNM-SAN Server Fabric

Configuring Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Managing a Cisco DCNM-SAN Server Fabric

You can continuously manage a Cisco DCNM-SAN Server fabric, whether or not a client has that fabric open. A continuously managed fabric is automatically reloaded and managed by Cisco DCNM-SAN Server whenever the server starts.

Selecting a Fabric to Manage Continuously

DETAILED STEPS
Step 1

Choose Server > Admin. You see the Control Panel dialog box with the Fabrics tab open.

Note

The Fabrics tab is only accessible to network administrators.

Note

You can preconfigure a user name and password to manage fabrics. In this instance, you should use a local switch account, not a TACACS+ server.

Step 2

Choose one of the following Admin options:

a. b. c.

Manage ContinuouslyThe fabric is automatically managed when Cisco DCNM-SAN Server starts and continues to be managed until this option is changed to Unmanage. ManageThe fabric is managed by Cisco DCNM-SAN Server until there are no instances of DCNM-SAN viewing the fabric. UnmanageCisco DCNM-SAN Server stops managing this fabric.

Step 3

Click Apply.

Note

If you are collecting data on these fabrics using Performance Manager, you should now configure flows and define the data collections.

Cisco DCNM-SAN Server Properties File

The Cisco DCNM-SAN Server properties file (MDS 9000\server.properties) contains a list of properties that determine how the Cisco DCNM-SAN Server will function. You can edit this file with a text editor, or you can set the properties through the DCNM-SAN Web Services GUI, under the Admin tab.

Note

As of Cisco NX-OS Release 4.1(1b) and later, you can optionally encrypt the password in the server.properties and the AAA.properties files. The server properties file contains these nine general sections:

Cisco DCNM Fundamentals Guide, Release 6.x

3-6

OL-25174-02

Chapter 3

Configuring Cisco DCNM-SAN Server Managing a Cisco DCNM-SAN Server Fabric

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

GENERALContains the general settings for the server. SNMP SPECIFICContains the settings for SNMP requests, responses, and traps. SNMP PROXY SERVER SPECIFICContains the settings for SNMP proxy server configuration and TCP port designation. GLOBAL FABRICContains the settings for fabrics, such as discovery and loading. CLIENT SESSIONContains the settings for DCNM-SAN Clients that can log into the server. EVENTSContains the settings for syslog messages. PERFORMANCE CHARTContains the settings for defining the end time to generate a Performance Manager chart. EMC CALL HOMEContains the settings for the forwarding of traps as XML data using e-mail, according to EMC specifications. EVENT FORWARD SETUPContains the settings for forwarding events logged by Cisco DCNM-SAN Server through e-mail.

The following server properties are added or changed in the Cisco DCNM-SAN Release 3.x and later.
SNMP Specific

snmp.preferTCPIf this option is set to true, TCP is the default protocol for Cisco DCNM-SAN Server to communicate with switches. By default, this setting is true. For those switches that do not have TCP enabled, Cisco DCNM-SAN Server uses UDP. The advantage of this setting is the ability to designate one TCP session for each SNMP user on a switch. It also helps to reduce timeouts and increase scalability.

Note

If you set this option to false, the same choice must be set in DCNM-SAN. The default value of snmp.preferTCP for DCNM-SAN is true.

Performance Chart

pmchart.currenttimeSpecifies the end time to generate a Performance Manager chart. This should only be used for debugging purposes.

EMC Call Home

server.callhome.enable Enables or disables EMC Call Home. By default, it is disabled. server.callhome.locationSpecifies the Location parameter. server.callhome.fromEmailSpecifies the From Email list. server.callhome.recipientEmailSpecifies the recipientEmail list. server.callhome.smtphostSpecifies the SMTP host address for outbound e-mail. server.callhome.xmlDirSpecifies the path to store the XML message files. server.callhome.connectTypeSpecifies the method to use to remotely connect to the server. server.callhome.accessTypeSpecifies the method to use to establish remote communication with the server. server.callhome.versionSpecifies the version number of the connection type. server.callhome.routerIpSpecifies the public IP address of the RSC router.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

3-7

Chapter 3 Modifying Cisco DCNM-SAN Server

Configuring Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Event Forwarding

server.forward.event.enableEnables or disables event forwarding. server.forward.email.fromAddressSpecifies the From Email list. server.forward.email.mailCCSpecifies the CC Email list. server.forward.email.mailBCCSpecifies the BCC Email list. server.forward.email.smtphostSpecifies the SMTP host address for outbound e-mail.

Deactivation

deactivate.confirm=deactivateSpecific Request for User to type a String for deactivation.

Note

In a federated server environment, you should not change Cisco DCNM-SAN Server properties by modifying server.properties file. You must modify the server.properties using web client menu Admin > Configure > Preferences.

Modifying Cisco DCNM-SAN Server

Fabric Manager Release 2.1(2) or later allows you to modify certain Cisco DCNM-SAN Server settings without stopping and starting the server.

Adding or Removing Cisco DCNM-SAN Server Users, page 3-8 Changing the Cisco DCNM-SAN Server Username and Password, page 3-9 Changing the DCNM-SAN Server Fabric Discovery Username and Password, page 3-9 Changing the Polling Period and Fabric Rediscovery Time, page 3-9 Using Device Aliases or FC Aliases, page 3-10

Adding or Removing Cisco DCNM-SAN Server Users

BEFORE YOU BEGIN
You must be a network administrator before you can manage users.

DETAILED STEPS
To add a Cisco DCNM-SAN Server user or to change the password for an existing user using DCNM-SAN, follow these steps:
Step 1 Step 2

Click the Local FM Users tab in the Control Panel dialog box. You see a list of DCNM-SAN users. Click New to add a user or click the user name and click Edit to change the password for an existing user. You see the FM User dialog box. Set the username and password for the new user and then click Apply.

Step 3

Step 1

Click the Local FM Users tab in the Control Panel dialog box. You see a list of DCNM-SAN users.

Cisco DCNM Fundamentals Guide, Release 6.x

3-8

OL-25174-02

Chapter 3

Configuring Cisco DCNM-SAN Server Modifying Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2 Step 3 Step 4

Click the username you want to delete. Click Remove to delete the user. Click Yes to confirm the deletion or No to cancel it.

Changing the Cisco DCNM-SAN Server Username and Password

You can modify the username or password used to access a fabric from DCNM-SAN Client without restarting Cisco DCNM-SAN Server.

DETAILED STEPS
Step 1

Choose Server > Admin. You see the Control Panel dialog box with the Fabrics tab open. Set the Name or Password for each fabric that you are monitoring with Cisco DCNM-SAN Server. Click Apply to save these changes.

Step 2 Step 3

Changing the DCNM-SAN Server Fabric Discovery Username and Password

DETAILED STEPS
Step 1

Click Server > Admin in Cisco DCNM-SAN. You see the Control Panel dialog box with the Fabrics tab open . Click the fabrics that have updated user name and password information. From the Admin listbox, select Unmanage and then click Apply. Enter the appropriate user name and password and then click Apply. For more information, see the Performance Manager Authentication section on page 4-4.

Step 2 Step 3 Step 4

Changing the Polling Period and Fabric Rediscovery Time

Cisco DCNM-SAN Server periodically polls the monitored fabrics and periodically rediscovers the full fabric at a default interval of five cycles.You can modify these settings from DCNM-SAN Client without restarting Cisco DCNM-SAN Server.

DETAILED STEPS
Step 1

Choose Server > Admin. You see the Control Panel dialog box with the Fabrics tab open.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

3-9

Chapter 3 Modifying Cisco DCNM-SAN Server

Configuring Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2 Step 3 Step 4

For each fabric that you are monitoring with Cisco DCNM-SAN Server, set the Polling Interval to determine how frequently Cisco DCNM-SAN Server polls the fabric elements for status and statistics. For each fabric that you are monitoring with Cisco DCNM-SAN Server, set the Rediscover Cycles to determine how often Cisco DCNM-SAN Server rediscovers the full fabric. Click Apply to save these changes.

Changing the IP Address of the Cisco DCNM-SAN Server

DETAILED STEPS
Step 1 Step 2

Stop the Cisco DCNM-SAN Server. Change the following parameter in the $INSTALLDIR/conf/FMServer.conf. wrapper.app.parameter.4=127.0.0.1 Change the following parameter in the $INSTALLDIR/conf/server.properties. server.bindaddrs = 127.0.0.1 Enter the following command to assign a new IP address.
run $INSTALLDIR/bin/PLMapping.bat -p newipaddress 0

Step 3

Step 4

Assume $INSTALLDIR is the top directory of DCNM-SAN installation. The above command is for single server instance, where 0 is the server ID.

Using Device Aliases or FC Aliases

You can change whether DCNM-SAN uses FC aliases or global device aliases from DCNM-SAN Client without restarting Cisco DCNM-SAN Server.

DETAILED STEPS
Step 1

Choose Server > Admin. You see the Control Panel dialog box with the Fabrics tab open. For each fabric that you are monitoring with Cisco DCNM-SAN Server, check or uncheckthe FC Alias check box. If you check the FC Alias checkbox, DCNM-SAN will use FC Alias from DCNM-SAN Client. If you uncheck the FC Alias checkbox, DCNM-SAN will use global device alias from DCNM-SAN Client.

Step 2

Step 3

Click Apply to save these changes.

Cisco DCNM Fundamentals Guide, Release 6.x

3-10

OL-25174-02

Chapter 3

Configuring Cisco DCNM-SAN Server Server Federation

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Server Federation
Server Federation is a distributed system that includes a collection of intercommunicated servers or computers that is utilized as a single, unified computing resource. With Cisco DCNM-SAN Server Federation, you can communicate with multiple servers together in order to provide scalability and easy manageability of data and programs running within the federation. The core of server federation includes several functional units such as Cisco DCNM-SAN Server, embedded web servers, database and DCNM-SAN Client that accesses the servers. The Cisco DCNM-SAN Server in the federation uses the same database to store and retrieve data. The database is shared among different servers to share common information. A DCNM-SAN Client or DCNM-SAN Web Client can open fabrics from the Cisco DCNM-SAN Server using the mapping table. A fabric can be moved from one logical server to another. A logical server also can be moved from one physical machine to another machine.

Restrictions

You cannot upgrade more than one Cisco DCNM-SAN Server in an existing federation. If you choose to do so, you may not be able to migrate the Performance Manager statistics and other information on that server. You may require to synchronize the time on all the DCNM-SAN Servers in a federated server environment.

Mapping Fabric ID to Server ID

The IP address of the physical server will be mapped to the server ID during the installation of the Cisco DCNM-SAN Server whenever the IP address of the physical server is changed, you need to map the IP address to the server ID using the PLMapping script provided with the Cisco DCNM-SAN Server. Whenever the you open or discover a fabric, the fabric ID will be mapped to the server ID . You can move a fabric to a different server ID using the control panel.

DETAILED STEPS
Step 1

Choose Server > Admin. You see the Control Panel. Select the fabric that you want to move to a different server and then click Move. You see the Move Fabric dialog box. You see the fabrics that you selected in the Fabrics to Move list box. From the Move To Server drop-down list select the server you want to move the fabric to. Click Move.

Step 2

Step 3 Step 4

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

3-11

Chapter 3 Server Federation

Configuring Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Opening the Fabric on a Different Server

DETAILED STEPS
Step 1

Choose Server > Admin. You see the Control Panel.

Step 2

Click Discover. You see the Discover New Fabric dialog box. In the Seed Switch list box, enter the IP Address of the seed switch. In the User Name field, enter the username. In the password field, enter the password. From the Auth-Privacy drop-down list, choose the privacy protocol you want to apply. To open the selected fabric in a different server, select the server ID from the Server drop-down list. Click Discover.

Step 3 Step 4 Step 5 Step 6 Step 7 Step 8

Note

You may receive an error message when you discover a fabric in a federation while another Cisco DCNM-SAN Server is joining the federation. You can discover the fabric on after the installation or upgradation is complete.

Viewing the Sessions in a Federation

DETAILED STEPS
Step 1 Step 2

Choose Server > Admin. Click the Connected Clients tab. You see the Control Panel.

Viewing the Servers in a Federation

DETAILED STEPS
Step 1 Step 2

Choose Server > Admin. Click the Servers tab. You see the Control Panel.

Cisco DCNM Fundamentals Guide, Release 6.x

3-12

OL-25174-02

Chapter 3

Configuring Cisco DCNM-SAN Server Additional References

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Additional References

Server Federation is a licensed feature. For more information on Cisco DCNM-SAN Server Licensing, see Cisco MDS 9000 Family NX-OS Licensing Guide. For more information on deploying Cisco DCNM-SAN Server in a federation, see Cisco Fabric Manager Server Federation Deployment Guide.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

3-13

Chapter 3 Additional References

Configuring Cisco DCNM-SAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

3-14

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

Configuring Authentication in Cisco DCNM-SAN

This chapter describes the interdependent software components in Cisco DCNM-SAN that communicate with the switches, authentication steps and the best practices for setting up your fabric and components for authentication. This chapter contains the following sections:

Information About Cisco DCNM-SAN Authentication, page 4-1 Best Practices for Discovering a Fabric, page 4-3 Performance Manager Authentication, page 4-4 Cisco DCNM-SAN Web Client Authentication, page 4-4

Information About Cisco DCNM-SAN Authentication

Cisco DCNM-SAN contains multiple components that interact to manage a fabric. These components include:

Cisco DCNM-SAN Client Cisco DCNM-SAN Server Performance Manager Interconnected fabric of Cisco MDS 9000 switches and storage devices AAA server (optional)

Figure 4-1 shows an example configuration for these components.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

4-1

Chapter 4 Information About Cisco DCNM-SAN Authentication

Configuring Authentication in Cisco DCNM-SAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 4-1 Cisco DCNM-SAN Authentication Example

AAA server

DCNM-SAN Server and Performance Manager

DCNM-SAN Client Fabric

130715

Local database

Administrators launch Cisco DCNM-SAN Client and select the seed switch that is used to discover the fabric. The user name and password used are passed to Cisco DCNM-SAN 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 Cisco DCNM-SAN Client or Cisco DCNM-SAN Server opens a CLI session to the switch (SSH or Telnet) and retries the user name and 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 Cisco DCNM-SAN Client and server.

Note

You may encounter a delay in authentication if you use a remote AAA server to authenticate Cisco DCNM-SAN or Device Manager.

Note

You must allow CLI sessions to pass through any firewall that exists between Cisco DCNM-SAN Client and Cisco DCNM-SAN Server.

Note

We recommend that you use the same password for the SNMPv3 user name authentication and privacy passwords as well as the matching CLI user name and password.

Cisco DCNM Fundamentals Guide, Release 6.x

4-2

OL-25174-02

Chapter 4

Configuring Authentication in Cisco DCNM-SAN Best Practices for Discovering a Fabric

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Best Practices for Discovering a Fabric

Cisco DCNM-SAN Server monitors multiple physical fabrics under the same user interface. This facilitates managing redundant fabrics. A licensed Cisco DCNM-SAN Server maintains up-to-date discovery information on all configured fabrics so device status and interconnections are immediately available when you launch Cisco DCNM-SAN Client.

Caution

If the Cisco DCNM-SAN Servers CPU usage exceeds 50 percent, it is recommended that you switch to a higher CPU-class system. We recommend that you use these best practices for discovering your network and setting up Performance Manager. This ensures that Cisco DCNM-SAN Server has a complete view of the fabric. Subsequent Cisco DCNM-SAN 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 Cisco DCNM-SAN Server using a network administrator or network operator role so that Cisco DCNM-SAN Server has a view of all the VSANs in the fabric. When a VSAN-limited user launches Cisco DCNM-SAN Client, that user sees only the VSANs they are allowed to manage.

Note

Cisco DCNM-SAN 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.

Setting Up Discovery for a Fabric

DETAILED STEPS
Step 1

Create a special Cisco DCNM-SAN administrative user name in each switch on your fabric with network administrator or network operator roles. Or, create a special Cisco DCNM-SAN 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 Cisco DCNM-SAN administrative user name are the same on all switches in the fabric and that this role has access to all VSANs. Launch Cisco DCNM-SAN Client using the Cisco DCNM-SAN administrative user. This step ensures that your fabric discovery includes all VSANs. Set Cisco DCNM-SAN Server to continuously monitor the fabric. Repeat Step 4 for each fabric that you want to manage through Cisco DCNM-SAN Server.

Step 2 Step 3 Step 4 Step 5

.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

4-3

Chapter 4 Performance Manager Authentication

Configuring Authentication in Cisco DCNM-SAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Performance Manager Authentication

Performance Manager uses the user name and password information stored in the Cisco DCNM-SAN Server database. If this information changes on the switches in your fabric while Performance Manager is running, you need to update the Cisco DCNM-SAN Server database and restart Performance Manager. Updating the Cisco DCNM-SAN Server database requires removing the fabric from Cisco DCNM-SAN Server and rediscovering the fabric.

DETAILED STEPS
Step 1

Click Server > Admin in Cisco DCNM-SAN. You see the Control Panel dialog box with the Fabrics tab open . Click the fabrics that have updated user name and password information. From the Admin listbox, choose Unmanage and then click Apply. Enter the appropriate user name and password and then click Apply. From the Admin listbox, choose Manage and then click Apply. To rediscover the fabric, click Open tab and check the check box(es) next to the fabric(s) you want to open in the Select column. Click Open to rediscover the fabric. Cisco DCNM-SAN Server updates its user name and password information. Repeat Step 3 through Step 7 for any fabric that you need to rediscover. Choose Performance > Collector > Restart to restart Performance Manager and use the new user name and password.

Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9

Cisco DCNM-SAN Web Client Authentication

Cisco DCNM-SAN Web Server does not communicate directly with any switches in the fabric. Cisco DCNM-SAN Web Server uses its own user name and password combination that is either stored locally or stored remotely on an AAA server. We recommend that you use a RADIUS or TACACS+ server to authenticate users in Cisco DCNM-SAN Web Server.

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4

Launch Cisco DCNM-SAN Web Client. Choose Admin > Management Users > Remote AAA to update the authentication used by Cisco DCNM-SAN Web Client. Set the authentication mode attribute to radius. Set the RADIUS server name, shared secret, authentication method, and ports used for up to three RADIUS servers.

Cisco DCNM Fundamentals Guide, Release 6.x

4-4

OL-25174-02

Chapter 4

Configuring Authentication in Cisco DCNM-SAN Cisco DCNM-SAN Web Client Authentication

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 5

Click Modify to save this information.

Step 1 Step 2 Step 3 Step 4 Step 5

Launch Cisco DCNM-SAN Web Client. Choose Admin > Management Users > Remote AAA to update the authentication used by Cisco DCNM-SAN Web Client. Set the authentication mode attribute to tacacs. Set the TACACS+ server name, shared secret, authentication method, and port used for up to three TACACS+ servers. Click Modify to save this information.

Note

Cisco DCNM-SAN does not support SecureID because it is not compatible with SNMP authentication. Cisco DCNM-SAN uses the same login credentials for all the switches in a fabric. Since SecureID cannot be used more than once for authentication, Cisco DCNM-SAN will not be able to establish a connection to the second switch using a SecureID.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

4-5

Chapter 4 Cisco DCNM-SAN Web Client Authentication

Configuring Authentication in Cisco DCNM-SAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

4-6

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

Configuring Cisco DCNM-SAN Client

This chapter describes about the Cisco DCNM-SAN Client, which is a java-based GUI application that provides access to the Cisco DCNM-SAN applications from a remote workstation. This chapter contains the following sections:

Information About DCNM-SAN Client, page 5-1 Cisco DCNM-SAN Client Quick Tour: Server Admin Perspective, page 5-2 Cisco DCNM-SAN Client Quick Tour: Admin Perspective, page 5-7 Launching Cisco DCNM-SAN Client, page 5-24 Setting Cisco DCNM-SAN Preferences, page 5-28 Network Fabric Discovery, page 5-30 Modifying the Device Grouping, page 5-31 Controlling Administrator Access with Users and Roles, page 5-32 Using Cisco DCNM-SAN Wizards, page 5-32 Cisco DCNM-SAN Troubleshooting Tools, page 5-33 Integrating Cisco DCNM-SAN and Data Center Network Management Software, page 5-34

Information About DCNM-SAN Client

Cisco DCNM-SAN is a Java and SNMP-based network fabric and device management tool with a GUI that displays real-time views of your network fabric, including Cisco Nexus 5000 Series switches, Cisco MDS 9000 Family and third-party switches, hosts, and storage devices. In addition to complete configuration and status monitoring capabilities for Cisco MDS 9000 Family switches and Cisco Nexus 5000 Series switches, Cisco DCNM-SAN Client provides Fibre Channel troubleshooting tools. You can use these health and configuration analysis tools on the MDS 9000 Family switch or Cisco Nexus 5000 Series switch to perform Fibre Channel ping and traceroute. Cisco DCNM-SAN Release 4.1(1b) and later provides multilevel security system by adding a server admin role that allows access to limited features. The configuration capabilities of a server admin is limited to FlexAttach and relevant data.

Note

You must use the same release of Cisco DCNM-SAN Client and Cisco DCNM-SAN Server.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-1

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Server Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM-SAN Advanced Mode

Advanced mode is enabled by default and provides the full suite of Cisco DCNM-SAN features, including security, IVR, iSCSI, and FICON. To simplify the user interface, from the list box in the upper right corner of the Cisco DCNM-SAN Client, choose Simple. In simple mode, you can access basic MDS 9000 features such as VSANs, zoning, and configuring interfaces. Advanced mode option is not available for server admin role.

Cisco DCNM-SAN Client Quick Tour: Server Admin Perspective

Cisco DCNM-SAN provides a multilevel security system by adding a server admin role that allows access only to limited features. The configuration capabilities of a server admin role is limited to FlexAttach and relevant data. The server admin can pre-configure SAN for new servers, move a server to another port on the same NPV device or another NPV device and replace a failed server onto the same port without involving the SAN administrator. The server role admin will not be able to manage Cisco DCNM-SAN users or connected clients. Cisco DCNM-SAN provides a much improved user interface by including movable and dockable panes to let users arrange the Physical Attributes pane, Logical Domains pane, Fabric pane and Information pane according to requirements, making it easier to manage the workflow. The dockable panes are also called as dockable frames. A dockable frame can be standalone (floating), minimized or maximized. The logical, physical, information and the fabric panes can be can be collapsed and expanded as needed. These panes can also be docked at either the right side left side or to the bottom of the workspace.

Cisco DCNM-SAN Main Window

This section describes the Cisco DCNM-SAN Client interface that is specific to server admin users as shown in Figure 5-1.

Cisco DCNM Fundamentals Guide, Release 6.x

5-2

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Server Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 5-1 Cisco DCNM-SAN Main Window: Server Admin Perspective

1 2 3 4 5 6 7 8

Menu barProvides access to options that are organized by menus. ToolbarProvides icons for direct access to the most commonly used options on the File, Tools, and Help menus. Information paneDisplays information about whatever option is selected in the menu tree. Status Bar (right side)Shows the last entry displayed by the discovery process and the possible error message. Fabric paneDisplays a map of the network fabric, including switches, hosts, and storage. It also provides tabs for displaying log and event data. Status Bar (left side)Shows short-term transient messages, such as the number of rows displayed in a table. Physical Attributes paneDisplays a tree of available configuration tasks depending on the fabric, VSAN, or zone selected previously. Lists the switches in the logical selection. Logical Domains paneDisplays a tree of configured SAN, fabrics and user-defined groups.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-3

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Server Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Menu Bar
The menu bar at the top of the Cisco DCNM-SAN main window provides options for managing and for controlling the display of information on the Fabric pane. Server admin will not have all the options that are available for SAN admin. The menu bar provides the following menus:

FileOpens a new fabric, rediscovers the current fabric, locates switches, sets preferences, prints the map. ViewChanges the appearance of the map (these options are duplicated on the Fabric pane toolbar). ToolsManages the Server and configuration using the FlexAttach virtual pWWN feature. HelpDisplays online help topics for specific dialog boxes in the Information pane.

Tool Bar
The Cisco DCNM-SAN main toolbar (specific to server admin) provides icons for accessing the most commonly used menu bar options as shown in Table 5-1.
Table 5-1 Cisco DCNM-SAN Client Main Toolbar

Icon

Description Opens switch fabric.

Rediscovers current fabric.

Finds in the map.

Shows online help.

Logical Domains Pane

Use the Logical Domains pane to view fabrics and to access user-defined groups. You can expand the groups to see different user-defined groups. The non-editable groups created for each core switch contains their NPV switches.

Physical Attributes Pane

Use the Physical Attributes pane to display a tree of the options available for managing the switches in the currently selected fabric or group.

Cisco DCNM Fundamentals Guide, Release 6.x

5-4

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Server Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
To select an option, click a folder to display the options available and then click the option. You see the table with information for the selected option in the Information pane. The Physical Attributes pane provides the following main folders:

SwitchesViews and configures hardware, system, licensing, and configuration files. InterfacesViews and configures FC physical, FC logical, VFC (FCoE), Ethernet, SVC, and PortChannel interfaces.

Information Pane
Use the Information pane to display tables of information associated with the option selected from the menu tree in the Logical Domains or Physical Attributes panes. The Information pane toolbar provides buttons for performing one or more of the operations shown in Table 5-2.
Table 5-2 Information Pane Toolbar

Icons

Description Applies configuration changes.

Refreshes table values.

Copies data from one row to another.

Pastes the data from one row to another.

Undoes the most recent change.

Finds a specified string in the table.

Exports and saves information to a file.

Prints the contents of the Information pane.

Displays a non-editable copy of the table in the Information pane in its own window, which you can move around the screen.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-5

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Server Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Fabric Pane
Use the Fabric pane to display the graphical representation of your fabric. Table 5-1 explains the graphics you may see displayed, depending on which devices you have in your fabric. The bottom of the Fabric pane has the following tabs:

FabricWhen displaying multiple fabrics, each fabric has its own tab. You can switch between fabrics by clicking on their respective tabs. LogDisplays messages that describe Cisco DCNM-SAN operations, such as fabric discovery. EventsDisplays information about the SNMP traps received by the management station. This includes combination events as detected by discovery and important traps such as license, SNMP, and FICON.

Note

Fabric map display is based on what you select in the logical domain pane. When you select a fabric node, all the switches that belong to that fabric will be enabled. When you select the group node, all the switches that belong to the groups listed under that group node will be enabled. When you select only a group, all the switches that belong to the specific group will be enabled.

Cisco DCNM Fundamentals Guide, Release 6.x

5-6

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM-SAN Client Quick Tour: Admin Perspective

This section describes the Cisco DCNM-SAN Client interface shown in Figure 5-2.
Figure 5-2 Cisco DCNM-SAN Main Window

1 2 3 4 5

Menu barProvides access to options that are organized by menus. ToolbarProvides icons for direct access to the most commonly used options on the File, Tools, and Help menus. Information paneDisplays information about whatever option is selected in the menu tree. Status Bar (right side)Shows the last entry displayed by the discovery process and the possible error message. Fabric paneDisplays a map of the network fabric, including switches, hosts, and storage. It also provides tabs for displaying log and event data.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-7

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
6 7 Status Bar (left side)Shows short-term transient messages, such as the number of rows displayed in a table. Physical Attributes paneDisplays a tree of available configuration tasks depending on the fabric, VSAN, or zone selected previously. Lists the switches and end devices in the logical selection. Logical Domains paneDisplays a tree of configured SAN, fabrics, VSANs, and zones, and provides access to user-defined groups. The label next to the segmented VSAN indicates the number of segments.

Note

You can resize each pane by dragging the boundaries between each region or by clicking the Minimize or Maximize controls.

Menu Bar
The menu bar at the top of the Cisco DCNM-SAN main window provides options for managing and troubleshooting the current fabric and for controlling the display of information on the Fabric pane. The menu bar provides the following menus:

FileOpens a new fabric, rediscovers the current fabric, locates switches, sets preferences, prints the map, and exports the Fabric pane log. ViewChanges the appearance of the map (these options are duplicated on the Fabric pane toolbar). ZoneManages zones, zone sets, and inter-VSAN routing (IVR). ToolsVerifies and troubleshoots connectivity and configuration, as described in the Cisco DCNM-SAN Troubleshooting Tools section on page 5-33. PerformanceRuns and configures Performance Manager and Cisco Traffic Analyzer, and generates reports. ServerRuns administrative tasks on clients and fabrics. Provides Cisco DCNM-SAN Server management and a purge command. Lists fabrics being managed. HelpDisplays online help topics for specific dialog boxes in the Information pane.

File
The file menu provides the following options:

Open FabricOpens a new switch fabric. Locate Switches and Devices Uses the SNMPv2 protocol to discover devices responding to SNMP requests with the read-only community string public. You may use this feature if you want to locate other Cisco MDS 9000 switches in the subnet, but are not physically connected to the fabric. RediscoverInitiates an on-demand discovery to learn recent changes from the switches and update the Cisco DCNM-SAN Client. You may use this option when Cisco DCNM-SAN Server is not in sync with switches in the fabric and you do not want to wait until the next polling cycle. The rediscover option does not delete the fabric and add it again. You may delete and add the fabric only if the rediscover option fails to update Cisco DCNM-SAN Server.

Cisco DCNM Fundamentals Guide, Release 6.x

5-8

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Resync All Open Fabrics Cisco DCNM-SAN Server forces all the fabrics to close and re-open. You may use this option when Cisco DCNM-SAN Client is not in sync with Cisco DCNM-SAN Server. Rediscover SCSI Targets Initiates an on-demand discovery to learn recent changes from the SCSI target switches. You may use this option when Cisco DCNM-SAN Server is not in sync with SCSI target switches in the fabric and you do not want to wait until the next polling cycle. PreferencesSets your preferences to customize the behavior of the Cisco DCNM-SAN Client. Import EnclosuresImports saved enclosures. Export
Map ImageGenerates and export the map to a specified location. VisioExports the map to a Visio file. TableExports the table data to a text file. LogExports the log to a text file. EventsExports the events to a text file. EnclosuresExports the enclosure values to a text file.

Print Prints the map. ExitExit Cisco DCNM-SAN.

View
View menu provides the following options:

Refresh MapRefreshes the current map. Layout

CancelCancels the current layout. SpringDisplays the layout based on spring algorithm. QuickQuickly displays the layout when the switch has many end devices.

Zoom
InZooms in the view. OutZooms out the view. FitFits the view in the fabric pane.

GridEnables the grid view. Overview WindowAllows you to center the Fabric pane on the area of the fabric that you want to see. This option is useful for large fabrics that cannot be displayed entirely within the Fabric pane. LegendShows all the legends used in the fabric map. Find in MapFinds a device in the fabric map.

Zone
The zone menu provides the following options:

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-9

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Edit Local Full Zone DatabaseAllows you to create zones across multiple switches. Zones provide a mechanism for specifying access control. Zone sets are a group of zones to enforce access control in the fabric. All zoning features are available through the Edit Local Full Zone Database dialog box. Deactivate ZonesetDeactivates an active zone set. Copy Full Zone DatabaseCreates a new zone set. On the Cisco MDS Family switches, you cannot edit an active zone set. However, you can copy an active zone set to create a new zone set that you can edit. Merge AnalysisEnables you to determine if zones will merge successfully when two Cisco MDS switches are interconnected. If the interconnected switch ports allow VSANs with identical names or contain zones with identical names, then Cisco DCNM-SAN verifies that the zones contain identical members. You can use merge analysis tool before attempting a merge, or after fabrics are interconnected to determine zone merge failure causes. Merge Fail RecoveryRecovers the port from its isolated state either by importing the neighboring switch's active zone set database and replacing the current active or by exporting the current database to the neighboring switch. Migrate Non-MDS DatabaseMigrate a non-MDS database using Cisco DCNM-SAN (you may need to use the Zone Migration Wizard to accomplish this task). IVR
Deactivate ZonesetDeactivates an active zone set. Copy Full Zone DatabaseRecovers an IVR zone database by copying the IVR full zone

database from another switch.

Copy Full TopologyRecovers a topology by copying from the active zone database or the full

zone database.

Tools
Tools menu provides the following options:

Health
Switch HealthDetermines the status of the components of a specific switch. Fabric ConfigurationAnalyzes the configuration of a switch by comparing the current

configuration to a specific switch or to a policy file. You can save a switch configuration to a file and then compare all switches against the configuration in the file.
Show Tech SupportCollects large amount of information about your switch for

troubleshooting purposes. When you issue a show tech support command from Cisco DCNM-SAN for one or more switches in a fabric, the results of each command are written to a text file, one file per switch, in a directory you specify. You can then view these files using Cisco DCNM-SAN.

Connectivity
End to End ConnectivityDetermines connectivity and routes among devices with the switch

fabric. This tool checks to see that every pair of end devices can talk to each other, using a Ping test and by determining if they are in the same VSAN or in the same active zone.
PingDetermines connectivity from another switch to a port on your switch. Trace RouteVerifies connectivity between two end devices that are currently selected on the

Fabric pane.

Cisco DCNM Fundamentals Guide, Release 6.x

5-10

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Compact Flash ReportAutomatically scans the fabric and generate a report that shows the

status of CompactFlash.

NPV
CFS Static Peer SetupManage the peer list used during CFS on NPV-enabled switches. After

setting up the static peers list, the CFS discovery on the switches will be changed to static mode for all peers in the list. Cisco DCNM-SAN does not automatically update static peers list. You may need to update the list using the CFS Static Peer Setup Wizard when a new switch is added to the fabric.
Traffic Map SetupConfigures the list of external interfaces to the servers, and enabling or

disabling disruptive load balancing. Using Traffic Map Setup you can specify the external ports that a server should use for traffic management.
Flex Attach Pre-Configure ServerSets the port configurations for all the ports in a switch such

as enabling or disabling FlexAttach, setting the default VSAN ID, and setting the interface status.
Flex Attach Move ServerMoves a server to another port on the same NPV device or another

NPV device without changing the SAN.

Flex Attach Replace ServerReplaces a failed server with a new server on the same port

without changing the SAN.

Data Mobility Manager

Server BasedPerforms server-based data migration. Storage basedPerforms storage-based data migration. Server LUN DiscoveryPerforms LUN discovery to select the LUNs available for migration

and automates the session creation by matching the LUNs in the existing and new storage.

FCoELaunches the FCoE Configuration Wizard to create virtual Fibre Channel interfaces. Port ChannelCreates PortChannels from selected ISL either manually or automatically. DPVM SetupEstablishes dynamic port VSAN membership, enables autolearning, and activates the DPVM database. IP SAN
FCIP TunnelCreates FCIP links between Gigabit Ethernet ports. Enables Fibre Channel write

acceleration and IP compression.

iSCSI SetupCreates zones for iSCSI initiators and adds a VSAN to a target-allowed VSAN

list.
SAN Extension TunerOptimizes FCIP performance by generating either direct access

(magnetic disk) or sequential access (magnetic tape) SCSI I/O commands and directing such traffic to a specific virtual target. This option is used to generate SCSI I/O commands (read and write) to the virtual target based on your configured options.

Security
Port SecurityPrevents unauthorized access to a switch port in the Cisco MDS 9000 Family,

rejects intrusion attempts and reports these intrusions to the administrator.

IP ACLCreates an ordered list of IP filters in a named IPv4-ACL or IPv6-ACL profile using

the IPv4-ACL Wizard.

Install
LicenseFacilitate download and installation of licenses in selected switches in the fabric.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-11

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
SoftwareVerifies image compatibility and installs software images on selected switches in the

fabric.

Flow Load Balance CalculatorAllows you to get the best load-balancing configuration for your FICON flows. The calculator does not rely on any switch or flow discovery in the fabric. Device ManagerInvokes Device Manager for a switch. Command Line Interface Enables command-line operations. Run CLI CommandsRuns command-line operations on more than one switch at a time.

Performance
The performance menu provides the following options:

Create FlowsCreates host-to-storage, storage-to-host, or bidirectional flows. You can add these flows to a collection configuration file to monitor the traffic between a host or storage element pair.

Server
The server menu provides the following options:

AdminOpens the control panel. Purge Down ElementsPurges all down elements in the fabric.

Help
The help menu provides the following options:

Contents Launches the online help contents. Config GuideLaunches the Cisco DCNM-SAN Configuration Guide. AboutDisplays information about Cisco DCNM-SAN.

Toolbar
The Cisco DCNM-SAN main toolbar provides icons for accessing the most commonly used menu bar options as shown in Table 5-3.
Table 5-3 Cisco DCNM-SAN Client Main Toolbar

Icon

Description Opens switch fabric.

Rediscovers current fabric.

Finds in the map.

Cisco DCNM Fundamentals Guide, Release 6.x

5-12

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 5-3 Cisco DCNM-SAN Client Main Toolbar (continued)

Icon

Description Creates VSAN.

Launches DPVM wizard.

Launches Port Security wizard.

Edits full zone database.

Launches IVR zone wizard.

Launches the FCoE configuration wizard.

Launches PortChannel wizard.

Launches FCIP wizard.

Launches iSCSI wizard.

Launches NPVM wizard.

Launches QoS wizard.

Configures users and roles.

Launches IP-ACL wizard.

Launches License Install wizard.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-13

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 5-3 Cisco DCNM-SAN Client Main Toolbar (continued)

Icon

Description Launches Software Install wizard.

Performs switch health analysis.

Performs fabric configuration analysis.

Performs end-to-end connectivity analysis.

Monitors ISL performance. Brings up real-time ISL performance information for all interfaces in the fabric, in the Information pane. Shows online help.

Logical Domains Pane

Use the Logical Domains pane to manage attributes for fabrics, VSANs, and zones, and to access user-defined groups. Starting from NX-OS Release 4.2(0), SAN and LAN nodes are listed under Datacenter node and all the fabrics are listed under SAN node. When you select Datacenter node in the tree, Cisco DCNM-SAN displays all the switches and ISLs. When you select LAN node, Cisco DCNM-SAN displays only Ethernet switches and Ethernet links. Under the fabric node, VSANs are ordered by a VSAN ID. The segmented VSANs are placed under the fabric node. The label next to the segmented VSAN indicates the number of segments. You can expand a segmented VSAN and the segments under that VSAN. Right-click one of the folders in the tree and click a menu item from the pop-up menu. You see the appropriate configuration dialog box. The default name for the fabric is the name, IP address, or WWN for the principal switch in VSAN 1. If VSAN 1 is segmented, the default name is chosen from a principal switch with the smallest WWN. The fabric names you see are as follows:

Fabric <sysName> Fabric <ipAddress> Fabric <sWWN>

You can change the fabric name using Cisco DCNM-SAN.

DETAILED STEPS
Step 1

Choose Server > Admin. You see the Control Panel dialog box.

Cisco DCNM Fundamentals Guide, Release 6.x

5-14

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2 Step 3

Double-click the fabric name and enter the new name of the fabric. Click Apply to change the name.

Filtering
Cisco DCNM-SAN has a filtering mechanism that displays only the data that you are interested in. To filter, first select the fabric and VSAN from the Logical Domains pane. This action narrows the scope of what is displayed in the Fabric pane. Any information that does not belong to the selected items is dimmed. Also, any information that does not belong to the selected items is not displayed in the tables in the Information pane. The filter that you select is displayed at the top right of the Cisco DCNM-SAN window. To further narrow the scope, select attributes from the Physical Attributes pane. The Cisco DCNM-SAN table, display, and filter criteria change accordingly.

Physical Attributes Pane

Use the Physical Attributes pane to display a tree of the options available for managing the switches in the currently selected fabric, VSAN, or zone. To select an option, click a folder to display the options available and then click the option. You see the table with information for the selected option in the Information pane. The Physical Attributes pane provides the following main folders:

SwitchesViews and configures hardware, system, licensing, and configuration files. InterfacesViews and configures FC physical, FC logical, VFC (FCoE), Ethernet, SVC, and PortChannel interfaces. FC ServicesViews and configures Fibre Channel network configurations. IPViews and configures IP storage and IP services. EventsViews and configures events, alarms, thresholds, notifications, and informs. SecurityViews and configures MDS management and FC-SP security. FCoEViews and configures FCoE interfaces. ISLsViews and configures Inter-Switch Links. End DevicesViews and configures end devices.

Note

You cannot view the detailed physical attributes of the data center switches or monitor the connections. When you select either a data center node or a LAN node the physical attributes pane will be blank.

Context Menu for Tables

When you right-click in the table, you see a pop-up menu with options that vary depending on the type of option you selected in the Physical Attributes pane. You can perform various operations by right-clicking the device listed in the table. To view various options available for switches, ISLs, and end devices, refer to the procedures in the sections that follows:

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-15

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Viewing Switch Options
When you select the datacenter node, the switch table displays all the switches that are discovered. When you select the SAN node or the fabric node, the switch table displays all the Fibre Channel switches and when you select the LAN node, the switch table displays all the Ethernet switches.

DETAILED STEPS
Step 1 Step 2

Click Switches in the Physical Attributes pane. Right-click the device in the table. The pop-up menu provides the following options:

Apply ChangesApplies the changes to the switch. Refresh ValuesRefreshes the current values. Undo ChangesUndoes modifications to the switch. Export to FileExport the values to a file. Print TablePrints the table. Detach TableDetaches the table. Switch AttributesChanges the switch properties. Interface AttributesChanges the interface properties. Element ManagerManages this switch. Command Line InterfaceEnables to perform command line operations. CopyCopies the switch. PurgePurges the switch. Fix LocationFixes the switch in the current location. AlignAligns the switch. Show End DevicesShows the end devices. Expand Multiple LinksExpands the links to this switch. OtherOther options. GroupGroups switches.

Viewing ISL Options

When you select the data center node, the ISLs table displays all of the Fibre Channel and Ethernet links. When you select the LAN node, the ISLs table displays all the Ethernet links.

DETAILED STEPS
Step 1 Step 2

In the Physical Attributes pane, click ISLs and then click Summary tab. Right-click the device in the table. The pop-up menu provides the following options:

Refresh ValuesRefreshes the current values.

Cisco DCNM Fundamentals Guide, Release 6.x

5-16

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CopyCopies information from a specific field. FindConducts search based on the input string. Export to FileExports the values to a file. Print TablePrints the table. Detach TableDetaches the table. Interface AttributesChanges the interface properties. Element ManagerManages the device. FCIP Tunnel AttributesChanges FCIP tunneling properties. Create Port ChannelCreates port channel. Re-enableReenables a disabled device. Enable FC-SPEnables FC-SP. SAN Extention TunerOptimizes FCIP performance. PurgePurges the device.

Note

When you select a port channel from the table, the pop-up menu will have the following additional options:

Member AttributesChanges the member properties. Channel AttributesChanges the port channel properties. EditEdits the channel properties.

Viewing End Device Options DETAILED STEPS

Step 1 Step 2

In the Physical Attributes pane, click End Devices and then click the Summary tab. Right-click the device in the table. The pop-up menu provides the following options:

Apply ChangesApplies the changes to the device. Refresh ValuesRefreshes the current values. CopyCopies the information specific to the field. PastePastes the copied text. Undo ChangesUndoes modifications to the device. FindSearches for information depending on the input string. Export to FileExports the values to a file. Print TablePrints the table. Detach TableDetaches the table. Device AttributesChanges the device properties. Interface AttributesChanges the interface properties.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-17

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Element ManagerManages this device. Command Line InterfaceEnables you to perform command line operations. CopyCopies the switch. PurgePurges the switch. Fix LocationFixes the switch in the current location. AlignAligns the switch. PingPings another device. Trace RouteDetermines the route taken by packets across the network. Select Dependent PortsSelects dependent ports. GroupGroups devices.

Information Pane
Use the Information pane to display tables of information associated with the option selected from the menu tree in the Logical Domains or Physical Attributes panes. The Information pane toolbar provides buttons for performing one or more of the operations shown in Table 5-4.
Table 5-4 Information Pane Toolbar

Icon

Description Applies configuration changes.

Refreshes table values.

Opens the appropriate dialog box to make a new row in the table. Deletes the currently highlighted rows from the table. Copies data from one row to another.

Pastes the data from one row to another.

Undoes the most recent change.

Cisco DCNM Fundamentals Guide, Release 6.x

5-18

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 5-4 Information Pane Toolbar (continued)

Icon

Description Finds a specified string in the table.

Exports and saves information to a file.

Prints the contents of the Information pane.

Displays a non-editable copy of the table in the Information pane in its own window, which you can move around the screen.

Note

After making changes, you must save the configuration or the changes will be lost when the device is restarted.

Note

The buttons that appear on the toolbar vary according to the option that you select. They are activated or deactivated (dimmed) according to the field or other object that you select in the Information pane.

Detachable Tables
Detachable tables in Cisco DCNM-SAN allow you to detach tables and move them to different areas on your desktop so that you can compare similar tables from different VSANs. You can keep informational tables open from one view while you examine a different area in Cisco DCNM-SAN. To detach tables, click the Detach Table icon in the Information pane in Cisco DCNM-SAN.

Fabric Pane
Use the Fabric pane to display the graphical representation of your fabric. Table 5-5 explains the graphics you may see displayed, depending on which devices you have in your fabric.
Table 5-5 Cisco DCNM-SAN Graphics

Icon or Graphic

Description Director class MDS 9000 Fibre Channel switch.

iSAN

Non-director class MDS 9000 Fibre Channel switch.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-19

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 5-5 Cisco DCNM-SAN Graphics (continued)

Icon or Graphic

Description Nexus 7000 switch.

Nexus FCoE or Fibre Channel switch.

Catalyst LAN switch.

Generic Fibre Channel switch.

Cisco SN5428.

Dashed or dotted orange line through a device indicates that the device is manageable but there are operational problems. Dashed or dotted orange X through a device or link indicates that the device or ISL is not working properly. A red line through a device indicates that the device is not manageable. A red X through a device or link indicates that the device is down or that the ISL is down. Fibre Channel HBA (or enclosure).

Fibre Channel target (or enclosure).

iSCSI host.
Terminal blocks

1 2 3
99509

Fibre Channel ISL and edge connection.

Fibre Channel PortChannel.

Cisco DCNM Fundamentals Guide, Release 6.x

5-20

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 5-5 Cisco DCNM-SAN Graphics (continued)

Icon or Graphic

Description IP ISL and edge connection.

IP PortChannel.

DWDM connection.

NPV connection.

Fibre Channel loop (storage).

IP cloud (hosts). This icon is also used to represent a fabric when viewing a SAN (multiple fabrics) in the Cisco DCNM-SAN Fabric pane. Any device, cloud, or loop with a box around it means that there are hidden links attached.

If a switch or director is grayed out, Cisco DCNM-SAN can no longer communicate with it. The bottom of the Fabric pane has the following tabs:

FabricWhen displaying multiple fabrics, each fabric has its own tab. You can switch between fabrics by clicking on their respective tabs. LogDisplays messages that describe Cisco DCNM-SAN operations, such as fabric discovery. EventsDisplays information about the SNMP traps received by the management station. This includes combination events as detected by discovery and important traps such as license, SNMP, and FICON. Turn off end device labels. Collapse loops. Collapse expanded multiple links (collapsed multiple links are shown as very thick single lines). Dim or hide portions of your fabric by VSAN.

When viewing large fabrics in the Fabric pane, it is helpful to do the following tasks:

Note

When a VSAN, zone, or zone member is selected in the VSAN tree, the map highlighting changes to identify the selected objects. To remove this highlighting, click the Clear Highlight button on the Fabric pane toolbar or choose Clear Highlight from the pop-up menu.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-21

Chapter 5 Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Context Menus
When you right-click an icon in the Fabric pane, you see a pop-up menu with options that vary depending on the type of icon selected. The various options available for different objects include the following:

Open an instance of Device Manager for the selected switch. Open a CLI session for the selected switch. Copy the display name of the selected object. Execute a ping or traceroute command for the device. Show or hide end devices. View attributes. Quiesce and disable members for PortChannels. Set the trunking mode for an ISL. Create or add to a PortChannel for selected ISLs.

The Fabric pane has its own toolbar with options for saving, printing, and changing the appearance of the map. When you right-click the map, a pop-up menu appears that provides options (duplicated on the toolbar) for changing the appearance of the map.

Note

You can launch web-based or non-web-based applications from the Fabric pane. To do this, you assign an IP address to the storage port or enclosure. Then right-click to bring up the pop-up menu, and select Device Manager.

Saving the Map

You can save the map in the Fabric Pane as an image, or as an editable Visio diagram. You can save the map with or without labels on the links. The created Visio diagram is editable and saved in two layers:

The default layer includes all switches and links in the fabric. The end devices layer includes the end devices and can be turned off to remove end devices from the Visio diagram.

To save the map as a Visio diagram, choose Files > Export > Visio and choose Map or Map with link labels. The saved Visio diagram retains the viewing options that you selected from the Fabric pane. For example, if you collapse multiple links in the map and export the links as a Visio diagram, the Visio diagram shows those multiple links as one solid link. The Show Tech Support option from the Tools menu also supports saving the map as a Visio diagram.

Purging Down Elements

The Fabric pane allows you to refresh the map at any time by clicking the Refresh Map icon. The Refresh Map icon redraws the map but does not purge elements that are down. To purge down elements you can:

Choose Server > Purge Down Elements. This purges all down elements in the fabric. Right-click the Fabric pane and choose Purge Down Elements. Right-click a down element and choose Purge. This action purges only this element from the fabric.

Cisco DCNM Fundamentals Guide, Release 6.x

5-22

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Client Quick Tour: Admin Perspective

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

If you select an element that is not down and purge it, that element will reappear on the next fabric discovery cycle.

Multiple Fabric Display

Cisco DCNM-SAN can display multiple fabrics in the same pane. The information for both fabrics is displayed; you do not need to select a seed switch. To see details of a fabric, select the tab for that fabric at the bottom of the Fabric pane, or double-click the Cloud icon for the fabric in the SAN tab.

Note

Enclosure names should be unique. If the same enclosure name is used for each port, Cisco DCNM-SAN shows a host/target enclosure connected to both fabrics. To fix this problem, you can either disable auto-creation or create unique enclosure names.

Filtering by Groups
You can filter the Fabric pane display by creating groups of switches or end ports.

DETAILED STEPS
Step 1

Right-click a switch or end port in the Fabric pane map and select Group > Create. You see the Edit User Defined Group dialog box . Enter a group name in the Name field. Use the arrows to move additional switches or end ports from the Available column to the Selected column. Click OK to save the group.

Step 2 Step 3 Step 4

To add a switch or end port to an existing group in Cisco DCNM-SAN.

DETAILED STEPS
Step 1

Right-click a switch or end device and select Group > Add To > YourGroupName. You see the Edit User Defined Group dialog box. Use the arrows to move additional switches or end ports from the Available column to the Selected column. Click OK to save the updated group.

Step 2 Step 3

To filter the display by a group you have created.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-23

Chapter 5 Launching Cisco DCNM-SAN Client

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

Expand the Groups folder in the Logical Domains pane. You see the list of groups that you have created. Click the name of the group that you want to filter. In the Fabric pane, the switches or end devices in your group are shown normally; all other switches and end devices are shown in gray.

Step 2

Step 3

Click the Groups folder in the Logical Domains pane to return the display to normal.

Note

User-defined groups tables are filtered based on switches in the group except for switches where CFS-controlled features are enabled when all CFS member switches are displayed to avoid misconfigurations.

Status Bar
The status bar at the bottom of the Cisco DCNM-SAN window shows the last entry displayed by the discovery process, and the possible error message on the right side. The status bar displays a message stating that something has changed in the fabric and a new discovery is needed. The status bar shows both short-term, transient messages (such as the number of rows displayed in the table) and long-term discovery issues.

Launching Cisco DCNM-SAN Client

As of Cisco SAN-OS 3.x and NX-OS Release 4.x, the Fabric Manager Client login procedure has changed. If you are running a version of Cisco SAN-OS that is earlier than Cisco SAN-OS 3.2(1), follow the login instructions in the Setting the Seed Switch in Cisco SAN-OS Releases 3.1(1) to 3.2(1) section on page A-1 or the Setting the Seed Switch in Releases Prior to Cisco SAN-OS Release 3.1(1) section on page A-2.

Launching Fabric Manager Client in Cisco SAN-OS Release 3.2(1) and Later
You can launch Fabric Manager Client.

Note

Network administrators must initially launch Cisco DCNM-SAN Client using Cisco DCNM-SAN Web Server, as described in the following procedure. Once an administrator has installed the Cisco DCNM-SAN Client icon on your desktop, you can double-click the icon to launch the Cisco DCNM-SAN Client.

Cisco DCNM Fundamentals Guide, Release 6.x

5-24

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Launching Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

Open your browser and enter the IP address where you installed Cisco DCNM-SAN Server, or enter localhost if you installed Cisco DCNM-SAN Server on your local workstation. You see the Cisco DCNM Web Client Login dialog box. Enter your user name and password and click Login. You see the Cisco DCNM Web Client Summary page. Click the Download link in the upper right corner of the page. You see the Download page for Cisco DCNM-SAN and Device Manager. Click the link for Cisco DCNM-SAN. If you are launching Cisco DCNM-SAN Client for the first time, you see a message asking whether you want to create shortcuts for Cisco DCNM-SAN.

Step 2

Step 3

Step 4

Step 5

Click Yes to create shortcuts for Cisco DCNM-SAN.

Note

This message only appears the first time you launch Cisco DCNM-SAN Client. If you select No, your selection will be remembered and you will not be prompted to make a selection again. In this case, you will need to launch Cisco DCNM-SAN Client using the Cisco DCNM-SAN Web Client.

Step 6

When the software is installed and icons are created on your desktop, double-click the Cisco DCNM-SAN icon to launch Cisco DCNM-SAN. You see the Cisco DCNM-SAN Login dialog box. Enter the Cisco DCNM-SAN Server user name and password. Check the Use SNMP Proxy check box if you want Cisco DCNM-SAN Client to communicate with Cisco DCNM-SAN Server through a TCP-based proxy server. Click Login. Once you successfully log in to Cisco DCNM-SAN Server, you can set the seed switch and open the fabrics that you are entitled to access.

Step 7 Step 8 Step 9

Note

When you launch Cisco DCNM-SAN Client for the first time or when there are no available fabrics, you see the Discover New Fabric dialog box.

You see the Discover New Fabric dialog box.

Note Step 10 Step 11

Only network administrators can discover new fabrics.

Click the Ethernet (CDP) radio button to discover using Cisco Discovery Protocol (CDP). Starting from NX-OS Release 4.2(0), Fabric Manager uses Cisco Discovery Protocol to discover Ethernet switches such as Nexus 5000, Nexus 7000, Catalyst 4000, and Catalyst 6000 switches. You need to use a CDP seed switch for a CDP discovery. Set the fabric seed switch to the Cisco MDS 9000 Family switch or Cisco Nexus 5000 Series that you want Fabric Manager to use.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-25

Chapter 5 Launching Cisco DCNM-SAN Client

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 12

Choose the Auth-Privacy option according to the privacy protocol you have configured on your switch:
a. b.

If you have not configured the switch with a privacy protocol, then choose Auth-Privacy option MD5 (no privacy). If you have configured the switch with your privacy protocol, choose your Auth-Privacy choice.

Note

You may use SNMP v2 credentials for CDP discovery as the most of the Catalyst switches do not use MD5-DES for configuration.

Note

If you want a clean fabric discovery, remove the fabric and rediscover it. If you want a clean LAN discovery, unmanage LAN, remove the CDP seed switch and then rediscover it.

Step 13 Step 14

Enter the username and password for the switch. (Optionsl) To limit the discovery, specify the VSAN range. Scoping limits the resources discovered by Cisco DCNM-SAN client. You can either include a range of VSANs to be discovered or exclude a range of VSANs from being discovered.
a. b.

To limit the discovery to a range of VSANs, click Included VSAN List radio button. Specify the range of VSANs. To exclude a range of VSANs from being discovered, click Excluded VSAN List radio button. Specify the range of VSANs to be excluded.

Step 15

Click Discover. You see the Control Panel dialog box. You see the included and excluded VSANs list under the Fabric tab.

Note

You see a message in the dialog box when the server and client are running on the same workstation and there are unlicensed fabrics in the database. You also see a message when there are unmanaged fabrics (the state of the licenses is unknown).

Note

In the open tab, you see all the discovered fabrics displayed in the control panel. You need to click on the Open button to see all the discovered Ethernet switches.

Step 16

Check the check box(es) next to the fabric(s) you want to open in the Select column, or click Discover to add a new fabric.

Note

Only network administrators can continuously manage or unmanage fabrics. For more information, see the Selecting a Fabric to Manage Continuously section on page 3-6.

Step 17

Click Open to open the selected fabric(s).

Cisco DCNM Fundamentals Guide, Release 6.x

5-26

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Launching Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

If you have an incomplete view of your fabric, rediscover the fabric with a user that has no VSAN restriction. If the fabric includes a Cisco Nexus 5000 Series switch, then the Layer 2 node appears under the Switches > Interfaces > Ethernet tree, the VFC (FCoE) node appears under the Switches > Interfaces tree, and the FCoE node appears under the Switches tree in the Physical Attributes pane. For Cisco Nexus 5000 Series switches in the fabric, the tooltip for the switch shows the bind information of a virtual Fibre Channel interface to its corresponding Ethernet interface, such as vfc2(eth1/4).

You can launch Cisco DCNM-SAN Client from within a running instance of Cisco DCNM-SAN.

DETAILED STEPS
Step 1

Choose File > Open or click the Open Switch Fabric icon on the Cisco DCNM-SAN toolbar. You see the Control Panel dialog box. Check the check box(es) next to the fabric(s) you want to open in the Select column and click Open.

Step 2

Note

Changes made using Cisco DCNM-SAN are applied to the running configuration of the switches that you are managing. If you have made changes to the configuration or performed an operation (such as activating zones), Cisco DCNM-SAN prompts you to save your changes before you exit.

Launching Cisco DCNM-SAN Client Using Launch Pad

Starting from Cisco NX-OS Release 4.2(0), you can use Cisco DCNM-SAN launch pad to connect to any server by specifying the IP address of the server. With launch pad, you can connect to any Cisco DCNM-SAN Server version 3.3(0) and later. Launch pad establishes connection with the server using HTTP protocol.

DETAILED STEPS
Step 1

Open your browser and enter the IP address where you installed Cisco DCNM-SAN Server, or enter localhost if you installed Cisco DCNM-SAN Server on your local workstation. You see the Cisco DCNM-SAN Web Server Login dialog box. Enter your user name and password and click Login. You see the Cisco DCNM-SAN Web Client Summary page. Click the Download link in the upper right corner of the page. You see the Download page for Cisco DCNM-SAN and Device Manager. Click the link for Cisco DCNM-SAN.

Step 2

Step 3

Step 4

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-27

Chapter 5 Setting Cisco DCNM-SAN Preferences

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
You see the Cisco DCNM-SAN Server launch pad.
Step 5 Step 6

Enter the host name of the server or IP address in the Server URL drop-down list. Click Start.

Note

Launch pad retains the history of the server URLs used. You can choose one of the previously user Server URLs from the drop-down list.

Setting Cisco DCNM-SAN Preferences

To set your preferences for the behavior of the Cisco DCNM-SAN, choose File > Preferences from the Cisco DCNM-SAN menu bar. You see the Preferences dialog box with the following tabs for setting different components of the application:

General SNMP Map Show Device Name byDisplays the switches in the Fabric pane by IP address, DNS name, or logical name. The default setting for this value is Logical Name. Show WorldWideName (WWN) VendorDisplays the world wide name vendor name in any table or listing displayed by Cisco DCNM-SAN. Check the Prepend Name check box to display the name in front of the IP address of the switch. Check the Replacing Vendor Bytes check box to display the name instead of the IP address. The default is the Prepend Name option. Show End Device UsingDisplays end devices in the Fabric pane using alias or pWWN alias. The default setting for this value is Alias. Show Shortened iSCSI NamesDisplays the default setting for this value is OFF. Show Timestamps as Date/TimeDisplays timestamps in the date/time format. If this preference is not checked, timestamps are displayed as elapsed time. The default setting is enabled (checked). Telnet PathDisplays the path for the telnet.exe file on your system. The default is telnet.exe, but you need to browse for the correct location.

The default General preferences for Cisco DCNM-SAN are as follows:

Note

If you browse for a path or enter a path and you have a space in the pathname (for example, c:\program files\telnet.exe), then the path will not work. To get the path to work, you must manually place quotes around it (for example, "c:\program files\telnet.exe").

Use Secure Shell instead of TelnetSpecifies whether to use SSH or Telnet when using the CLI to communicate with the switch. If enabled, you must specify the path to your SSH application. The default setting is disabled. Confirm DeletionDisplays a confirmation pop-up window when you delete part of your configuration using Cisco DCNM-SAN. The default setting is enabled (checked). Export Tables with FormatSpecifies the type of file that is created when you export a table using Device Manager. The options are tab-delimited or XML. The default setting is Tab-Delimited.

Cisco DCNM Fundamentals Guide, Release 6.x

5-28

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Setting Cisco DCNM-SAN Preferences

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Show CFS WarningsShows warning messages if CFS is not enabled on all switches for a selected feature. Retry request 1 time(s) after 5 sec timeoutYou can set the retry value to 0-5, and the timeout value to 3-30. Trace SNMP packets in LogThe default setting for this value is ON. Enable Audible Alert when Event ReceivedThe default setting for this value is OFF. Display Unselected VSAN MembersDisplays the unselected VSAN members in the Fabric pane. The default setting for this value is ON. Display End DevicesDisplays the fabrics end devices in the Fabric pane. The default setting for this value is ON. Display End Device LabelsDisplays the fabrics end device labels in the Fabric pane. The default setting for this value is OFF. Expand LoopsDisplays the loops in the fabric as individual connections in the Fabric pane. The default setting for this value is OFF. Expand Multiple LinksDisplays multiple links in the Fabric pane as separate lines instead of one thick line. The default setting for this value is OFF. Open New Device Manager Each TimeOpens a new instance of Device Manager each time that you invoke it from a switch in your fabric. The default value is OFF, which means that only one instance of Device Manager is open at a time. Select Switch or Link from TableAllows you to select a switch or link in the Fabric pane by clicking the switch or link in a table in the Information pane. The default setting for this value is disabled (unchecked), which means clicking a switch or link in the table does not change the switch or link selection in the Fabric pane. Layout New Devices AutomaticallyAutomatically places new devices in the Fabric pane in an optimal configuration. The default setting for this value is OFF. In this mode, when you add a new device, you must manually reposition it if the initial position does not suit your needs. Use Quick Layout when Switch has 30 or more End DevicesDisplays the default setting for this value (30). You can enter any number in this field. Enter 0 to disable Quick Layout. Override Preferences for Non-default LayoutDisplays the default setting for this value (ON). Automatically Save LayoutIf this option is enabled, any changes in the layout are automatically saved. The default setting for this value is ON. Detach Overview WindowAllows you to easily center the Fabric pane on the area of the fabric that you want to see. (This feature is useful for large fabrics that cannot be displayed entirely within the Fabric pane.) Bring up the overview window by clicking the Show/Hide Overview Window button. It overlays the fabric window and remains there until you click the Show/Hide Overview Window button again. If you enable this preference, you can detach the overview window and move it to one side while you access the Fabric pane. The default setting for this value is disabled (unchecked).

The default SNMP preferences for Cisco DCNM-SAN are as follows:

The default Map preferences for Cisco DCNM-SAN are as follows:

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-29

Chapter 5 Network Fabric Discovery

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Network Fabric Discovery

Cisco DCNM-SAN collects information about the fabric topology through SNMP queries to the switches that are connected to Cisco DCNM-SAN. The switch replies after having discovered all devices connected to the fabric by using the information from its FSPF technology database and the Name Server database and collected using the Fabric Configuration Servers request/response mechanisms that are defined by the FC-GS-3/4 standard. When you start Cisco DCNM-SAN, you enter the IP address (or host name) of a seed switch for discovery. After you start Cisco DCNM-SAN and the discovery completes, Cisco DCNM-SAN presents you with a view of your network fabric, including all discovered switches, hosts, and storage devices.

Network LAN Discovery

Starting from NX-OS Release 4.2(0), you can discover Nexus and Catalyst Ethernet switches using Cisco Discovery Protocol (CDP). DataCenter 3(DC3) switches are displayed under Datacenter and LAN nodes. Cisco DCNM-SAN displays basic information about DC3 switches and its ISLs.

Viewing Ethernet Switches

DETAILED STEPS
Step 1 Step 2

Click the LAN node under Datacenter node. Click Switches tab in the Information pane. You can see the switch information.

Note

Datacenter is the parent node of SAN and LAN nodes. The SAN node remains in the tree as the parent for all the fabrics.

Removing a LAN
DETAILED STEPS
Step 1

Choose Server > Admin. You can see the switch information. Click to select the switch IP of the LAN you want to remove. Click Remove.

Step 2 Step 3

Cisco DCNM Fundamentals Guide, Release 6.x

5-30

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Modifying the Device Grouping

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Modifying the Device Grouping

Because not all devices are capable of responding to FC-GS-3 requests, different ports of a single server or storage subsystem may be displayed as individual end devices on the Cisco DCNM-SAN map.

DETAILED STEPS
Step 1

Expand End Devices and then choose Storage or Hosts in the Physical Attributes pane. You see the end devices displayed in the Information pane. Click one of the devices in the Fabric pane, or click the Enclosures tab of the Information pane, and then click the device name (in the Name field) that you want to include in the enclosure. Enter a name to identify the new enclosure in the Fabric pane map. Click once on the device name in the Name field. To select more than one name, press the Shift key and click each of the other names. Press Ctrl-C to copy the selected name(s). Press Ctrl-V to paste the device name into the Name field.

Step 2 Step 3 Step 4 Step 5 Step 6

Note

To remove devices from an enclosure, triple click the device name and press Delete. To remove an enclosure, repeat this step for each device in the enclosure.

Using Alias Names as Enclosures

DETAILED STEPS
Step 1

Expand End Devices and choose Hosts or Storage from the Physical Attributes pane. You see the list of devices in the Information pane. The NxPorts tab is the default. Right-click the enclosure names that you want to convert to alias names and choose Alias > Enclosure . The Ailas > Enclosures window appears . It contains a list of expressions. You can also add expressions to the list and modify expressions in the current list.

Step 2

Step 3

Click the Apply Changes icon to save the changes and then click Close.

Note

Cisco DCNM-SAN uses the regular expressions to convert multiple alias names into one enclosure. The alias names should be in the same expression pattern rule. You can create enclosure names from selected aliases using the regular expresssions list.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-31

Chapter 5 Controlling Administrator Access with Users and Roles

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Using Alias Names as Descriptions

DETAILED STEPS
Step 1 Step 2

Choose End Devices and from the Physical Attributes pane. Click the General tab. You see the list of devices in the Information pane. Select the device names that you want to populate the description with alias names and then click Alias > Enclosure button . You see the alias names are copied to corresponding rows in the description column.

Step 3

Note

Cisco DCNM-SAN does not parse or format the alias name while copying.

Controlling Administrator Access with Users and Roles

Cisco MDS 9000 Family switches support role-based management access whether using the CLI or Cisco Cisco DCNM-SAN. This lets you assign specific management privileges to particular roles and then assign one or more users to each role. The default-role contains the access permissions needed by a user to access the GUI (Cisco DCNM-SAN and Device Manager). These access permissions are automatically granted to all users in order for them to use the GUI. Cisco Cisco DCNM-SAN uses SNMPv3 to establish role-based management access. After completing the setup routine, a single role, user name, and password are established. The role assigned to this user allows the highest level of privileges, which includes creating users and roles. Use the Cisco Cisco DCNM-SAN to create roles and users and to assign passwords as required for secure management access in your network.

Using Cisco DCNM-SAN Wizards

Cisco DCNM-SAN Client provides the following wizards to facilitate common configuration tasks:

VSANCreates VSANs on multiple switches in the fabric and sets VSAN attributes including interop mode, load balancing, and FICON. Zone Edit ToolCreates zone sets, zones, and aliases. Adds members to zones and edits the zone database. IVR ZoneCreates IVR zone sets, zones, and aliases. Enables IVR NAT and auto-topology. Adds members to IVR zones, and edits the IVR zone database. FCoECreates virtual Fibre Channel (FC) interfaces and VLAN-VSAN mappings, and binds virtual FC interfaces to Ethernet interfaces or PortChannels.

Cisco DCNM Fundamentals Guide, Release 6.x

5-32

OL-25174-02

Chapter 5

Configuring Cisco DCNM-SAN Client Cisco DCNM-SAN Troubleshooting Tools

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

PortChannelCreates PortChannels from selected ISLs either manually or automatically. Sets PortChannel attributes such as channel ID and trunking mode. FCIPCreates FCIP links between Gigabit Ethernet ports. Enables Fibre Channel write acceleration and IP compression. DPVMEstablishes dynamic port VSAN membership, enables autolearning, and activates the DPVM database. Port SecurityPrevents unauthorized access to Cisco MDS switches and reports these intrusions to the administrator. iSCSICreates zones for iSCSI initiators and adds a VSAN to a target-allowed VSAN list. NPVReduces the number of Fibre Channel domain IDs in SANs. QoSSets QoS attributes for zones in the selected VSAN. IP ACLCreates ordered IP access control lists and distributes to selected switches in the fabric. License InstallFacilitates download and installation of licenses in selected switches in the fabric. Software InstallVerifies image compatibility and installs software images on selected switches in the fabric.

Cisco DCNM-SAN Troubleshooting Tools

Cisco DCNM-SAN has several troubleshooting tools available from the toolbar or Tools menu

Zone Merge AnalysisThe zone merge analysis tool (available from the Zone menu) enables you to determine if zones will merge successfully when two Cisco MDS switches are interconnected. If the interconnected switch ports allow VSANs with identical names or contain zones with identical names, then Cisco DCNM-SAN verifies that the zones contain identical members. The merge analysis tool can be run before attempting a merge or after fabrics are interconnected to determine zone merge failure causes. End-to-End ConnectivityCisco DCNM-SANs end-to-end connectivity analysis tool uses FC Ping to verify interconnections between Cisco MDS switches and end-device (HBAs and storage devices) in a particular VSAN. In addition to basic connectivity, Cisco DCNM-SAN can optionally verify the following:
Paths are redundant. Zones contain at least two members.

End devices are connected to a manageable switch (have a currently active in-band or out-of-band management path.)

Switch Health AnalysisYou can run an in-depth switch health analysis with Cisco DCNM-SAN. It verifies the status of all critical Cisco MDS switches, modules, ports, and Fibre Channel services. Over 40 conditions are checked. This tool provides a very fast, simple, and thorough way to assess Cisco MDS switch health. Fabric Configuration AnalysisCisco DCNM-SAN includes a fabric configuration analysis tool. It compares the configurations of all Cisco MDS switches in a fabric to a reference switch or a policy file. You can define what functions to check and what type of checks to perform. The analysis can look for mismatched values, and missing or extra values. If all configuration checking is performed for all functions, over 200 checks are performed for each Cisco MDS switch.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

5-33

Chapter 5 Integrating Cisco DCNM-SAN and Data Center Network Management Software

Configuring Cisco DCNM-SAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
After the analysis is run, the results are displayed with details about the issues that were discovered. You can automatically resolve configuration differences by selecting them and clicking the Resolve button. Cisco DCNM-SAN automatically changes the configuration to match the reference switch or policy file.

Integrating Cisco DCNM-SAN and Data Center Network Management Software

Cisco DCNM-SAN and Data Center Network Management (DCNM) software are the two major components in the Cisco next-generation data center environment. Cisco DCNM-SAN configures Cisco Nexus 5000 Series switches and Cisco MDS 9000 Series switches. DCNM software configures Cisco Nexus 5000 and Cisco Nexus 7000 Series switches. The Scope of the Cisco DCNM-SAN software is confined to SAN while the scope of the DCNM-LAN software is limited to the LAN network. In a typical data center environment, the mixture of SAN and LAN topology are becoming increasingly common. Since the two management software are not designed to work across their topology limits, users are not able to navigate to Cisco DCNM-SAN from DCNM-LAN software and vice versa. Integrating Cisco DCNM-SAN and DCNM-LAN provides a single platform to manage the networks in data center 3.0 and it provides seamless user experience under specific configuration. Starting from Cisco MDS NX-OS Release 4.2, the directory structure has changed to accommodate the integration of Cisco DCNM-SAN with Cisco Nexus 5000 Series products.

Launching a Switch from the Topology Map

DETAILED STEPS
Step 1

In the Cisco DCNM-SAN fabric pane, right-click the Nexus switch in the LAN map that you want to open with DCNM. You see the pop-up menu . In the pop up menu, click DCNM and select appropriate context.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x

5-34

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

Device Manager
This chapter contains descriptions and instructions for using the Cisco MDS 9000 Device Manager. This chapter contains the following sections:

Information About Device Manager, page 6-1 Device Manager Features, page 6-2 Using Device Manager Interface, page 6-2 Setting Device Manager Preferences, page 6-10

Information About Device Manager

Device Manager provides a graphic representation of a Cisco MDS 9000 Family switch chassis or Cisco Nexus 5000 Series switch chassis, including the installed switching modules, the supervisor modules, the status of each port within each module, the power supplies, and the fan assemblies. Device Manager provides a graphical representation of a Cisco MDS 9000 Family switch chassis or Cisco Nexus 5000 Series switch chassis, including the installed switching modules, the supervisor modules, the status of each port within each module, the power supplies, and the fan assemblies. The tables in the DCNM-SAN Information pane basically correspond to the dialog boxes that appear in Device Manager. However, while DCNM-SAN tables show values for one or more switches, a Device Manager dialog box shows values for a single switch. Also, Device Manager provides more detailed information for verifying or troubleshooting device-specific configuration than DCNM-SAN. Device Manager Release 4.2 and later provides enhanced security using multiple perspectives (simple and advanced) allowing role based-access to its features. The Device Manager perspective filters out menu items that are not relevant to the user. Users with server admin role, can only access a subset of the fabric related features. The server admin role will not be able to manage Device Manager users or connected clients. Device Manager Release 5.0 and later supports all the software features that are offered by Cisco NX-OS for managing Cisco MDS 9148 and 9124 Multilayer Fabric switches. Cisco MDS 9148 Multilayer Fabric Switch is a 48-port (1/2/4/8G) FC 1RU switch based on the Sabre ASIC andCisco MDS 9124 Multilayer Fabric switch is a 1/2/4/8G switch module for HP BladeServer based on the Sabre ASIC. Device Manager and DCNM-SAN allow you to discover, display, configure, monitor and service both these new switches. Device Manager also supports the following Cisco Nexus 2000 Series Fabric Extenders on a Cisco Nexus 5000 Series switch that runs Cisco NX-OS Release 5.0(1):

Cisco Nexus 2148T Fabric ExtenderIt has four 10-Gigabit Ethernet fabric interfaces for its uplink connection to the parent Cisco Nexus 5000 Series switch and eight 1-Gigabit Ethernet or 10-Gigabit Ethernet host interfaces for its downlink connection to servers or hosts.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

6-1

Chapter 6 Information About Device Manager

Device Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco Nexus 2232PP Fabric ExtenderIt has eight 10-Gigabit Ethernet fabric interfaces with SFP+ interface adapters for its uplink connection to the parent Cisco Nexus 5000 Series switch and 32 10-Gigabit Ethernet fabric interfaces with SFP+ interface adapters for its downlink connection to servers or hosts. Cisco Nexus 2248TP Fabric ExtenderIt has four 10-Gigabit Ethernet fabric interfaces with small form-factor pluggable (SFP+) interface adapters for its uplink connection to the parent Cisco Nexus 5000 Series switch and 48 1000BASE-T (1-Gigabit) Ethernet host interfaces for its downlink connection to servers or hosts.

Device Manager allows you to discover and display these Fabric Extenders. Cisco Device Manager and the Cisco DCNM-SAN client support provisioning and monitoring of the 48-port 8-Gbps Advanced Fibre Channel switching module (DS-X9248-256K9) and the 32-port 8-Gbps Advanced Fibre Channel switching module (DS-X9232-256K9).

Device Manager Features

Device Manager provides two views: Device View and Summary View. Use Summary View to monitor interfaces on the switch. Use Device View to perform switch-level configurations including the following:

Configure virtual Fibre Channel interfaces. Configure Fibre Channel over Ethernet (FCoE). Configure zones for multiple VSANs. Manage ports, PortChannels, and trunking. Manage SNMPv3 security access to switches. Manage CLI security access to the switch. Manage alarms, events, and notifications. Save and copy configuration files and software image. View hardware configuration. View chassis, module, port status, and statistics.

Using Device Manager Interface

This section describes the Device Manager interface.

Cisco DCNM Fundamentals Guide, Release 6.x

6-2

OL-25174-02

Chapter 6

Device Manager Information About Device Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 6-1 Device Manager, Device Tab

1 2 3 4

Menu bar Toolbar Tabs Legend

5 6 7

Status Supervisor modules Switching or services modules

Menu Bar
The menu bar at the top of the Device Manager main window provides options for managing and troubleshooting a single switch. The menu bar provides the following options:

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

6-3

Chapter 6 Information About Device Manager

Device Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

DeviceOpens an instance of Device Manager, sets management preferences, sets the page layout, opens a Telnet/SSH session with the current switch, exports a device image, and closes the Device Manager application. PhysicalAllows you to view and manage inventory, modules, temperature sensors, power supplies, fans, and the entire system. InterfaceAllows you to configure and manage PortChannels, as well as Fibre Channel, Ethernet, iSCSI, and FICON ports. Also provides diagnostic, management and monitoring capabilities, as well as SPAN and port tracking.

Note

The Interface > Port Channels menu option does not appear if the Cisco Nexus 5000 Series switch is in NPV mode and runs a Cisco NX-OS release prior to 4.2(1).

FCAllows you to configure and manage VSAN, domain, and name server characteristics. Also provides advanced configuration capabilities. FCoEAllows you to configure the FCoE parameters and map VSANs to VLANs on a Cisco Nexus 5000 Series switch.

Note

The FCoE menu option appears only if the Cisco Nexus 5000 Series switch runs Cisco NX-OS Release 4.0(1a) or later releases.

FICONAllows you to configure and manage FICON VSANs, configure RLIR ERL information, swap selected FICON ports, and view FICON port numbers. IPAllows you to configure and manage the following types of information: FCIP, iSCSI, iSNS, routes, VRRP, and CDP. SecurityAllows you to configure and manage FCSP, port security, iSCSI security, SNMP security, common roles, SSH, AAA, and IP ACLs. AdminAllows you to save, copy, edit, and erase the switch configuration, monitor events, manipulate Flash files, manage licenses, configure NTP, use CFS, and reset the switch. Also enables you to use the show tech support, show cores, and show image commands. LogsShows the various logs: message, hardware, events, and accounting. Also displays FICON link incidents, and allows you to configure the syslog setup. HelpDisplays online help topics for specific dialog boxes in the Information pane.

Toolbar Icons
The Device Manager toolbar provides quick access to many Device Manager features. Once the icon is selected, a dialog box may open that allows configuration of the feature. The toolbar provides the main Device and Summary View icons as shown in Table 6-1.

Cisco DCNM Fundamentals Guide, Release 6.x

6-4

OL-25174-02

Chapter 6

Device Manager Information About Device Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 6-1 Device Manager Main Toolbar

Icon Open Device

Description Opens the Device Manager view for another switch, with the option to open this view in a separate window. Communicates with the switch and displays the information in the Device Manager view. Opens a separate CLI command window to the switch. Opens a configuration dialog box for the selected component (line card or port). Opens a window that lists the latest system messages that occurred on the switch. Opens the VSAN dialog box that provides VSAN configuration for the switch. Saves the current running configuration to the startup configuration. Copies configuration file between server and switch. Toggles the FICON and interface port labels.

Refresh Display

Command-Line Interface Configure Selected

SysLog

VSANs

Save Configuration

Copy

Toggle FICON/Interface Port Labels Select VSAN

Filters the port display to show only those ports belonging to the selected VSAN. Accesses online help for Device Manager.

Help

Dialog Boxes
If a toolbar icon is selected, a dialog box may open that allows configuration of the selected feature. The dialog box may include table manipulation icons. See the Information Pane section on page 5-5 for descriptions of these icons.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

6-5

Chapter 6 Information About Device Manager

Device Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Tabs
Click the Device tab on the Device Manager main window to see a graphical representation of the switch chassis and components.

Note

The Device view also shows the switch chassis information of the Cisco Nexus 2000 Series Fabric Extenders (FEXs) that are connected to a Cisco Nexus 5000 Series switch that runs Cisco NX-OS Release 5.0(1). Click the Summary tab on the Device Manager main window to see a summary of active interfaces on a single switch, as well as Fibre Channel and IP neighbor devices. The Summary View also displays port speed, link utilization, and other traffic statistics. There are two buttons in the upper left corner of the Summary View tab used to monitor traffic. To monitor traffic for selected objects, click the Monitor Selected Interface Traffic Util% button. To display detailed statistics for selected objects, click the Monitor Selected Interface Traffic Details button. You can set the poll interval, the type or Rx/Tx display, and the thresholds.

Note

The Summary tab does not display the utilization statistics (Util%) of virtual Fibre Channel interfaces for Cisco Nexus 5000 Series switches that run Cisco NX-OS Release 4.2.

Legend
The legend at the bottom right of the Device Manager indicates port status, as follows: Colors

GreenThe port is up. BrownThe port is administratively down. RedThe port is down or has failed. AmberThe port has a minor fault condition. GrayThe port is unreachable. BlueThe port is out of service. XLink failure EISL TEMulti-VSAN ISL FHost/storage FLF loop I iSCSI SDSPAN destination CHChannel CUControl Unit NPProxy N-Port (NPV Mode)

Labels

Cisco DCNM Fundamentals Guide, Release 6.x

6-6

OL-25174-02

Chapter 6

Device Manager Information About Device Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

TNPTrunking NP_Port (NPV Mode) TFTrunking F_Port fvFC Present (Cisco Nexus 5000 Series switches only)

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

6-7

Chapter 6 Launching Device Manager

Device Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Supervisor and Switching Modules

In the Device View, you can right-click an object and get information on it, or configure it. If you right-click a module, the menu shows the module number and gives you the option to configure or reset the module. If you right-click a port, the menu shows the port number and gives you the option to configure, monitor, enable/disable, set beacon mode, or perform diagnostics on the port.

Tip

You can select multiple ports in Device Manager and apply options to all the selected ports at one time. Either select the ports by clicking the mouse and dragging it around them, or hold down the Control key and click each port. To enable or disable a port, right-click the port and click Enable or Disable from the pop-up menu. To enable or disable multiple ports, drag the mouse to select the ports and then right-click the selected ports. Then click Enable or Disable from the pop-up menu. To manage trunking on one or more ports, right-click the ports and click Configure. In the dialog box that appears, right-click the current value in the Trunk column and click nonTrunk, trunk, or auto from the pull-down list. To create PortChannels using Device Manager, click PortChannels from the Interface menu.

Note

To create a PortChannel, all the ports on both ends of the link must have the same port speed, trunking type, and administrative state.

Context Menus
Context menus are available in both Device Manager views by right-clicking a device or table. From Device View:

DeviceRight-click a system, module, or power supply to bring up a menu that gives you the option to configure or reset the device. Port Right-click a port to bring up a menu that shows you the number of the port you have clicked, and to give you the option to configure, monitor, enable, disable, set beacon mode, or perform diagnostics on the port. Table Right-click the table header to show a list of which columns to display in that table: Interface, Description, VSANs, Mode, Connected To, Speed (Gb), Rx, Tx, Errors, Discards, and Log. Click the Description field to bring up the appropriate configuration dialog box for the port type.

From Summary View:

Launching Device Manager

To launch Device Manager from your desktop, double-click the Device Manager icon and follow the instructions described in the Cisco DCNM Installation and Licensing Guide.

Cisco DCNM Fundamentals Guide, Release 6.x

6-8

OL-25174-02

Chapter 6

Device Manager Launching Device Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

You can choose one of the following three steps

a. b. c.

Right-click the switch you want to manage on the Fabric pane map and choose Device Manager from the menu that appears. Double-click a switch in the Fabric pane map. Select a switch in the Fabric pane map and choose Tools > Device Manager.

You see the Device Manager open dialog box

Step 2 Step 3 Step 4 Step 5

Enter the IP adress of the device. Enter the user name and password. Check the Proxy SNMP through FMS check box if you want Device Manager Client to use a TCP-based proxy server. Choose the Auth-Privacy option according to the privacy protocol you have configured on your switch:
a. b.

If you have not configured the switch with a privacy protocol, then choose Auth-Privacy option MD5 (no privacy). If you have configured the switch with your privacy protocol, choose your Auth-Privacy choice.

Step 6

Click Open to open the Device Manager.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

6-9

Chapter 6 Setting Device Manager Preferences

Device Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Setting Device Manager Preferences

To set your preferences for the behavior of the Device Manager application, choose Device > Preferences from the Device menu. You can set the following preferences:

Retry Requests x Time(s) After x sec TimeoutAllows you to set the retry request values. The default settings are 1 time after a 5-second timeout. Enable Status Polling Every x secsAllows you to set the status polling value. The default setting is enabled (checked) with a time of 40 seconds. Trace SNMP Packets in Message LogAllows you to set whether Device Manager traces SNMP packets and logs the trace. The default setting is disabled (unchecked). Register for Events After Open, Listen on Port 1163Allows you to register this switch so that events are logged once you open Device Manager. The default setting is enabled (checked). Show WorldWideName (WWN) VendorDisplays the world wide name vendor name in any table or listing displayed by Device Manager. If Prepend is checked, the name is displayed in front of the IP address of the switch. If Replace is checked, the name is displayed instead of the IP address. The default setting is enabled (checked) with the Prepend option. Show Timestamps as Date/TimeDisplays timestamps in the date/time format. If this preference is not checked, timestamps are displayed as elapsed time. The default setting is enabled (checked). Telnet PathSets the path for the telnet.exe file on your system. The default is telnet.exe, but you need to browse for the correct location.

Note

If you browse for a path or enter a path and you have a space in the pathname (for example, c:\program files\telnet.exe, then the path will not work. To get the path to work, manually place quotes around it (for example, "c:\program files\telnet.exe").

CLI Session Timeout x secs (0= disable)Specifies the timeout interval for a CLI session. Enter 0 to disable (no timeout value). The default setting is 30 seconds. Show Tooltips in Physical ViewDetermines whether tooltips are displayed in Physical (Device) View. The default setting is enabled (checked). Label Physical View Ports With:Specifies the type of label to assign to the ports when you are in Physical (Device) View. The options are FICON and Interface. The default setting is Interface. Export TableSpecifies the type of file that is created when you export a table using Device Manager. The options are Tab-Delimited or XML. The default setting is Tab-Delimited.

Cisco DCNM Fundamentals Guide, Release 6.x

6-10

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

Configuring Performance Manager

This chapter describes how DCNM-SAN is used to monitor and manage a network. This chapter includes the following topics:

Information About Performance Manager, page 7-1 Flow Statistics, page 7-3 Flow Setup Wizards, page 7-4

Information About Performance Manager

This section includes the following topics:

Data Interpolation, page 7-2 Data Collection, page 7-2 Using Performance Thresholds, page 7-2 Creating a Flow Using Performance Manager Flow Wizard, page 7-4

Performance Manager gathers network device statistics historically and provides this information graphically using a web browser. It presents recent statistics in detail and older statistics in summary. Performance Manager also integrates with external tools such as Cisco Traffic Analyzer. The Performance Manager has three operational stages:

DefinitionThe Flow Wizard sets up flows in the switches. CollectionThe Web Server Performance Collection screen collects information on desired fabrics. PresentationGenerates web pages to present the collected data through DCNM-SAN Web Server.

Performance Manager can collect statistics for ISLs, hosts, storage elements, and configured flows. Flows are defined based on a host-to-storage (or storage-to-host) link. Performance Manager gathers statistics from across the fabric based on collection configuration files. These files determine which SAN elements and SAN links Performance Manager gathers statistics for. Based on this configuration, Performance Manager communicates with the appropriate devices (switches, hosts, or storage elements) and collects the appropriate information at fixed five-minute intervals. Performance Manager uses a round-robin database to hold the statistical data collected from the fabric. This data is stored based on the configured parameters in the collection configuration file. At each polling interval, Performance Manager gathers the relevant statistics and stores them in the round-robin database. This database is a fixed size and will not grow beyond its preset limits.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

7-1

Chapter 7 Information About Performance Manager

Configuring Performance Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Performance Manager creates a series of archived data to hold summarized information present in the real-time round-robin database. This archived data is used to generate daily, weekly, monthly, and yearly consolidated reports. In this way, Performance Manager maintains significant historical data without the cost of an ever-increasing database size.

Note

You must restart Performance Manager if you change the user credentials on DCNM-SAN Server.

Data Interpolation
One of the unique features of Performance Manager is its ability to interpolate data when statistical polling results are missing or delayed. Other performance tools may store the missing data point as zero, but this can distort historical trending. Performance Manager interpolates the missing data point by comparing the data point that preceded the missing data and the data point stored in the polling interval after the missing data. This maintains the continuity of the performance information.

Data Collection
One years worth of data for two variables (Rx and Tx bytes) requires a round-robin database (rrd) file size of 76 K. If errors and discards are also collected, the rrd file size becomes 110 K. The default internal values are as follows:

600 samples of 5 minutes (2 days and 2 hours) 700 samples of 30 minutes (12.5 days) 775 samples of 2 hours (50 days) 300 samples of 1 day

A 1000-port SAN requires 110 MB for a years worth of historical data that includes errors and discards. If there were 20 switches in this SAN with equal distribution of fabric ports, about two to three SNMP packets per switch would be sent every 5 minutes for a total of about 100 request or response SNMP packets required to monitor the data. Because of their variable counter requests, flows are more difficult to predict storage space requirements for. But in general you can expect that, each extra flow adds another 76 KB.

Note

Performance Manager does not collect statistics on nonmanageable and non-MDS switches. Loop devices (FL/NL) are not collected.

Using Performance Thresholds

The Performance Manager Configuration Wizard allows you to set up two thresholds that will trigger events when the monitored traffic exceeds the percent utilization configured. These event triggers can be set as either Critical or Warning events that are reported on the DCNM-SAN web client Events browser page. Absolute value thresholds apply directly to the statistics gathered. These statistics, as a percent of the total link capacity, are compared to the percent utilization configured for the threshold type. If the statistics exceed either configured threshold, an event is shown on the DCNM-SAN web client Events tab.

Cisco DCNM Fundamentals Guide, Release 6.x

7-2

OL-25174-02

Chapter 7

Configuring Performance Manager Flow Statistics

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Baseline thresholds create a threshold that adapts to the typical traffic pattern for each link for the same time window each day, week, or every two weeks. Baseline thresholds are set as a percent of the average (110% to 500%), where 100% equals the calculated weighted average. Figure 7-1 shows an example of setting a baseline threshold for a weekly or daily option.
Figure 7-1 Baseline Threshold Example

Weekly (option) 8 weeks Mon 1/3 Mon 1/10 Mon 1/17

Two thresholds per throughput statistic - updated hourly

Mon 2/21

@2 PM Threshold setting Mon 2/28 @2 PM

Average

Percent over baseline (e.g. 130%)

Daily (option) 14 days Mon 2/14 Tues 2/15 Wed 2/16 Sun 2/27 @2 PM Threshold setting Mon 2/28 @2 PM
130886

Average

Percent over baseline (e.g. 130%)

The threshold is set for Monday at 2 p.m. The baseline threshold is set at 130% of the average for that statistic. The average is calculated from the statistics value that occurred at 2 p.m. on Monday, for every prior Monday (for the weekly option) or the statistics value that occurred at 2 p.m. on each day, for every prior day (for the daily option).

Flow Statistics
Flow statistics count the ingress traffic in the aggregated statistics table. You can collect two kinds of statistics:

Aggregated flow statistics to count the traffic for a VSAN. Flow statistics to count the traffic for a source and destination ID pair in a VSAN.

If you enable flow counters, you can enable a maximum of 1 K entries for aggregate flow and flow statistics. Be sure to assign an unused flow index to a module for each new flow. Flow indexes can be repeated across modules. The number space for flow index is shared between the aggregate flow statistics and the flow statistics.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

7-3

Chapter 7 Flow Setup Wizards

Configuring Performance Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Generation 1 modules allow a maximum of 1024 flow statements per module. Generation 2 modules allow a maximum of 2048-128 flow statements per module. Table 7-1 explains the Flow Type radio button that defines the type of traffic monitored.
Table 7-1 Performance Manager Flow Types

Flow type Host->Storage Storage->Host Both

Description Unidirectional flow, monitoring data from the host to the storage element Unidirectional flow, monitoring data from the storage element to the host Bidirectional flow, monitoring data to and from the host and storage elements

Flow Setup Wizards

The Performance Manager Flow and Performance Manager Setup wizards greatly simplify configuration. All you need to do is select the categories of statistics to capture and the wizards provide a list of flows and links to monitor. You can remove entries if desired, or just accept the provided list and start data collection. Statistics for host and storage links are not associated with a specific port on a switch, so you do not lose long term statistics if a connection is moved to a different port.

Creating a Flow Using Performance Manager Flow Wizard

DETAILED STEPS
Step 1

Choose Performance > Create Flows. You see the Define Traffic Flows dialog box. Click the drop-down menu in the VSAN field. Choose the list of VSANs provided by the flow configuration wizard. Click the drop-down menu in the Zone field. Choose the list of zones provided by the flow configuration wizard. Click Next to continue to the next window . Choose items in the Possible Flow Pairs area. The Review Traffic Flows window displays all VSAN flow pairs in the Exisitng Flows for Vsan area. Click Add to create the selected flow. Choose items in the Existing Flows for Vsan area. Click Remove to remove the selected flow. Click Finish to restart the Performance Manager collection. You see the Confirmation dialog box. To verify the newly created flow, choose Physical Attributes > End Devices > Flow Statistics. The newly created flows are displayed.

Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

Step 8 Step 9 Step 10 Step 11

Cisco DCNM Fundamentals Guide, Release 6.x

7-4

OL-25174-02

Chapter 7

Configuring Performance Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

Performance Manager Collection can be enabled for LAN devices and traffice counters are collected periodically.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

7-5

Chapter 7

Configuring Performance Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

7-6

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

Monitoring the Network

This chapter describes how the DCNM-SAN manages the network. In particular, SAN discovery and network monitoring are two of its key network management capabilities. This chapter contains the following sections:

Information About Network Monitoring, page 8-1 Device Discovery, page 8-2 Topology Mapping, page 8-3

Information About Network Monitoring

DCNM-SAN provides extensive SAN discovery, topology mapping, and information viewing capabilities. DCNM-SAN collects information on the fabric topology through SNMP queries to the switches connected to it. DCNM-SAN recreates a fabric topology, presents it in a customizable map, and provides inventory and configuration information in multiple viewing options such as fabric view, device view, summary view, and operation view. Once DCNM-SAN is invoked, a SAN discovery process begins. Using information polled from a seed Cisco MDS 9000 Family switch, including Name Server registrations, Fibre Channel Generic Services (FC-GS), Fabric Shortest Path First (FSPF), and SCSI-3, DCNM-SAN automatically discovers all devices and interconnects on one or more fabrics. All available switches, host bus adapters (HBAs), and storage devices are discovered. The Cisco MDS 9000 Family switches use Fabric-Device Management Interface (FMDI) to retrieve the HBA model, serial number and firmware version, and host operating-system type and version discovery without host agents. DCNM-SAN gathers this information through SNMP queries to each switch. The device information discovered includes device names, software revision levels, vendor, ISLs, PortChannels, and VSANs.

Monitoring Health and Events

DCNM-SAN works with the Cisco MDS 9000 Family switches to show the health and status of the fabric and switches. Information about the fabric and its components is gathered from multiple sources, including Online System Health Management, Call Home, system messages, and SNMP notifications. This information is then made available from multiple menus on DCNM-SAN or Device Manager.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

8-1

Chapter 8 Information About Network Monitoring

Monitoring the Network

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

DCNM-SAN Events Tab

The DCNM-SAN Events tab, available from the topology window, displays the events DCNM-SAN received from sources within the fabric. These sources include SNMP events, RMON events, system messages, and system health messages. The Events tab shows a table of events, including the event name, the source and time of the event, a severity level, and a description of the event. The table is sortable by any of these column headings.

Event Information in DCNM-SAN Web Server Reports

The DCNM-SAN web server client displays collections of information gathered by the Performance Manager. This information includes events sent to the DCNM-SAN Server from the fabric. To open these reports, choose Performance Manager > Reports. This opens the web client in a web browser and displays a summary of all fabrics monitored by the DCNM-SAN Server. Choose a fabric and then click the Events tab to see a summary or detailed report of the events that have occurred in the selected fabric. The summary view shows how many switches, ISLs, hosts, or storage elements are down on the fabric and how many warnings have been logged for that SAN entity. The detailed view shows a list of all events that have been logged from the fabric and can be filtered by severity, time period, or type.

Events in Device Manager

Device Manager displays the events when you choose Logs > Events. Device Manager can display the current list of events or an older list of events that has been stored on the DCNM-SAN host. The event table shows details on each event, including time, source, severity, and a brief description of the event.

SAN Discovery and Topology Mapping

DCNM-SAN provides extensive SAN discovery, topology mapping, and information viewing capabilities. DCNM-SAN collects information on the fabric topology through SNMP queries to the switches connected to it. DCNM-SAN recreates a fabric topology, presents it in a customizable map, and provides inventory and configuration information in multiple viewing options.

Device Discovery
Once DCNM-SAN is invoked, a SAN discovery process begins. Using information polled from a seed Cisco MDS 9000 Family switch, including Name Server registrations, Fibre Channel Generic Services (FC-GS), Fabric Shortest Path First (FSPF), and SCSI-3, DCNM-SAN automatically discovers all devices and interconnects on one or more fabrics. All available switches, host bus adapters (HBAs), and storage devices are discovered. The Cisco MDS 9000 Family switches use Fabric-Device Management Interface (FMDI) to retrieve HBA model, serial number and firmware version, and host operating-system type and version discovery without host agents. DCNM-SAN gathers this information through SNMP queries to each switch. The device information discovered includes device names, software revision levels, vendor, ISLs, PortChannels, and VSANs. For a VSAN change involving a third-party switch, DCNM-SAN will need a second discovery to show the correct topology due to the discovery dependency when there is any change in a mixed VSAN. The first discovery finds the third-party switch and the subsequent discovery will show the information on which VSAN it is going to join and can discover the end devices connected to it. You can wait for the subsequent discovery or trigger a manual discovery.

Cisco DCNM Fundamentals Guide, Release 6.x

8-2

OL-25174-02

Chapter 8

Monitoring the Network Information About Network Monitoring

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Topology Mapping
DCNM-SAN is built upon a topology representation of the fabric. DCNM-SAN provides an accurate view of multiple fabrics in a single window by displaying topology maps based on device discovery information. You can modify the topology map icon layout with an easy-to-use, drag-and-drop interface. The topology map visualizes device interconnections, highlights configuration information such as zones, VSANs, and ISLs exceeding utilization thresholds. The topology map also provides a visual context for launching command-line interface (CLI) sessions, configuring PortChannels, and opening device managers.

Using the Topology Map

The DCNM-SAN topology map can be customized to provide a view into the fabric that varies from showing all switches, end devices, and links, to showing only the core switches with single bold lines for any multiple links between switches. Use the icons along the left side of the topology map to control these views or right-click anywhere in the topology map to access the map controls. You can zoom in or out on the topology map to see an overview of the SAN or focus on an area of importance. You can also open an overview window that shows the entire fabric. From this window, you can right-click and draw a box around the area you want to view in the main topology map view. Another way to limit the scope of the topology display is to select a fabric or VSAN from the Logical Domains pane. The topology map displays only that fabric or VSAN. Moving the mouse pointer over a link or switch provides a simple summary of that SAN component, along with a status indication. Right-clicking on the component brings up a pop-up menu. You can view the component in detail or access configuration or test features for that component. Double-click a link to bring link status and configuration information to the information pane. Double-click a switch to bring up Device Manager for that switch.

Saving a Customized Topology Map Layout

Changes made to the topology map can be saved so that the customized view is available any time you open the DCNM-SAN Client for that fabric.

DETAILED STEPS
Step 1 Step 2 Step 3

Click File > Preferences to open the DCNM-SAN preferences dialog box. Click the Map tab and check the Automatically Save Layout check box to save any changes to the topology map . Click Apply, and then click OK to save this change.

Using Enclosures with DCNM-SAN Topology Maps

Because not all devices are capable of responding to FC-GS-3 requests, different ports of a single server or storage subsystem may be displayed as individual end devices on the topology map. See the Modifying the Device Grouping section on page 5-31 to group these ports into a single enclosure for DCNM-SAN.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

8-3

Chapter 8 Information About Network Monitoring

Monitoring the Network

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Clicking Alias->Enclosure displays hosts and storage elements in the Information pane. This is a shortcut to naming enclosures. To use this shortcut, highlight each row in the host or storage table that you want grouped in an enclosure then click Alias -> Enclosure. This automatically sets the enclosure names of each selected row with the first token of the alias.

Mapping Multiple Fabrics

To log into multiple fabrics, the same username and password must be used. The information for both fabrics is displayed, with no need to select a seed switch. To see details of a fabric, click the tab for that fabric at the bottom of the Fabric pane, or double-click the fabrics cloud icon. To continuously manage a fabric using DCNM-SAN, follow the instructions in the Managing a Cisco DCNM-SAN Server Fabric section on page 3-6.

Inventory Management
The Information pane in DCNM-SAN shows inventory, configuration, and status information for all switches, links, and hosts in the fabric. Inventory management includes vendor name and model, and software or firmware versions. Select a fabric or VSAN from the Logical Domains pane, and then select the Summary tab in the Information pane to get a count of the number of VSANS, switches, hosts, and storage elements in the fabric. See the Cisco DCNM-SAN Client Quick Tour: Admin Perspective section on page 5-7 for more information on the DCNM-SANDCNM-SAN user interface.

Using the Inventory Tab from DCNM-SAN Web Server

If you have configured DCNM-SAN Web Server, you can launch this application and access the Inventory tab to see a summary of the fabrics managed by the DCNM-SAN Server. The Inventory tab shows an inventory of the selected SAN, fabric, or switch. See Chapter 2, Cisco DCNM Web Client for more information on how to configure and use DCNM-SAN Web Server.

DETAILED STEPS
Step 1 Step 2

Point your browser at the DCNM-SAN Web Server. See the Adding a Security Exception section on page 2-5. Click the Events tab and then the Details tab to view the system messages. The columns in the events table are sortable. In addition, you can use the Filter button to limit the scope of messages within the table.

Viewing Logs from Device Manager

You can view system messages from Device Manager if Device Manager is running from the same workstation as the DCNM-SAN Server. Choose Logs > Events > current to view the system messages on Device Manager. The columns in the events table are sortable. In addition, you can use the Find button to locate text within the table.

Cisco DCNM Fundamentals Guide, Release 6.x

8-4

OL-25174-02

Chapter 8

Monitoring the Network

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
You can view switch-resident logs even if you have not set up your local syslog server or your local PC is not in the switch's syslog server list. Due to memory constraints, these logs will wrap when they reach a certain size. The switch syslog has two logs: an NVRAM log that holds a limited number of critical and greater messages and a nonpersistent log that contains notice or greater severity messages. Hardware messages are part of these logs.

Note

To view syslog local logs, you need to configure the IP address of the DCNM-SAN Server in the syslog host.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

8-5

Chapter 8

Monitoring the Network

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

8-6

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

Monitoring Performance
This chapter describes how to configure Performance Monitoring tools for Cisco DCNM-SAN and Device Manager. These tools provide real-time statistics as well as historical performance monitoring. This chapter contains the following sections:

Information About Performance Monitoring, page 9-1 Configuring Performance Manager, page 9-2 Configuring the Summary View in Device Manager, page 9-4 Configuring Per Port Monitoring using Device Manager, page 9-4 Displaying DCNM-SAN Real-Time ISL Statistics, page 9-5 Displaying Performance Manager Reports, page 9-6 Generating Performance Manager Reports, page 9-8 Exporting Data Collections, page 9-11 Analyzing SAN Health, page 9-12

Information About Performance Monitoring

Device Manager provides an easy tool for monitoring ports on the Cisco MDS 9000 Family switches. This tool gathers statistics at a configurable interval and displays the results in tables or charts. Real-time performance statistics are useful for dynamic troubleshooting and fault isolation within the fabric. Real-time statistics gather data on parts of the fabric in user-configurable intervals and display these results in DCNM-SAN and Device Manager. For a selected port, you can monitor any of a number of statistics including traffic in and out, errors, class 2 traffic, and FICON data.

Real-Time Performance Monitoring

Device Manager provides an easy tool for monitoring ports on the Cisco MDS 9000 Family switches. This tool gathers statistics at a configurable interval and displays the results in tables or charts. These statistics show the performance of the selected port in real-time and can be used for performance monitoring and troubleshooting. For a selected port, you can monitor any of a number of statistics including traffic in and out, errors, class 2 traffic, and FICON data. You can set the polling interval from ten seconds to one hour, and display the results based on a number of selectable options including absolute value, value per second, and minimum or maximum value per second.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

9-1

Chapter 9 Configuring Performance Manager

Monitoring Performance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Device Manager checking for oversubscription on the host-optimized four-port groups on relevant modules. Right-click the port group on a module and choose Check Oversubscription from the pop-up menu. Device manager provides two performance views: the Summary View tab and the configurable monitor option per port.

Historical Performance Monitoring

Performance Manager gathers network device statistics historically and provides this information using DCNM-SAN client and web browser. It presents recent statistics in detail and older statistics in summary. Performance Manager also integrates with external tools such as Cisco Traffic Analyzer. See the Information About Performance Manager section on page 7-1 for an overview of Performance Manager.

Configuring Performance Manager

This section includes the following topics:

Creating a Flow with Performance Manager, page 9-2 Creating a Collection with Performance Manager, page 9-2 Using Performance Thresholds, page 9-3

Creating a Flow with Performance Manager

With the Flow Configuration Wizard you can create host-to-storage, storage-to-host, or bidirectional flows. Once defined, you can add these flows to a collection configuration file to monitor the traffic between a host/storage element pair. The flows created become part of the collection options in the Performance Manager Configuration Wizard.

Creating a Collection with Performance Manager

The Performance Manager Configuration Wizard steps you through the process of creating collections using configuration files. Collections are defined for one or all VSANs in the fabric. Collections can include statistics from the SAN element types described in Table 9-1.
Table 9-1 Performance Manager Collection Types

Collection Type Description ISLs Host Storage Flows Collects link statistics for ISLs. Collects link statistics for SAN hosts. Collects link statistics for a storage elements. Collects flow statistics defined by the Flow Configuration Wizard.

Cisco DCNM Fundamentals Guide, Release 6.x

9-2

OL-25174-02

Chapter 9

Monitoring Performance Configuring Performance Manager

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Using Performance Thresholds

The Performance Manager Configuration Wizard allows you to set up two thresholds that trigger events when the monitored traffic exceeds the percent utilization configured. These event triggers can be set as either Critical or Warning events that are reported on the DCNM-SAN web client Events browser page. You must choose either absolute value thresholds or baseline thresholds that apply to all transmit or receive traffic defined in the collection. Click the Use absolute values radio button on the last screen of the Performance Manager Configuration Wizard to configure thresholds that apply directly to the statistics gathered. These statistics, as a percent of the total link capacity, are compared to the percent utilization configured for the threshold type. If the statistics exceed either configured threshold, an event is shown on the DCNM-SAN web client Events tab. As an example, the collection has absolute value thresholds set for 60% utilization (for warning) and 80% utilization (for critical). If Performance Manager detects that the traffic on a 1-Gigabit link in its collection exceeds 600 Mbps, a warning event is triggered. If the traffic exceeds 800 Mbps, a critical event is triggered. Baseline thresholds are defined for a configured time of day or week (1 day, 1 week, or 2 weeks). The baseline is created by calculating the average of the statistical results for the configured time each day, week, or every 2 weeks. Table 9-2 shows an example of the statistics used to create the baseline value for a collection defined at 4 pm on a Wednesday.
Table 9-2 Baseline Time Periods for a Collection Started on Wednesday at 4pm

Baseline Time Window 1 day 1 week 2 weeks

Statistics Used in Average Calculation Every prior day at 4 pm Every prior Wednesday at 4 pm Every other prior Wednesday at 4 pm

Baseline thresholds create a threshold that adapts to the typical traffic pattern for each link for the same time window each day, week, or every 2 weeks. Baseline thresholds are set as a percent of the average (110% to 500%), where 100% equals the calculated average. As an example, a collection is created at 4 pm on Wednesday, with baseline thresholds set for 1 week, at 150% of the average (warning) and 200% of the average (critical). Performance Manager recalculates the average for each link at 4 pm every Wednesday by taking the statistics gathered at that time each Wednesday since the collection started. Using this as the new average, Performance Manager compares each received traffic statistic against this value and sends a warning or critical event if the traffic on a link exceeds this average by 150% or 200% respectively. Table 9-3 shows two examples of 1-Gigabit links with different averages in our example collection and at what traffic measurements the Warning and Critical events are sent.
Table 9-3 Example of Events Generated for 1-Gigabit Links

Average 400 Mbps 200 Mbps

Warning Event Sent at 150% 600 Mbps 300 Mbps

Critical Event Sent at 200% 800 Mbps 400 Mbps

Set these thresholds on the last screen of the Collections Configuration Wizard by checking the Send events if traffic exceeds threshold check box.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

9-3

Chapter 9 Configuring the Summary View in Device Manager

Monitoring Performance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Configuring the Summary View in Device Manager

DETAILED STEPS
Step 1

Click the Summary tab on the main display. You see all of the active ports on the switch, as well as the configuration options available from the Summary view .
Figure 9-1 Device Manager Summary Tab

Step 2 Step 3

Choose a value from the Poll Interval drop-down list. Decide how you want your data to be interpreted by looking at the Show Rx/Tx drop-down menu. The table updates each polling interval to show an overview of the receive and transmit data for each active port on the switch. Select a value from the Show Rx/Tx drop-down list. If you select Util%, you need to also select values from the two Show Rx/Tx > %Util/sec drop-down lists. The first value is the warning level and the second value is the critical threshold level for event reporting. Note that you can also display percent utilization for a single port by selecting the port and clicking the Monitor Selected Interface Traffic Util % icon.

Step 4

Configuring Per Port Monitoring using Device Manager

The configurable monitor per port option gives statistics for in and out traffic on that port, errors, class 2 traffic and other data that can be graphed over a period of time to give a real-time view into the performance of the port.

Cisco DCNM Fundamentals Guide, Release 6.x

9-4

OL-25174-02

Chapter 9

Monitoring Performance Displaying DCNM-SAN Real-Time ISL Statistics

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1 Step 2

Click the Device tab. Right-click the port you are interested in and choose Monitor from the drop-down menu. You see the port real-time monitor dialog box. Select a value from the Interval drop-down list to determine how often data is updated in the table shown here. Click a statistical value in the table then click one of the graphing icons to display a running graph of that statistic over time. You see a graph window that contains options to change the graph type.

Step 3 Step 4

Tip

You can open multiple graphs for statistics on any of the active ports on the switch.

Displaying DCNM-SAN Real-Time ISL Statistics

This section includes the following topics:

Using the Performance Manager Configuration Wizard section on page 9-6 Viewing Performance Statics Using DCNM-SAN section on page 9-6

You can configure DCNM-SAN to gather ISL statistics in real time. These ISL statistics include receive and transmit utilization, bytes per second, as well as errors and discards per ISL.

DETAILED STEPS
Step 1

Choose Performance > ISLs in Real-Time. You see any ISL statistics in the Information pane .
Figure 9-2 ISL Performance in Real Time

Step 2 Step 3

Select a value from the Poll Interval drop-down list. Select two values from the Bandwidth utilization thresholds drop-down lists, one value for the minor threshold and one value for the major threshold. The table shown updates each polling interval to show the statistics for all configured ISLs in the fabric.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

9-5

Chapter 9 Displaying Performance Manager Reports

Monitoring Performance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 4

Select a row in the table to highlight that ISL in blue in the Topology map.

Using the Performance Manager Configuration Wizard

See the Creating, Editing, and Removing Performance Collections section on page 2-57.

Viewing Performance Statics Using DCNM-SAN

You can configure DCNM-SAN to gather historic and real time statistics of ISLs or End devices. These statistics include receive and transmit utilization, bytes per second, as well as errors and discards per ISL or end device.

DETAILED STEPS
Step 1

Right-click the ISL or end device in the Fabric pane. You see a context menu . Select Show Statics.

Step 2

Note

Show Statics menu will be enabled only if you add the fabric to the Performance Manager collection.

Displaying Performance Manager Reports

This section includes the following topics:

Displaying Performance Summary section on page 9-7 Displaying Performance Tables and Details Graphs section on page 9-7 Displaying Performance of Host-Optimized Port Groups section on page 9-7 Displaying Performance Manager Events section on page 9-7

You can view Performance Manager statistical data using preconfigured reports that are built on demand and displayed in a web browser. These reports provide summary information as well as detailed statistics that can be viewed for daily, weekly, monthly, or yearly results.

DETAILED STEPS
Step 1

Choose Performance > Reports to access Performance Manager reports from DCNM-SAN. This opens a web browser window showing the default DCNM-SAN web client event summary report. Click the Performance tab to view the Performance Manager reports.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x

9-6

OL-25174-02

Chapter 9

Monitoring Performance Displaying Performance Manager Reports

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Performance Manager begins reporting data ten minutes after the collection is started.

Note

DCNM-SAN Web Server must be running for reports to work.

Displaying Performance Summary

The Performance Summary page presents a dashboard display of the throughput and link utilization for hosts, ISLs, storage, and flows for the last 24-hour period. The summary provides a quick overview of the fabrics bandwidth consumption and highlights any hotspots. The report includes network throughput pie charts and link utilization pie charts. Use the navigation tree on the left to show summary reports for monitored fabrics or VSANs. The summary displays charts for all hosts, storage elements, ISLs, and flows. Each pie chart shows the percent of entities (links, hosts, storage, ISLs, or flows) that measure throughput or link utilization on each of six predefined ranges. Move the mouse over a pie chart section to see how many entities exhibit that range of statistics. Double-click any pie chart to bring up a table of statistics for those hosts, storage elements, ISLs, or flows.

Displaying Performance Tables and Details Graphs

Click Host, Storage, ISL, or Flow to view traffic over the past day for all hosts, storage, ISLs, or flows respectively. A table lists all of the selected entities, showing transmit and receive traffic and errors and discards, if appropriate. The table can be sorted by any column heading. The table can also be filtered by day, week, month, or year. Tables for each category of statistics display average and peak throughput values and provide hot-links to more detailed information. Clicking a link in any of the tables opens a details page that shows graphs for traffic by day, week, month, and year. If flows exist for that port, you can see which storage ports sent data. The details page also displays graphs for errors and discards if they are part of the statistics gathered and are not zero. If you double-click a graph on a Detail report, it will launch the Cisco Traffic Analyzer for Fibre Channel, if configured. The aliases associated with hosts, storage devices, and VSANs in the fabric are passed to the Cisco Traffic Analyzer to provide consistent, easy identification.

Displaying Performance of Host-Optimized Port Groups

You can monitor the performance of host-optimized port groups by selecting Performance > End Devices and selecting Port Groups from the Type drop-down list.

Displaying Performance Manager Events

Performance Manager events are viewed through DCNM-SAN Web Server. To view problems and events in DCNM-SAN Web Server, choose a fabric and then click the Events tab to see a summary or detailed report of the problems and events that have occurred in the selected fabric.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

9-7

Chapter 9 Generating Performance Manager Reports

Monitoring Performance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Generating Performance Manager Reports

Generating Top10 Reports in Performance Manager section on page 9-8 Generating Top10 Reports Using Scripts section on page 9-8

Generating Top10 Reports in Performance Manager

You can generate historical Top10 reports that can be saved for later review. These reports list the entities from the data collection, with the most active entities appearing first. This is a static, one-time only report that generates averages and graphs of the data collection as a snapshot at the time the report is generated. These Top10 reports differ from the other monitoring tables and graphs in Performance Manager in that the other data is continuously monitored and is sortable on any table column. The Top10 reports are a snapshot view at the time the report was generated and are static. These are one-time reports that generate averages and graphs of the data collection as a snapshot at the time the report is generated.

Tip

Name the reports with a timestamp so that you can easily find the report for a given day or week. These Top10 reports differ from the other monitoring tables and graphs in Performance Manager in that the other data is continuously monitored and is sortable on any table column. The Top10 reports are a snapshot view at the time the report was generated.

Note

Top10 reports require analyzing the existing data over an extended period of time and can take hours or more to generate on large fabrics. See the Creating a Custom Report Template section on page 2-40 for information on creating a Top10 report.

Generating Top10 Reports Using Scripts

You can generate Top10 reports manually by issuing the following commands:

On UNIX, run the script:

/<user_directory>/.cisco_mds9000/bin/pm.sh display pm/pm.xml <output_directory>

On Windows, run the script:

c:\Program Files\Cisco Systems\MDS 9000\bin\pm.bat display pm\pm.xml <output_directory>

On UNIX, you can automate the generation of the Top10 reports on your DCNM-SANDCNM-SAN Server host by adding the following cron entry to generate the reports once an hour:
0 * * * * /<user_directory>/.cisco_mds9000/bin/pm.sh display pm/pm.xml <output_directory>

If your crontab does not run automatically or Java complains about an exception similar to Example 9-1, you need to add -Djava.awt.headless=true to the JVMARGS command in /<user_directory>/.cisco_mds9000/bin/pm.sh.

Cisco DCNM Fundamentals Guide, Release 6.x

9-8

OL-25174-02

Chapter 9

Monitoring Performance Generating Performance Manager Reports

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Example 9-1 Example Java Exception

in thread main java.lang.InternalError Can't connect to X11 window server using '0.0' as the value of the DISPLAY variable.

Configuring Performance Manager for Use with Cisco Traffic Analyzer

Performance Manager works in conjunction with the Cisco Traffic Analyzer to allow you to monitor and manage the traffic on your fabric. Using Cisco Traffic Analyzer with Performance Manager requires the following components:

A configured Fibre Channel Switched Port Analyzer (SPAN) destination (SD) port to forward Fibre Channel traffic. A Port Analyzer Adapter 2 (PAA-2) to convert the Fibre Channel traffic to Ethernet traffic. Cisco Traffic Analyzer software to analyze the traffic from the PAA-2.

DETAILED STEPS
Step 1 Step 2

Set up the Cisco Traffic Analyzer according to the instructions in the Cisco MDS 9000 Family Port Analyzer Adapter 2 Installation and Configuration Note. Get the following three items of information:

The IP address of the management workstation on which you are running Performance Manager and Cisco Traffic Analyzer. The path to the directory where Cisco Traffic Analyzer is installed. The port that is used by Cisco Traffic Analyzer (the default is 3000). Choose Performance > Traffic Analyzer > Open. Enter the URL for the Cisco Traffic Analyzer, in the format:
http://<ip address>:<port number>

Step 3

Start the Cisco Traffic Analyzer.

a. b.

ip address is the address of the management workstation on which you have installed the Cisco Traffic Analyzer :port number is the port that is used by Cisco Traffic Analyzer (the default is :3000).
c. d. e.

Click OK. Choose Performance > Traffic Analyzer > Start. Enter the location of the Cisco Traffic Analyzer, in the format:
D:\<directory>\ntop.bat

D: is the drive letter for the disk drive where the Cisco Traffic Analyzer is installed. directory is the directory containing the ntop.bat file.
f. Step 4

Click OK.

Create the flows you want Performance Manager to monitor, using the Flow Configuration Wizard. See the Creating a Flow with Performance Manager section on page 9-2

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

9-9

Chapter 9 Generating Performance Manager Reports

Monitoring Performance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 5

Define the data collection you want Performance Manager to gather, using the Performance Manager Configuration Wizard. See the Creating a Collection with Performance Manager section on page 9-2.
a. b. c.

Choose the VSAN you want to collect information for or choose All VSANs. Check the types of items you want to collect information for (Hosts, ISLs, Storage Devices, and Flows). Enter the URL for the Cisco Traffic Analyzer in the format:
http://<ip address>/<directory>

where: ip address is the address of the management workstation on which you have installed the Cisco Traffic Analyzer, and directory is the path to the directory where the Cisco Traffic Analyzer is installed.
d. e. f.

Click Next. Review the data collection on this and the next section to make sure this is the data you want to collect. Click Finish to begin collecting data.

Note

Data is not collected for JBOD or for virtual ports. If you change the data collection configuration parameters during a data collection, you must stop and restart the collection process for your changes to take effect.

Step 6

Choose Performance > Reports to generate a report. Performance Manager Web Server must be running. You see Web Services; click Custom then select a report template.

Note

It takes at least five minutes to start collecting data for a report. Do not attempt to generate a report in Performance Manager during the first five minutes of collection.

Step 7

Click Cisco Traffic Analyzer at the top of the Host or Storage detail pages to view the Cisco Traffic Analyzer information, or choose Performance > Traffic Analyzer > Open . The Cisco Traffic Analyzer page will not open unless ntop has been started already.

Note

For information on capturing a SPAN session and starting a Cisco Traffic Analyzer session to view it, refer to the Cisco MDS 9000 Family Port Analyzer Adapter 2 Installation and Configuration Note.

Note

For information on viewing and interpreting your Performance Manager data, see the Creating a Flow with Performance Manager section on page 9-2. For information on viewing and interpreting your Cisco Traffic Analyzer data, refer to the Cisco MDS 9000 Family Port Analyzer Adapter 2 Installation and Configuration Note.

Cisco DCNM Fundamentals Guide, Release 6.x

9-10

OL-25174-02

Chapter 9

Monitoring Performance Exporting Data Collections

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
For performance drill-down, DCNM-SAN Server can launch the Cisco Traffic Analyzer in-context from the Performance Manager graphs. The aliases associated with hosts, storage devices, and VSANs are passed to the Cisco Traffic Analyzer to provide consistent, easy identification.

Exporting Data Collections

This section includes the following topics:

Exporting Data Collections to XML Files section on page 9-11 Exporting Data Collections in Readable Format section on page 9-11

Exporting Data Collections to XML Files

The RRD files used by Performance Manager can be exported to a freeware tool called rrdtool. The rrd files are located in pm/db on the DCNM-SAN Server. To export the collection to an XML file, enter the following command at the operating system command-line prompt:
/bin/pm.bat xport xxx yyy

In this command, xxx is the RRD file and yyy is the XML file that is generated. This XML file is in a format that rrdtool is capable of reading with the command:
rrdtool restore filename.xml filename.rrd

You can import an XML file with the command:

bin/pm.bat pm restore <xmlFile> <rrdFile>

This reads the XML export format that rrdtool is capable of writing with the command:
rrdtool xport filename.xml filename.rrd.

The pm xport and pm restore commands can be found on your DCNM-SAN Server at bin\PM.bat for Windows platforms or bin/PM.sh on UNIX platforms. For more information on the rrdtool, refer to the following website: http://www.rrdtool.org.

Exporting Data Collections in Readable Format

You can export the RRD files used by Performance Manager to a freeware tool called rrdtool and export the collection to an XML file. Cisco MDS SAN-OS Release 2.1(1a) introduces the inability to export data collections in comma-separated format (CSV). This format can be imported to various tools, including Microsoft Excel. You can export these readable data collections either from the DCNM-SAN Web Services menus or in batch mode from the command line on Windows or UNIX. Using DCNM-SAN Web Services, you can export one file. Using batch mode, you can export all collections in the pm.xml file.

Note

DCNM-SAN Web Server must be running for this to work. You can export data collections to Microsoft Excel using DCNM-SAN Web Server.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

9-11

Chapter 9 Analyzing SAN Health

Monitoring Performance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

Click the Performance tab on the main page. You see the overview table. Click the Flows sub-tab. Right-click the name of the entity you want to export and select Export to Microsoft Excel . You see the Excel chart for that entity in a pop-up window.

Step 2 Step 3

You can export data collections using command-line batch mode.

DETAILED STEPS
Step 1 Step 2 Step 3

Go to the installation directory on your workstation and then go to the bin directory. On Windows, enter .\pm.bat export C:\Program Files\Cisco Systems\MDS 9000\pm\pm.xml <export directory>. This creates the csv file (export.csv) in the export directory on your workstation. On UNIX, enter ./pm.sh export /usr/local/cisco_mds9000/pm/pm.xml <export directory>. This creates the csv file (export.csv) in the export directory on your workstation.

When you open this exported file in Microsoft Excel, the following information displays:

Title of the entity you exported and the address of the switch the information came from. The maximum speed seen on the link to or from this entity. The VSAN ID and maximum speed. The timestamp, followed by the receive and transmit data rates in bytes per second.

Analyzing SAN Health

The SAN Health Advisor tool is a utility that used to monitor the performance and collect the statistics. You can perform the following tasks with this tool:

Run Performance Monitor to collect I/O statistics Collect fabric inventory (switches and other devices) Create a graphical layout of fabric topology Create reports of error conditions and statistical data

You can install this tool at any SAN environment to collect I/O statistics for the specified time (usually 24 hours), generate health reports and automatically send reports to the designated system administrator for review at regular intervals. When you start SAN Health Advisor tool, it runs in wizard mode, and prompts for inputs such as seed switch credentials, IP address of the server to which the data to be sent and all the necessary information for the software setup. As soon as the fabric is discovered, the tool starts capturing performance data, I/O statistics and error conditions.

Cisco DCNM Fundamentals Guide, Release 6.x

9-12

OL-25174-02

Chapter 9

Monitoring Performance Analyzing SAN Health

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The reports generated from the collection is stored in the $INSTALLDIR/dcm/fm/reports directory. These reports are automatically sent to the designated SAN administrator for review. In a situation where the tool fails to collect the data, it generates a report with an error message or exception. After sending the reports the tool automatically uninstalls itself and terminates all the processes that it established on the host machine. The report that SAN Health Advisor tool generates will have the following details:

Events System messages Analysis of connectivity Zone discrepancy System configuration Interface status Domain information Security settings

Installing the SAN Health Advisor Tool

SAN Health Advisor tool can be installed and run on Windows, UNIX, and Solaris platforms. Install the package that contains the .jar file with JRE version 6.0.

Note

The SAN Health tool is not installed by default when you install DCNM-SAN software.

DETAILED STEPS
Step 1

Double-click the San Health Advisor tool installer. You see the San Health Advisor tool Installer window. Select an installation folder on your workstation for SAN Health Advisor. On Windows, the default location is C:\Program Files\Cisco Systems\. Click Install to start the installation. You see the installation progressing. You see the Fabric Options dialog box In the Seed Switch text box, enter the IP address of the seed switch. Enter the user name and password for the switch. Select the authentication privacy option from the Auth-Privacy drop-down list box. Click the Performance Collection check box to enable the process to run for 24 hours. Click Collect to start gathering performance information. You see the collecting dialog box. If you want to stop gathering information in the middle of the process, click Cancel. You see the message indicating performance collection is complete.

Step 2

Step 3

Step 4 Step 5 Step 6 Step 7 Step 8

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

9-13

Chapter 9 Analyzing SAN Health

Monitoring Performance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 9

Click Uninstall to remove the SAN Health Advisor software.

Cisco DCNM Fundamentals Guide, Release 6.x

9-14

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

10

Software Images
This chapter describes how to install and upgrade Cisco MDS software images. It includes the following sections:

Information About Software Images, page 10-1 Prerequisites for Installing Software Images, page 10-4 Using the Software Install Wizard, page 10-8 Performing Nondisruptive Upgrades on Fabric and Modular Switches, page 10-11 Maintaining Supervisor Modules, page 10-12 Installing Generation 2 Modules in Generation 1 Chassis, page 10-14 Replacing Modules, page 10-14

Information About Software Images

This section contains the following topics:

Software Upgrade Methods, page 10-2 Determining Software Compatibility, page 10-2 Automated Upgrades, page 10-3 Benefits of Using the Software Install Wizard, page 10-3 Recognizing Failure Cases, page 10-4

Each switch is shipped with a Cisco MDS NX-OS or SAN-OS operating system for Cisco MDS 9000 Family switches. The Cisco MDS NX-OS consists of two imagesthe kickstart image and the system image. To upgrade the switch to a new image, you must specify the variables that direct the switch to the images.

To select the kickstart image, use the KICKSTART variable. To select the system image, use the SYSTEM variable.

The images and variables are important factors in any install procedure. You must specify the variable and the image to upgrade your switch. Both images are not always required for each install.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

10-1

Chapter 10 Information About Software Images

Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

Unless explicitly stated, the software install procedures in this chapter apply to any switch in the Cisco MDS 9000 Family.

Software Upgrade Methods

You can upgrade software without any disruptions using the Cisco MDS NX-OS software designed for mission-critical high availability environments. To realize the benefits of nondisruptive upgrades on the Cisco MDS 9500 Directors, we highly recommend that you install dual supervisor modules. You can upgrade any switch in the Cisco MDS 9000 Family using one of the following methods:

AutomaticYou can use the DCNM-SAN Software Install Wizard for Cisco MDS NX-OS switches as described in the Using the Software Install Wizard section on page 10-8. ManualFor information on manual upgrades, see the Cisco MDS 9020 Switch Configuration Guide and Command Reference.

In some cases, regardless of which process you use, the software upgrades may be disruptive. These exception scenarios can occur under the following conditions:

A single supervisor module system with kickstart or system image changes. A dual supervisor module system with incompatible system software images.

Note

For high availability, you need to connect the ethernet port for both active and standby supervisors to the same network or virtual LAN. The active supervisor owns the one IP address used by these Ethernet connections. On a switchover, the newly activated supervisor takes over this IP address.

Determining Software Compatibility

If the running image and the image you want to install are incompatible, the software reports the incompatibility. In some cases, you may decide to proceed with this installation. If the active and the standby supervisor modules run different versions of the image, both images may be HA compatible in some cases and incompatible in others. Compatibility is established based on the image and configuration:

Image incompatibilityThe running image and the image to be installed are not compatible. Configuration incompatibilityThere is a possible incompatibility if certain features in the running image are turned off as they are not supported in the image to be installed. The image to be installed is considered incompatible with the running image if one of the following statements is true:
An incompatible feature is enabled in the image to be installed and it is not available in the

running image and may cause the switch to move into an inconsistent state. In this case, the incompatibility is strict.
An incompatible feature is enabled in the image to be installed and it is not available in the

running image and does not cause the switch to move into an inconsistent state. In this case, the incompatibility is loose.

Cisco DCNM Fundamentals Guide, Release 6.x

10-2

OL-25174-02

Chapter 10

Software Images Information About Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Tip

The Software Install Wizard compares and presents the results of the compatibility before proceeding with the installation. You can exit if you do not want to proceed with these changes.

Automated Upgrades
The Software Install Wizard upgrades all modules in any Cisco MDS 9000 Family switch. Figure 10-1 provides an overview of the switch status before and after using Software Install Wizard.
Figure 10-1 The Effect of the Software Install Wizard

Cisco MDS 9500 Series switch Switch before issuing the install all comand Slot 5 install all 2.1(2b) to 3.0(1) Active supervisor module 2.1(2b) Slot 6 Standby supervisor module 2.1(2b) Switch after the install all comand completes Slot 5 Standby supervisor module 3.0(1) Slot 6 Active supervisor module 3.0(1)
154732

The Software Install Wizard automatically verifies if the standby supervisor module is functioning (if present). If it is not functioning, it reloads that module and uses the force download option to force it to function.

Benefits of Using the Software Install Wizard

The Software Install Wizard provides the following benefits:

You can upgrade the entire switch using just one procedure command. You can receive descriptive information on the intended changes to your system before you continue with the installation. You can upgrade the entire switch using the least disruptive procedure. You can see the progress of this command on the console, Telnet, and SSH screens:
After a switchover process, you can see the progress from both the supervisor modules. Before a switchover process, you can only see the progress from the active supervisor module.

The Software Install Wizard automatically checks the image integrity. This includes the running kickstart and system images. The Software Install Wizard performs a platform validity check to verify that a wrong image is not used. For example, to check if an MDS 9500 Series image is used inadvertently to upgrade an MDS 9200 Series switch. After issuing the installation, if any step in the sequence fails, the wizard completes the step in progress and ends.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

10-3

Chapter 10 Prerequisites for Installing Software Images

Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
For example, if a switching module fails to be updated for any reason (for example, due to an unstable fabric state), then the command sequence disruptively updates that module and ends. In such cases, you can verify the problem on the affected switching module and upgrade the other switching modules.

Recognizing Failure Cases

The following situations cause the installation to end:

If the standby supervisor module bootflash: file system does not have sufficient space to accept the updated image. If the specified system and kickstart images are not compatible. If the fabric or switch is configured while the upgrade is in progress. If a module is removed while the upgrade is in progress. If the switch has any power disruption while the upgrade is in progress. If the entire path for the remote location is not specified accurately. If images are incompatible after an upgrade. For example, a switching module image may be incompatible with the system image, or a kickstart image may be incompatible with a system image. This is also identified by the Software Install Wizard compatibility check.

Caution

If the installation is ended, be sure to verify the state of the switch at every stage and reissue the command after 10 seconds. If you reissue the installation within the 10-second span, it is rejected with an error message indicating that an installation is currently in progress.

Tip

All configurations are disallowed while the installation is in progress. However, configurations coming through the CFS applications are allowed and may affect the upgrade procedure.

Prerequisites for Installing Software Images

The software image install procedure is dependent on the following factors:

Software imagesThe kickstart and system image files reside in directories or folders that can be accessed from the Cisco MDS 9000 Family switch prompt. Image versionEach image file has a version. Flash disks on the switchThe bootflash: resides on the supervisor module and the CompactFlash disk is inserted into the slot0: device. Supervisor modulesThere are single or dual supervisor modules.

Cisco DCNM Fundamentals Guide, Release 6.x

10-4

OL-25174-02

Chapter 10

Software Images Prerequisites for Installing Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Selecting the Correct Software Images for Cisco MDS 9100 Series Switches
The Supervisor-1 and Supervisor-2 modules supported by Cisco MDS 9100 Series switches require different system and kickstart images. You can determine which images to use on your switch by the naming conventions shown in Table 10-1 and Table 10-2.
Table 10-1 Supervisor Module Software Image Naming Conventions for MDS 9100 Series

Cisco MDS 9100 Series Switch Type 9124, 9124e, 9134, Cisco Fabric Switch for HP c-Class BladeSystem, Cisco Fabric Switch for IBM BladeCenter

Supervisor Module Type Supervisor-2 module

Naming Convention Filename begins with m9100-s2ek9

Table 10-2

Software Image Naming Conventions for MDS 9100 Series

Cisco MDS 9100 Series Switch Type Cisco MDS 9148 Multilayer Fabric Switch Cisco MDS 9124 Multilayer Fabric Switch

Supervisor Module Type Supervisor-2 module Supervisor-2 module

Naming Convention Filename begins with m9100-s3ek9. Filename begins with m9100-s3ek9.

Selecting the Correct Software Images for Cisco MDS 9200 Series Switches
The Supervisor-1 and Supervisor-2 modules supported by Cisco MDS 9200 Series switches require different system and kickstart images. You can determine which images to use on your switch by the naming conventions shown in Table 10-3.
Table 10-3 Supervisor Module Software Image Naming Conventions for MDS 9200 Series

Cisco MDS 9200 Series Switch Type 9222i 9216, 9216A or 9216i

Supervisor Module Type Supervisor-2 module Supervisor-1 module

Naming Convention Filename begins with m9200-s2ek9 Filename begins with m9200-s1ek9

Selecting the Correct Software Images for Cisco MDS 9500 Family Switches
The Supervisor-1 and Supervisor-2 modules supported by Cisco MDS 9500 Family switches require different system and kickstart images. You can determine which images to use on your switch by the naming conventions shown in Table 10-4.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

10-5

Chapter 10 Prerequisites for Installing Software Images

Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 10-4 Supervisor Module Software Image Naming Conventions for MDS 9500 Series

Cisco MDS 9500 Series Switch Type 9513 9506 or 9509

Supervisor Module Type Supervisor-2 module Supervisor-2 module

Naming Convention Filename begins with m9500-sf2ek9 Filename begins with m9500-sf2ek9

Essential Upgrade Prerequisites

Note

During a software upgrade to Cisco SAN-OS 3.1(3), the CompactFlash CRC Checksum test runs automatically in the background. All modules that are online are tested and the installation stops if any modules are running with a faulty CompactFlash. When this occurs, the switch can not be upgraded until the situation is corrected. A system message displays the module information and indicates that you must issue the system health cf-crc-check module CLI command to troubleshoot. For descriptions of new commands supported by the CompactFlash checksum feature, refer to the Cisco MDS 9000 Family Command Reference. Before attempting to migrate to any software image version, follow these guidelines:

Customer Service Before performing any software upgrade, contact your respective customer service representative to review your software upgrade requirements and to provide recommendations based on your current operating environment.

Note

If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support at this URL: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml Scheduling Schedule the upgrade when the fabric is stable and steady. Ensure that everyone who has access to the switch or the network is not configuring the switch or the network during this time. All configurations are disallowed at this time.

Space Verify that sufficient space is available in the location where you are copying the images. This location includes the active and standby supervisor module bootflash: (internal to the switch).
Standby supervisor module bootflash: file system. Internal bootflash: offers approximately 200 MB of user space.

Hardware Avoid power interruption during any install procedure. These kinds of problems can corrupt the software image.

Connectivity (to retrieve images from remote servers)

Configure the IPv4 address or IPv6 address for the 10/100/1000 BASE-T Ethernet port

connection (interface mgmt0).

Cisco DCNM Fundamentals Guide, Release 6.x

10-6

OL-25174-02

Chapter 10

Software Images Prerequisites for Installing Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

1000 BASE-T Ethernet is only available on Supervisor-2 modules.

Ensure the switch has a route to the remote server. The switch and the remote server must be in

the same subnetwork if you do not have a router to route traffic between subnets.

Images
Ensure that the specified system and kickstart images are compatible with each other. If the kickstart image is not specified, the switch uses the current running kickstart image. If you specify a different system image, ensure that it is compatible with the running kickstart

image.
Retrieve images in one of two ways:

Local fileImages are locally available on the switch. Network fileImages are in a remote location and the user specifies the destination using the remote server parameters and the file name to be used locally.

Terminology Table 10-5 summarizes terms used in this chapter with specific reference to the install and upgrade process.

Table 10-5

Terms Specific to This Chapter

Term bootable impact install-type reset sw-reset rolling copy-only

Definition The modules ability to boot or not boot based on image compatibility. The type of software upgrade mechanismdisruptive or nondisruptive. Resets the module. Resets the module immediately after switchover. Upgrades each module in sequence. Updates the software for BIOS, loader, or bootrom.

Tools
Verify connectivity to the remote server by clicking Verify Remote Server in the Software

Install Wizard in DCNM-SAN.

Ensure that the required space is available for the image files to be copied by using Software

Install Wizard to check free disk space.

We recommend the Software Install Wizard in DCNM-SAN to upgrade your software. This

wizard upgrades all modules in any Cisco MDS 9000 Family switch (see the Benefits of Using the Software Install Wizard section on page 10-3).
Run only one installation on a switch at any time. Do not issue another command while running the installation. Do the installation on the active supervisor module, not the standby supervisor module.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

10-7

Chapter 10 Default Settings

Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

Prior to Cisco SAN-OS Release 3.0, to preserve the FC IDs in your configuration, verify that the persistent FC ID feature is enabled before rebooting. This feature is enabled by default. In earlier releases, the default is disabled.

Note

The Software Install Wizard supports installation and upgrade for Cisco MDS 9020 Fabric Switch or Cisco FabricWare. For successful installation and upgrade, specify the TFTP server address that the Cisco MDS 9020 Fabric Switch should use.

Note

Before you use this wizard, be sure the standby supervisor management port is connected.

Default Settings
Table 10-6 lists the default image settings for all Cisco MDS 9000 Family switches.
Table 10-6 Default Image Settings

Parameters Kickstart image System image

Default No image is specified. No image is specified.

Using the Software Install Wizard

You can use the Software Install Wizard to install Cisco NX-OS images on supported switches.

DETAILED STEPS
Step 1

Click the Software Install Wizard icon in the toolbar. You see the Select Switches dialog box with all switches selected by default. Deselect the check box for the switch(es) for which you do not want to install images on. You must have at least one switch selected to proceed . Click Next when finished. (Optional) Check the Skip Image Download check box and click Next to use images that are already downloaded (the file is already on the bootflash). Proceed to Step 11. You see the Specify Software Image(s) by Model Dialog Box. Click the Use Saved Settings check box to save the settings you specify. These settings will be saved for future use when you click Next.

Step 2 Step 3 Step 4

Step 5

Cisco DCNM Fundamentals Guide, Release 6.x

10-8

OL-25174-02

Chapter 10

Software Images Using the Software Install Wizard

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 6

Click the radio button for either:

a. b.

Local FM TFTP to transfer files from local computer. Remote to transfer files from a remote computer.

Step 7 Step 8 Step 9 Step 10

If you select Local FM TFTP, proceed to Step 10. If you select Remote, click one of the Copy Files Via radio buttons transfers files (SFTP, SCP, FTP). Enter the server name, user name and password. Enter the version and the image path and then click Apply.

Note

You can manually provide the file name, if you had choosen Local FM TFTP in step 6. To do that you may double-click the table, and choose the file form the Open dialog box or manually type the file name in the cell under system.

When you enter the version string and image path, DCNM-SAN tries retrieves the default file name and the calculate the flash space required to accommodate the image file. Version string should be the current version of the version to be installed. Image path is the path to locate the software image as shown in the following example:
Image URI: /tftpboot/rel/qa/5_0_0_201/gdb/m9500-sf2ek9-mzg.5.0.0.201.bin.S2 Path /tftpboot/rel/qa/5_0_0_201/gdb Version String 5.0.0.201.S2

Step 11 Step 12

Click the row under the System, Kickstart or SSI columns to enter image URIs. You must specify at least one image for each switch to proceed. Click Verify Remote Server and Path. DCNM-SAN will validate the file path and server credentials. You see the output Click OK and then click Next in the Specify Software Images by Model dialog box. You see the Check Flash Free Space dialog box. This dialog box shows the active (and standby, if applicable) bootflash space on each switch, and shows the status (whether there is enough space for the new images). If any switch has insufficient space, you cannot proceed. Deselect the switch without enough bootflash by going back to the first screen and unchecking the check box for that switch.

Step 13

Step 14

Click Next. You see the Start Install dialog box.

Note Step 15

There is no limit on the number of switches you can upgrade.

Click one of the the radio buttons:

a. b.

Serialized to upgrade one switch at a time. Parallel to simultaneously upgrade multiple switches.

Step 16 Step 17

(Optional) Check the Version Check Only check box to complete the version check first and then prompt for your input to continue with installation. (Optional) Click Finish to start installation. You see the Version Check Results dialog box .

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

10-9

Chapter 10 Using the Software Install Wizard

Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 18

(Optional) Check the Install without Version check Prompting check box to continue with the installation.

Note

The version check provides information about the impact of the upgrade for each module on the switch. It also shows any incompatibilities that might result. You see a final dialog box at this stage, prompting you to confirm that this check should be performed. We recommend that you do not ignore the version check results.

Caution

If Install without Version check Prompting is checked, the upgrade will proceed even if the current switch version is newer than the version you are installing.

Step 19 Step 20

Click OK to close the wizard. Click Continue to install to start the installation. You see the Download and Install Status dialog box.

Note

On hosts where the TFTP server cannot be started, a warning is displayed. The TFTP server may not start because an existing TFTP server is running or because access to the TFTP port 69 has been denied for security reasons (the default setting on Linux). In these cases, you cannot transfer files from the local host to the switch.

Note

Before exiting the session, be sure the upgrade process is complete. The wizard will display a status as it goes along. Check the lower left-hand corner of the wizard for the status message Upgrade Finished. First, the wizard displays the message Success followed a few seconds later by InProgress Polling. Then the wizard displays a second message Success before displaying the final Upgrade Finished.

Upgrading Services Modules

Any Fibre Channel switching module supports nondisruptive upgrades. The 14/2-port Multiprotocol Services (MPS-14/2)) module supports nondisruptive upgrades for the Fibre Channel ports. Any software upgrade for the two Gigabit Ethernet ports in this module is disruptive. Any software upgrade for the Caching Services Module (CSM) and the IP Storage (IPS) services modules is disruptive. CSMs and IPS modules use a rolling upgrade install mechanism to guarantee a stable state for each module in the switch:

Each IPS module in a switch requires a 5-minute delay before the next IPS module is upgraded. Each CSM module requires a 30-minute delay before the next CSM module is upgraded. See the Cisco MDS 9000 Family SAN Volume Controller Configuration Guide for more information on CSMs.

Cisco DCNM Fundamentals Guide, Release 6.x

10-10

OL-25174-02

Chapter 10

Software Images Performing Nondisruptive Upgrades on Fabric and Modular Switches

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Performing Nondisruptive Upgrades on Fabric and Modular Switches

This section describes how to perform nondisruptive upgrades on the following Cisco Fabric Switches:

Cisco MDS 9124 Multilayer Fabric Switch Cisco MDS 9134 Multilayer Fabric Switch Cisco MDS 9222i Multiservice Modular Switch Cisco Fabric Switch for HP c-Class BladeSystem Cisco Fabric Switch for IBM BladeCenter Preparing for a Nondisruptive Upgrade on Fabric and Modular Switches, page 10-11 Performing a Nondisruptive Upgrade on a Fabric Switch, page 10-12

This section includes the following topics:

Preparing for a Nondisruptive Upgrade on Fabric and Modular Switches

You can upgrade software on the following without any disruptions using the Software Install Wizard for the system software images.

Cisco MDS 9124 Multilayer Fabric Switch Cisco MDS 9134 Multilayer Fabric Switch Cisco MDS 9222i Multiservice Modular Switch Cisco Fabric Switch for HP c-Class BladeSystem Cisco Fabric Switch for IBM BladeCenter

When completed, the supervisor kickstart image, supervisor system image, the linecard image and the system BIOS are all updated. Nondisruptive upgrades on these fabric switches take down the control plane for not more than 80 seconds. In some cases, when the upgrade has progressed past the point at which it cannot be stopped gracefully, or if a failure occurs, the software upgrade may be disruptive.

Note

During the upgrade the control plane is down, but the data plane remains up. So new devices will be unable to log in to the fabric via the control plane, but existing devices will not experience any disruption of traffic via the data plane. Before attempting to upgrade any software images on these fabric switches, follow these guidelines:

During the upgrade, the fabric must be stable. None of the following configuration activities are allowed:
Zoning changes Telnet sessions Schedule changes Switch cabling Addition or removal of physical devices

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

10-11

Chapter 10 Maintaining Supervisor Modules

Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Configure the FSPF timers to the default value of 20 seconds. If there are any CFS commits pending in the fabric, the upgrade is aborted. If there is a zone server merge in progress, the upgrade is aborted. Check whether there is sufficient space available in the system to load the new images using the Software Install Wizard. At this point you need to either abort the upgrade or proceed with a disruptive upgrade. On the Cisco MDS 18/4-port multiservice module, upgrades of the 4-Gigabit Ethernet ports for the hybrid Supervisor 18/4 line card will be disruptive.

Performing a Nondisruptive Upgrade on a Fabric Switch

You can use the Software Install Wizard to perform nondisruptive upgrades on Cisco MDS 9124 Fabric Switches. See the Using the Software Install Wizard section on page 10-8 for more information on using the Software Install Wizard.

Caution

It is recommended that you enable port-fast on the Ethernet interface of the Catalyst switch to which the management interface of the fabric switch is connected. This is to avoid spanning-tree convergence time on the Catalyst switch and packets from the fabric switch are forwarded immediately during the nondisruptive upgrade.

Note

When selecting images during the upgrade, ASM-SFN and SSI are not supported on the Cisco MDS 9124 Switch and the Cisco MDS 9134 Multilayer Fabric Switch.

Maintaining Supervisor Modules

This section includes general information about replacing and using supervisor modules effectively. This section includes the following topics:

Replacing Supervisor Modules, page 10-12 Migrating from Supervisor-1 Modules to Supervisor-2 Modules, page 10-13 Setting Standby Supervisor Module Boot Variable Version, page 10-13 Setting Standby Supervisor Module Bootflash Memory, page 10-13 Standby Supervisor Module Boot Alert, page 10-14

Replacing Supervisor Modules

To avoid packet loss when removing a supervisor module from a Cisco MDS 9500 Series Director, take the supervisor modules out of service before removing the supervisor module.

Note

You must remove and reinsert or replace the supervisor module to bring it into service.

Cisco DCNM Fundamentals Guide, Release 6.x

10-12

OL-25174-02

Chapter 10

Software Images Maintaining Supervisor Modules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Migrating from Supervisor-1 Modules to Supervisor-2 Modules

Cisco MDS NX-OS Release 4.1(1a) requires the Supervisor-2 modules on the Cisco MDS 9509 and 9506 Directors both active and standby. You must upgrade from Supervisor-1 modules to Supervisor-2 modules before upgrading to MDS NX-OS Release 4.1(1a) or later, using the Cisco MDS SAN-OS Release 3.3(1c) or earlier. Supervisor-1 modules and Supervisor-2 modules cannot be used in the same switch, except for migration purposes. Both the active and standby supervisor modules must be of the same type, either Supervisor-1 or Supervisor-2 modules. For Cisco MDS 9513 Directors, both supervisor modules must be Supervisor-2 modules.

Caution

Migrating your supervisor modules is a disruptive operation. When migration occurs from a Supervisor 1 to a Supervisor 2 module, a cold switchover occurs and both modules are reloaded. When the Supervisor 1 attempts to come up as the standby with the Supervisor 2 as the active supervisor, the standby is not brought up. For step-by-step instructions about migrating from Supervisor 1 modules to Supervisor 2 modules, refer to the Cisco MDS 9000 Family NX-OS and SAN-OS Software Upgrade and Downgrade Guide.

Note

Migrating from Supervisor-2 modules to Supervisor-1 modules is not supported.

Setting Standby Supervisor Module Boot Variable Version

If the standby supervisor module boot variable images are not the same version as those running on the active supervisor module, the software forces the standby supervisor module to run the same version as the active supervisor module. If you specifically set the boot variables of the standby supervisor module to a different version and reboot the standby supervisor module, the standby supervisor module will only load the specified boot variable if the same version is also running on the active supervisor module. At this point, the standby supervisor module is not running the images set in the boot variables.

Setting Standby Supervisor Module Bootflash Memory

When updating software images on the standby supervisor module, verify that there is enough space available for the image . It is a good practice to remove older versions of Cisco MDS NX-OS images and kickstart images.

DETAILED STEPS
Step 1 Step 2

Click Admin > Flash Files. Select the standby supervisor from the Partition drop-down list. At the bottom of the Flash Files dialog box, you see the space used and free space.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

10-13

Chapter 10 Installing Generation 2 Modules in Generation 1 Chassis

Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Standby Supervisor Module Boot Alert

If a standby supervisor module fails to boot, the active supervisor module detects that condition and generates a Call Home event and a system message and reboots the standby supervisor module approximately 3 to 6 minutes after the standby supervisor module moves to the loader> prompt. The following system message is issued:
%DAEMON-2-SYSTEM_MSG:Standby supervisor failed to boot up.

This error message is also generated if one of the following situations apply:

You remain at the loader> prompt for an extended period of time. You do not set the boot variables appropriately.

Installing Generation 2 Modules in Generation 1 Chassis

The Generation 2 modules have the following installation restrictions:

Supervisor-2 modules can be installed on all Cisco MDS 9500 Series Directors.

Note

The Cisco MDS 9513 Director does not support Supervisor-1 modules. Generation 2 switching modules can be installed on all Cisco MDS 9000 Family switches, except the Cisco MDS 9216 switch. Generation 1 modules can be used with Cisco MDS 9000 Family switches. However, installing Generation 1 modules in combination with Generation 2 switching modules in the same chassis reduces the capabilities of the Generation 2 switching modules. Generation 1 and Generation 2 switching modules can be installed on Cisco MDS 9500 Family switches with either Supervisor-1 modules or Supervisor-2 modules.

Replacing Modules
When you replace any module (supervisor, switching, or services module), you must ensure that the new module is running the same software version as the rest of the switch. Refer to Cisco MDS 9000 Family SAN Volume Controller Configuration Guide for configuration details on replacing the Caching Services Module (CSM).

Note

When a spare standby supervisor module is inserted, it uses the same image as the active supervisor module. The Cisco NX-OS software image is not automatically copied to the standby flash device.

Tip

Use the Software Install Wizard to copy the Cisco NX-OS software image to the standby supervisor bootflash device. Using the Software Install Wizard after replacing any module, ensures the following actions:

The proper system and kickstart images are copied on the standby bootflash: file system.

Cisco DCNM Fundamentals Guide, Release 6.x

10-14

OL-25174-02

Chapter 10

Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

The proper boot variables are set. The loader and the BIOS are upgraded to the same version available on the active supervisor module.

DETAILED STEPS
Step 1 Step 2 Step 3

Create a backup of your existing configuration file, if required, by clicking Admin > Copy Configuration and selecting runningConfig to startupConfig. Replace the required module as specified in the Cisco MDS 9200 Series Hardware Installation Guide or the Cisco MDS 9500 Series Hardware Installation Guide. Verify that space is available on the standby supervisor bootflash by choosing Admin > Flash Files and selecting the sup-standby. It is a good practice to remove older versions of Cisco MDS NX-OS images and kickstart images. Use the Software Install Wizard to ensure that the new module is running the same software as the rest of the switch. Wait until the new module is online and then ensure that the replacement was successful by choosing Physical > Modules in Device Manager.

Step 4 Step 5

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

10-15

Chapter 10

Software Images

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

10-16

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

11

Management Software FAQ

This chapter answers some of the most frequently asked questions about Cisco DCNM-SAN and Device Manager. This chapter contains the following topics:

Installation Issues, page 11-3

When installing Cisco DCNM-SAN from windows, why does clicking install fail?, page 11-3 Why do I have trouble launching Cisco DCNM-SAN on Solaris?, page 11-3 What do I do if my browser prompts to save JNLP files?, page 11-3 What do I do if I see a "Java Web Start not detected" error?, page 11-4 How do I upgrade to a newer version of Cisco DCNM-SAN or Device Manager?, page 11-4 How do I downgrade Cisco DCNM-SAN or Device Manager?, page 11-4 What do I do if an upgrade is not working?, page 11-4 What do I do if Java Web Start hangs on the download dialog?, page 11-4 How do I manually configure a browser for Java Web Start?, page 11-5 How do I run Java Web Start from the command line?, page 11-5 How do I clear the Java Web Start cache?, page 11-5 What do I do if my login does not work in Cisco DCNM-SAN or Device Manager?, page 11-6 What do I do if I cannot install Cisco DCNM-SAN or Device Manager, or run Java, when

pcAnyWhere is running?, page 11-6

What do I do if the Cisco DCNM-SAN or Performance Manager service shows up as disabled

in the Services menu?, page 11-6

What do I do if I am unable to install Cisco DCNM-SAN or Device Manager, or run Java, when

McAfee Internet Suite 6.0 Professional is running?, page 11-7

General, page 11-7

What do I do if I see errors while monitoring Area chart graphing?, page 11-7 What do I do if I see "gen error" messages?, page 11-7 What do I do if disk images in the Device Manager Summary View are not visible?, page 11-7 What do I do if I am unable to set both the D_S_TOV and E_D_TOV timers in Device

Manager?, page 11-7

What do I do if columns in Device Manager tables are too small?, page 11-8 What do I do if fabric changes are not propagated onto the map (for example, links don't

disappear)?, page 11-8

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-1

Chapter 11

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
What do I do if the PortChannel creation dialog becomes too small after several uses?,

page 11-8
What do I do if I see errors after IPFC configuration?, page 11-8 What do I do if Cisco DCNM-SAN or Device Manager is using the wrong network interface?,

page 11-8
What do I do if I see display anomalies in Cisco DCNM-SAN or Device Manager?, page 11-9 Why is the active zone set in edit zone always shown in bold (even after successful activation)?,

page 11-9
Can I create a zone with prefix IVRZ or a zone set with name nozonset?, page 11-9 What do I do when One-Click License Install fails, and I cannot connect to the Cisco website?,

page 11-9
How do I increase the log window size in Cisco DCNM-SAN Client?, page 11-10 How do I increase the log window size in Cisco DCNM-SAN Client?, page 11-10 When do I do when the FM Server Database fails to start or has a file locking error?, page 11-10

Windows Issues, page 11-10

What do I do when text fields show up too small, and I cannot enter any data?, page 11-10 What do I do when printing causes an application crash?, page 11-11 What do I do when Windows XP hangs (or I see a blue screen)?, page 11-11 What do I do when Cisco DCNM-SAN and Device Manager Icons Disappear?, page 11-11 What do I do when Device Manager or Cisco DCNM-SAN window content disappears in

Windows XP?, page 11-11

What do I do when SCP/SFTP fails when a file is copied from local machine to the switch?,

page 11-11

UNIX Issues, page 11-12

What do I do when the parent Menus Disappear?, page 11-12 What do I do when the web browser cannot find web server even it is running?, page 11-12 How do I fix a "too many open files" error?, page 11-12

Other, page 11-13

How do I set the map layout so it stays after Cisco DCNM-SAN restarted?, page 11-13 What do I do when two switches show on the map, but there is only one switch?, page 11-13 What does a red/orange/dotted line through the switch mean?, page 11-13 How do I upgrade without losing map settings?, page 11-19 How do I preserve historical data when moving Cisco DCNM-SAN server to new host?,

page 11-19
Are there restrictions when using Cisco DCNM-SAN across FCIP?, page 11-19 How do I fix a "Please insure that FM server is running on localhost" message?, page 11-20 How do I run Cisco DCNM-SAN with multiple interfaces?, page 11-20 How do I configure an HTTP proxy server?, page 11-21 How do I clear the topology map?, page 11-22 How can I use Cisco DCNM-SAN in a mixed software environment?, page 11-22

Cisco DCNM Fundamentals Guide, Release 6.x

11-2

OL-25174-02

Chapter 11

Management Software FAQ Installation Issues

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
How do I fix a "corrupted jar file" error when Launching Cisco DCNM-SAN?, page 11-22 How do I search for Devices in a Fabric?, page 11-23 How do I manage Multiple Fabrics?, page 11-24 How can I clear an Orange X Through a Switch caused by license expiration?, page 11-24

Installation Issues
When installing Cisco DCNM-SAN from windows, why does clicking install fail?
You can make sure that Java Web Start is installed properly.

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4

Go to the Programs menu and see if Java Web Start is there. Start the Java Web Start program to make sure there is no problem with the Java Runtime installation. Click the Preferences tab, and make sure the proxies settings are fine for Web Start. Check that your browser is set up to handle JNLP settings properly (see the How do I manually configure a browser for Java Web Start? section on page 11-5).

If you had older versions of the application and you see an error pop-up window saying cannot open the JNLP file (in the error details), this could be because the Java Web Start cache is messed up. To work around this, clear the cache and retry. To clear the cache, see the How do I clear the Java Web Start cache? section on page 11-5.

Why do I have trouble launching Cisco DCNM-SAN on Solaris?

If you are using Solaris 2.8 and are logged in as root and are using Netscape Navigator 6, you will not be able to register the mime-type. Regular users can register the mime-type with Netscape Navigator 6 by manually adding it. Netscape 4.x works fine for all users.

What do I do if my browser prompts to save JNLP files?

Your browser may not be set up to launch Java Web Start for JNLP mime types. Java Web Start is probably not installed or configured properly (see the How do I manually configure a browser for Java Web Start? section on page 11-5).

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-3

Chapter 11 Installation Issues

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

What do I do if I see a "Java Web Start not detected" error?

If you installed Java Web Start but still see an error message (in red) saying Java Web Start not detected... on the switch home page, it could be a simple JavaScript error. We try to detect a Java Web Start installation by running some JavaScript code tested for Internet Explorer and Mozilla (newer versions). On some browsers (for example, Netscape 6.0, Opera) this code does not work properly although the links still work.

First, try clicking on the install links. If that does not work, check to see if the browser helper applications settings are correct (for example, for Netscape 6.0 Edit > Preferences > Navigator > Helper Applications ). See the How do I manually configure a browser for Java Web Start? section on page 11-5.

How do I upgrade to a newer version of Cisco DCNM-SAN or Device Manager?

DETAILED STEPS
Step 1 Step 2

Close all running instances of Cisco DCNM-SAN or Device Manager. Point your browser at the switch running the new version and click the appropriate install link. Cisco DCNM-SAN or Device Manager prompts you to upgrade if the switch is running a newer version. The installer checks your local copies and updates any newer versions of the software.

How do I downgrade Cisco DCNM-SAN or Device Manager?

As of Cisco MDS NX-OS Release 4.x, downgrades are not supported through the installer. To downgrade Cisco DCNM-SAN or Device Manager to an earlier release, you need to manually uninstall first and then install the previous version of Cisco DCNM-SAN or Device Manager.

What do I do if an upgrade is not working?

If you are trying to upgrade because Cisco DCNM-SAN or Device Manager prompted you saying that the switch version is higher, and the upgrade failed, it might be because your default browser settings are incorrect. Some error must have occurred during your last browser upgrade/install. To work around this, launch the browser independently and click on install. On rare occasions, we have seen the upgrade happen but the version does not change. This is because of HTTP caching in the network. During the upgrade, HTTP requests for files on the switch get cached in the local machine. Even though the switch is in a higher version, the management software installed is at the old version. The workaround for this is to uninstall the Fabric/Device Manager, clear the Java Web Start cache, and then do a clean install.

What do I do if Java Web Start hangs on the download dialog?

You can make sure Java Web Start is set up to access the switch in the same way your browser is set up.

Cisco DCNM Fundamentals Guide, Release 6.x

11-4

OL-25174-02

Chapter 11

Management Software FAQ Installation Issues

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1 Step 2 Step 3 Step 4

Start Java Web Start (javaws.exe or javaws). You see the Java Web Start Application Manager. Choose File > Preferences > General and make sure your proxy settings are correct. For example, if you are using an HTTP proxy, set it up here. Choose Use Browser. Click OK.

How do I manually configure a browser for Java Web Start?

For browsers like Opera, certain versions of Mozilla, or Konqueror, you must manually register Java Web Start as the helper application for the JNLP files. To do this, the data you need is:

Description=Java Web Start File Extension=jnlp Mime Type=application/x-java-jnlp-file Application=path-to-javaws (e.g. /usr/local/javaws/javaws)

After setting this up, you may need to restart the browser. If you see "Java Web Start not detected" warnings, you can ignore them. These warnings are based on JavaScript, and not all browsers behave well with JavaScript. Click on the install links to install Cisco DCNM-SAN or Device Manager.

Note

For Windows Users: To set up Java Web Start on *.jnlp files, select Windows Explorer > Tools > Folder Options > File Types. Either change the existing setting for JNLP or add one so that *.jnlp files are opened by javaws.exe. This executable is under Program Files\Java Web Start

How do I run Java Web Start from the command line?

If you cannot get your browser to run Java Web Start, you can still run Java Web Start from the command line (javaws.exe or javaws) giving it the URL of the Cisco DCNM-SAN or Device Manager on the switch as an argument. For example, if your switch IP address is 10.0.0.1, you would use these commands to start Cisco DCNM-SAN and Device Manager:
javaws http://10.0.0.1/cgi-bin/fabric-manager.jnlp javaws http://10.0.0.1/cgi-bin/element-manager.jnlp

How do I clear the Java Web Start cache?

DETAILED STEPS
Step 1

Start the Java Web Start Application Manager (javaws.exe or javaws).

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-5

Chapter 11 Installation Issues

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2

Go to File > Preferences > Advanced and clear the applications folder or cache. You can manually delete the .javaws or cache directory. On Windows this is under Documents and Settings, and on UNIX this is under $HOME.

What do I do if during a Cisco DCNM-SAN upgrade, the installer doesnt display a prompt to create a shortcut?
Clear the Java Web Start cache as described in How do I clear the Java Web Start cache? in this chapter.

What do I do if my login does not work in Cisco DCNM-SAN or Device Manager?

Make sure you have done the Initial Setup Routine on the switch. Quick checks:

Make sure that the management interface on the switch is up (show interface mgmt0). Check whether you can connect to the management interface (ping). Verify the username is valid (show snmp user). You can also add/edit the users through the CLI. If you have multiple network interfaces, see the What do I do if Cisco DCNM-SAN or Device Manager is using the wrong network interface? section on page 11-8

What do I do if I cannot install Cisco DCNM-SAN or Device Manager, or run Java, when pcAnyWhere is running?
You can either stop the pcAnyWhere service and install Cisco DCNM-SAN or Device Manager, or install/update DirectX. For more information,refer to the website at www.oracle.com

What do I do if the Cisco DCNM-SAN or Performance Manager service shows up as disabled in the Services menu?
This could happen if:

The service menu for Cisco DCNM-SAN or Performance Manager was open during an uninstall/upgrade. The Cisco DCNM-SAN client or Device Manager was running while doing an uninstall/upgrade.

This error happens when Windows is unable to delete a service completely. A reboot of the host should fix the problem.

Cisco DCNM Fundamentals Guide, Release 6.x

11-6

OL-25174-02

Chapter 11

Management Software FAQ General

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

What do I do if I am unable to install Cisco DCNM-SAN or Device Manager, or run Java, when McAfee Internet Suite 6.0 Professional is running?
The McAfee internet suite comes with a virus scanner, firewall, antispam, and privacy management. The privacy management can interfere with the Cisco DCNM-SAN server-client interactions. To work around this you must shut down the privacy service.

General
What do I do if I see errors while monitoring Area chart graphing?
When doing the area chart graphing from the monitor window, if you move the mouse over the Area chart before the first data comes back, you see a java.lang.ArrayIndexOutOfBoundsException error on the message log from JChart getX(). This is because JChart tries to locate a value that does not exist yet. This might be fixed in a future version of JChart.

What do I do if I see "gen error" messages?

Usually a "gen error" means that the SNMP agent on the switch had an unexpected error in the process of serving an SNMP request. However, when you are accessing the switch through a VPN connection or any sort of NAT scheme, all errors are reported as gen error. This is a known problem and will be fixed in a future release. You can verify whether this was the reason behind your gen error by trying to reproduce this error in an environment where there is no network address translation (where you are on the same network as the switch).

What do I do if disk images in the Device Manager Summary View are not visible?
On some occasions the Summary View table in the Device Manager does not show the icons for disks attached to a Fx port. This is because the FC4 features are empty for this port. A LUN discovery must be issued to discover information about these hosts/disks that do not register their FC4 types. You can do this in the Device Manager by clicking FC > Advanced > LUNs.

What do I do if I am unable to set both the D_S_TOV and E_D_TOV timers in Device Manager?
If you modify both E_D_TOV and D_S_TOV at the same time, and the new D_S_TOV value is larger than the old E_D_TOV value, you will get a WrongValue error. To work around this, you must change the values separately.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-7

Chapter 11 General

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

What do I do if columns in Device Manager tables are too small?

If Device Manager is trying to display a large table and your switch is running slowly, the table will come up with the tabs being hidden. To work around this, you must resize the window to see the data.

What do I do if fabric changes are not propagated onto the map (for example, links don't disappear)?
Cisco DCNM-SAN shows that a device or port is down by displaying a red cross on that port or device. However, Cisco DCNM-SAN does not remove any information that's already discovered. You must rediscover to correctly update the map.

What do I do if the PortChannel creation dialog becomes too small after several uses?
After several uses, the MemberList TextBox (in the PortChannel Create Window) does not display as it should. It changes from a long TextBox with a ComboBox for choosing ports, to a small square TextBox that is too small to choose ports. This is a known problem and will be fixed in a future release. To work around this problem, stop and restart Cisco DCNM-SAN or Device Manager.

What do I do if I see errors after IPFC configuration?

When IPFC and out of band management are configured, the Device Manager might not work using SNMPv3 if you use the IPFC address. The workaround is either to use the management interface (mgmt0) address, or to use SNMPv1/v2c over IPFC.

What do I do if Cisco DCNM-SAN or Device Manager is using the wrong network interface?
The problem happens because the underlying Java library picks a local interface arbitrarily. To work around this, supply a command line argument before starting the Fabric/Device Manager. In the desktop shortcut or shell script or batch file, add the following parameter "-Device Managerds.nmsAddress=" For example, in Windows the line looks like ".javaw.exe -Device Managerds.nmsAddress=X.X.X.X -cp .". In desktop shortcuts, this length could exceed the maximum characters allowed. If this happens, delete the "-Dsun.java2d.ddoffscreen=false" portion to make more space. Releases 1.2 and later allow you to pick a preferred network interface.

Cisco DCNM Fundamentals Guide, Release 6.x

11-8

OL-25174-02

Chapter 11

Management Software FAQ General

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

What do I do if I see display anomalies in Cisco DCNM-SAN or Device Manager?

If you see Cisco DCNM-SAN or Device Manager submenus detached from menus, the mouse pointer in Cisco DCNM-SAN Map is slow to react to mouse movement, or a wrong tooltip is displayed, these are display anomalies, not problems with Cisco DCNM-SAN or Device Manager. Some older video cards exhibit these display anomalies. To fix this, first try updating the video drivers. If this doesn't solve the problem, replace the video card.

What do I do if most of my Physical Attributes catagories disappear?

You have somehow turned off advanced features. Look for the check box Advanced Features in the upper right of the Cisco DCNM-SAN screen. Check the box.

What do I do if I cant see the Information pane?

The information pane should be in the upper half of the screen above the map in Cisco DCNM-SAN. The map my be covering it. Drag the edge of the map window down or use the black triangles to reorganize the display.

Why is the active zone set in edit zone always shown in bold (even after successful activation)?
A member of this VSAN must be participating in IVR zoning. Because the IVR zones get added to active zones, the active zone set configuration is always different from the local zone set configuration with the same name. The zone set name is always bold.

Can I create a zone with prefix IVRZ or a zone set with name nozonset?
Do not use these special names. These names are used by the system for identifying IVR zones.

What do I do when One-Click License Install fails, and I cannot connect to the Cisco website?
The one-click license install tries to open an HTTP connection to the Cisco website. If you do your browsing using an HTTP proxy then the following command- line variables need to be added to your Cisco DCNM-SAN client scripts:
-Dhttps.proxyHost and -Dhttps.proxyPort.

In case your one-click install URL starts with "http://" (and not "https://"), the variables are:
-Dhttp.proxyHost and -Dhttp.proxyPort.

For example, in Windows, edit the MDS 9000\bin\FabricManager.bat file and add to the JVMARGS "-Dhttps.proxyHost=HOSTADDRESS -Dhttps.proxyPort=HOSTPORT".

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-9

Chapter 11 Windows Issues

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

How do I increase the log window size in Cisco DCNM-SAN Client?

To limit the memory usage by FM Client, the log window is limited to 500 lines by default. If you want to increase this, edit sm.properties in < install directory>/db/<user> directory and change LogBufferSize.

When do I do when the FM Server Database fails to start or has a file locking error?
In the database log (FMPersist.log) you will see an error message "The database is already in use by another process". The HsqlDB 1.7.1 version has this problem. The file lock problem seems to happen occasionally, and can be resolved by shutdown and restart of the db server. On windows this can be done by stopping and starting the FMPersist service and on Unix just run the FMPersist.sh script with the argument restart.

How do I re-synchronize Cisco DCNM-SAN Client with Cisco DCNM-SAN Server?

On some occasions, when the Cisco DCNM-SAN Client in not in sync with the Cisco DCNM-SAN Server, you may need to re-synchronize the client and server. To re-synchronize Fabrix Manager Client with Cisco DCNM-SAN Server, click Resync All Open Fabrics from the File menu,

How do I rediscover the current fabric?

When the Cisco DCNM-SAN Server is not in sync with the switches in the fabric, you may need to initiate an on- demand discovery to update the Cisco DCNM-SAN Client with the most recent changes from the switches in the fabric. To rediscover the fabric switches, click Rediscover from the File menu.

How do I rediscover SCSI Targets?

When the Cisco DCNM-SAN Server is not in sync with the SCSI Target switches in the fabric, you may need to initiate an on- demand discovery to update the Cisco DCNM-SAN Client with the most recent changes from the SCSI Target switches in the fabric. To rediscover the fabric switches, click Rediscover SCSI Targets from the File menu.

Windows Issues
What do I do when text fields show up too small, and I cannot enter any data?
When Reflection X is running, certain text fields in the Cisco DCNM-SAN and Device Manager are not rendered to the full width of the field. Resize the dialog box to see the text fields properly.

Cisco DCNM Fundamentals Guide, Release 6.x

11-10

OL-25174-02

Chapter 11

Management Software FAQ Windows Issues

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

What do I do when printing causes an application crash?

On Windows NT there is a known Sun JVM bug - the printservice crashes the VM. The solution suggested by Sun is to update NT with SP 6. For more details refer to: http://developer.java.sun.com/developer/bugParade/bugs/4530428.html.

What do I do when Windows XP hangs (or I see a blue screen)?

Windows XP with the ATI Radeon AGP graphics cards has known to freeze (hang) when a Java application exits. The newer drivers from ATI seem to have fixed this problem. The other workaround is to run the application with "-Dsun.java2d.noddraw=true". We do this today in the shortcut and shell scripts we create. For more details refer to: http://developer.java.sun.com/developer/bugParade/bugs/4713003.html.

What do I do when Cisco DCNM-SAN and Device Manager icons disappear?

On certain versions of Windows, certain images disappear. This is a Java bug. We have a workaround that is already in place (disable DirectDraw acceleration) - but there are still cases where this problem might arise. For more details refer to: http://developer.java.sun.com/developer/bugParade/bugs/4664818.html.

What do I do when Device Manager or Cisco DCNM-SAN window content disappears in Windows XP?
Device Manager or Cisco DCNM-SAN main window content disappears in Windows XP due to a Java bug. Refer to the following website: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4919780. Minimize or maximize the window and restore to the normal size to restore the window content. Disabling Direct Draw may also prevent this from happening by adding "-Dsun.java2d.noddraw=true" to JVMARGS in <FM-install-dir>/bin/FabricManager.bat and DeviceManager.bat

What do I do when SCP/SFTP fails when a file is copied from local machine to the switch?
If there are embedded spaces in the file path, then windows scp/sftp might fail. You will get a copyDeviceBusy error from the switch. In tools such as the License Wizard either make sure tftp copy can be done or pick filenames with no spaces.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-11

Chapter 11 UNIX Issues

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

UNIX Issues
What do I do when the parent menus disappear?
Displaying a submenu may occasionally cause the parent menu to disappear. For more details on this bug, refer to: http://developer.java.sun.com/developer/bugParade/bugs/4470374.html.

What do I do when the web browser cannot find web server even it is running?
This can happens when web browser uses proxy server. To check that for Internet Explorer, choose tools in menu, then choose internet options, then choose connection subpanel, then click Lan Setting. A dialog comes up, verify the proxy setting.

How do I fix a "too many open files" error?

If you are running the JVM (Java Virtual Machine) on Linux and the drive where Java is installed or your home directory is NFS mounted, there is an open bug against the Sun JDK about errors acquiring file locks. The symptoms for the Cisco DCNM-SAN are that launching a Device Manager or saving/opening files will fail, giving a "too many open files" I/O or socket exception. The JVM keeps trying to open a file on the NFS mounted drives, fails, and keeps trying to do it until it hits the 1024 file descriptors limit. Workarounds (assuming /tmp is a local disk - replace it with your tmp area):

System Preferences Make sure the system level preferences are stored on a local disk. The system preferences are stored in $JAVA_HOME/.systemPrefs where JAVA_HOME is where you have installed the JDK. If this directory is NFS mounted, then just do the following:
$ rm -rf $JAVA_HOME/.systemPrefs< $ mkdir /tmp/.systemPrefs $ ln -s /tmp/.systemPrefs $JAVA_HOME/.systemPrefs

The problem with this workaround is that you have to make sure /tmp/.systemPrefs exists on every box where you are using $JAVA_HOME. We recommend installing the JVM as root and on a local disk.

User Preferences If your home directory is NFS mounted and you are getting this problem. Do the following:
$ rm -rf $HOME/.java $ mkdir /tmp/.java.$USER $ ln -s /tmp/.java.$USER $HOME/.java

For further details, see the following URLs: http://developer.java.sun.com/developer/bugParade/bugs/4673298.html http://developer.java.sun.com/developer/bugParade/bugs/4635353.html

Cisco DCNM Fundamentals Guide, Release 6.x

11-12

OL-25174-02

Chapter 11

Management Software FAQ Other

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Other
How do I set the map layout so it stays after Cisco DCNM-SAN restarted?
You can arrange the map to your liking and would like to freeze the map so that the objects stay as they are even after you stop Cisco DCNM-SAN and restart it again.

DETAILED STEPS
Step 1 Step 2

Right-click in a blank space in the map. You see a menu. Select Layout > Fix All Nodes from the menu.

What do I do when two switches show on the map, but there is only one switch?
If two switches show on your map, but you only have one switch, it may be that you have two switches in a non-contiguous VSAN that have the same Domain ID. Cisco DCNM-SAN uses <vsanId><domainId> to look up a switch, and this can cause the fabric discovery to assign links incorrectly between these errant switches. The workaround is to verify that all switches use unique domain IDs within the same VSAN in a physically connected fabric. (The fabric configuration checker will do this task.)

What does a red/orange/dotted line through the switch mean?

If a red line shows through your switch, this means Fabric Manger sees something wrong with the switch. Choose Switches in the Physical Attributes pane to see a status report in the information pane. A module, fan, or power supply has failed or is offline and plugged in. If a dotted orange line shows through your switch, this indicates a minor status warning for that switch. Usually it means an issue with one of the modules. The tooltip should say exactly what is wrong. Hold the mouse over the switch to see the tooltip. Below are tables of color settings and tooltip definitions for Cisco DCNM-SAN and Device Manager.
Table 11-1 Cisco DCNM-SAN Client and Device Manager Color Definitions

Cisco DCNM-SAN Color Red Slash Red X

Definition Cannot communicate with a switch via SNMP. Cannot communicate with or see a switch in the Domain Manager/Fabric Configuration Server list of fabric switches. Definition Port up.

Device Manager Color Green Square with Mode (e.g., F, T, TE, U/I for FICON)

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-13

Chapter 11 Other

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 11-1 Cisco DCNM-SAN Client and Device Manager Color Definitions (continued)

Cisco DCNM-SAN Color Orange Square with Mode Orange Cross Brown Square Light Gray Square Red Cross Red Square No Square or Black Square

Definition Trunk incomplete. Ols or Nos received. Port is administratively down. Port is not manageable. HardwareFailure/LoopbackDiagFailure/LinkFail ure Any other kind of configuration failure. Port not yet configured.

Table 11-2

Device Manager Tooltip Definitions

Tooltip adminDown bitErrRTThresExceeded bundleMisCfg channelAdminDown channelConfigurationInProgress channelOperSuspended

Definition The port is administratively down. Bit error rate too high. Misconfiguration in PortChannel membership detected. This port is a member of a PortChannel and that PortChannel is administratively down. This port is undergoing a PortChannel configuration. This port is a member of a PortChannel and its operational parameters are incompatible with the PortChannel parameters. Suspended due to port binding. The elected principal switch is not capable of performing domain address manager functions so no Nx_port traffic can be forwarded across switches, hence all Interconnect_Ports in the switch are isolated. Invalid RCF received. Domain manager is disabled. Domain manager failure after maximum retries. The peer E port is isolated. There is a overlap in domains while attempting to connect two existing fabrics. Isolated for ELP failure due to class F parameter error. Isolated for ELP failure due to class N parameter error.

deniedDueToPortBinding domainAddrAssignFailureIsolation

domainInvalidRCFReceived domainManagerDisabled domainMaxReTxFailure domainOtherSideEportIsolation domainOverlapIsolation elpFailureClassFParamErr elpFailureClassNParamErr

Cisco DCNM Fundamentals Guide, Release 6.x

11-14

OL-25174-02

Chapter 11

Management Software FAQ Other

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 11-2 Device Manager Tooltip Definitions (continued)

Tooltip elpFailureInvalidFlowCTLParam elpFailureInvalidPayloadSize elpFailureInvalidPortName elpFailureInvalidSwitchName elpFailureInvalidTxBBCredit elpFailureIsolation

Definition Isolated for ELP failure due to invalid flow control parameter. Isolated for ELP failure due to invalid payload size. Isolated for ELP failure due to invalid port name. Isolated for ELP failure due to invalid switch name. Isolated for ELP failure due to invalid transmit B2B credit. During a port initialization the prospective Interconnect_Ports find incompatible link parameters. Isolated for ELP failure due to loopback detected. Isolated for ELP failure due to R_A_TOV or E_D_TOV mismatch. Isolated for ELP failure due to revision mismatch. Isolated for ELP failure due to invalid flow control code. Port down because FICON prohibit mask in place for E/TE port. Trunk negotiation protocol failure after maximum retries. The port is not operational due to some error conditions that require administrative attention. During a port initialization the prospective Interconnect_Ports are unable to proceed with initialization as a result of Exchange Switch Capabilities (ESC). fabric bindingactive database mismatch with peer. Peer domain ID is invalid in fabric binding active database. Fabric binding no response from peer. Peer switch WWN not found in fabric binding active database. FCIP port went down due to configuration change. FCIP port went down due to TCP keep alive timer expired. FCIP port went down due to max TCP retransmissions reached the configured limit.

elpFailureLoopbackDetected elpFailureRatovEdtovMismatch elpFailureRevMismatch elpFailureUnknownFlowCTLCode ePortProhibited eppFailure errorDisabled escFailureIsolation

fabricBindingDBMismatch fabricBindingDomainInvalid fabricBindingNoRspFromPeer fabricBindingSWWNNotFound fcipPortAdminCfgChange fcipPortKeepAliveTimerExpire fcipPortMaxReTx

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-15

Chapter 11 Other

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 11-2 Device Manager Tooltip Definitions (continued)

Tooltip fcipPortPersistTimerExpire fcipPortSrcAdminDown fcipPortSrcLinkDown fcipSrcModuleNotOnline fcipSrcPortRemoved fcotChksumErr fcotNotPresent fcotVendorNotSupported fcspAuthenfailure ficonBeingEnabled ficonNoPortnumber ficonNotEnabled ficonVsanDown firstPortNotUp

Definition FCIP port went down due to TCP persist timer expired. FCIP port went down because the source ethernet link was administratively shutdown. FCIP port went down due to ethernet link down. FCIP port went down due to source module not online. FCIP port went down due to source port removal. FSP SPROM checksum error. SFP (GBIC) not present. FSP (GBIC) vendor is not supported. Fibre Channel security protocol authorization failed. FICON is being enabled. No FICON port number. FICON not enabled. FICON VSAN is down. In a over subscribed line card, first port cannot be brought up in E mode when the other ports in the group are up. In a over subscribed line card, when the first port in a group is up in E mode, other ports in that group cannot be brought up. Hardware failure. Disabled due to incompatible admin port rxbbcredit, performance buffers. Port admin mode is incompatible with port capabilities. Receive BB credit is incompatible. Receive buffer size is incompatible. Port speed is incompatible with port capabilities. The port is being initialized. Interface is being removed. Invalid attachment. This port has a misconfiguration with respect to port channels. Invalid fabric binding exchange. Link failure due to excessive credit loss indications.

firstPortUpAsEport

hwFailure incomAdminRxBBCreditPerBuf incompatibleAdminMode incompatibleAdminRxBBCredit incompatibleAdminRxBufferSize incompatibleadminSpeed initializing interfaceRemoved invalidAttachment invalidConfig invalidFabricBindExh linkFailCreditLoss

Cisco DCNM Fundamentals Guide, Release 6.x

11-16

OL-25174-02

Chapter 11

Management Software FAQ Other

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 11-2 Device Manager Tooltip Definitions (continued)

Tooltip linkFailCreditLossB2B linkFailDebounceTimeout linkFailLineCardPortShutdown linkFailLinkReset linkFailLIPF8Rcvd linkFailLIPRcvdB2B linkFailLossOfSignal linkFailLossOfSync linkFailLRRcvdB2B linkFailNOSRcvd linkFailOLSRcvd linkFailOPNyRETB2B linkFailOPNyTMOB2B linkFailPortInitFail linkFailPortUnusable linkFailRxQOverFlow linkFailTooManyINTR linkFailure loopbackDiagFailure loopbackIsolation noCommonVsanIsolation none nonParticipating offline ohmsExtLBTest other parentDown

Definition Link failure when link reset (LR) operation fails due to queue not empty. Link failure due to re-negotiation failed. Link failure due to port shutdown. Link failure due to link reset. Link failure due to F8 LIP received. Link failure when loop initialization (LIP) operation fails due to non empty receive queue. Link failure due to loss of signal. Link failure due to loss of sync. Link failure when link reset (LR) operation fails due to non-empty receive queue. Link failure due to non-operational sequences received. Link failure due to offline sequences received. Link failure due to open primitive signal returned while receive queue not empty. Link failure due to open primitive signal timeout while receive queue not empty. Link failure due to port initialization failure. Link failure due to port unusable. Link failure due to receive queue overflow. Link failure due to excessive port interrupts. Physical link failure. Loopback diagnostics failure. Port is connected to another port in the same switch. Trunk is isolated because there are no common vsans with peer. No failure. During loop initialization, the port is not allowed to participate in loop operations Physical link is in offline state as defined in the FC-FS standards. Link suspended due to external loopback diagnostics failure. Undefined reason. The physical port to which this interface is bound is down.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-17

Chapter 11 Other

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 11-2 Device Manager Tooltip Definitions (continued)

Tooltip peerFCIPPortClosedConnection peerFCIPPortResetConnection portBindFailure portBlocked portChannelMembersDown portFabricBindFailure portGracefulShutdown portVsanMismatchIsolation rcfInProgres

Definition Port went down because peer FCIP port closed TCP connection. Port went down because the TCP connection was reset by the peer FCIP port. Port got isolated due to port bind failure. Port blocked due to FICON. No operational members. Port isolated due to fabric bind failure. Port shutdown gracefully. An attempt is made to connect two switches using non-trunking ports having different port VSANs. An isolated xE_port is transmitting a reconfigure fabric, requesting a disruptive reconfiguration in an attempt to build a single, non-isolated fabric. Only the Interconnect_Ports can become isolated. No source port is specified for this interface. Port that belongs to a port channel is suspended due to incompatible operational mode. Port that belongs to a port channel is suspended due to incompatible operational speed. Port that belongs to a port channel is suspended due to incompatible remote switch WWN. Software failure. Suspended due to too many invalid FLOGIs. Link isolation due to TOV mismatch Some of the VSANs which are common with the peer are not up. Line card upgrade in progress. Port VSAN is inactive. The port becomes operational again when the port VSAN is active. This VSAN is not configured on both sides of a trunk port. The two Interconnect_Ports cannot merge zoning configuration after having exchanged merging request for zoning. Isolation due to remote zone server not responding.

srcPortNotBound suspendedByMode suspendedBySpeed suspendedByWWN swFailure tooManyInvalidFLOGIs tovMismatch trunkNotFullyActive upgradeInProgress vsanInactive vsanMismatchIsolation zoneMergeFailureIsolation

zoneRemoteNoRespIsolation

Cisco DCNM Fundamentals Guide, Release 6.x

11-18

OL-25174-02

Chapter 11

Management Software FAQ Other

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

How do I upgrade without losing map settings?

When you upgrade from one version of Cisco DCNM-SAN to another, there is a way to prevent the loss of map settings (enclosure names, placement on the map, etc.) The MDS 9000/db directory contains subfolders for each user (and one for fmserver). In these subfolders are files for all discovered fabrics (*.dat) and maps (*.map). These are upgradable between versions. If you need to clear the fabric cache, you should first export the enclosures to a file to avoid losing them. Everything else aside from enclosures and map coordinates are stored on the switch. The preferences, last opened, and site_ouis.txt format doesnt change from release to release.

How do I preserve historical data when moving Cisco DCNM-SAN server to new host?
DETAILED STEPS
Step 1 Step 2 Step 3 Step 4

Export the enclosures to a file. Reinstall Cisco DCNM-SAN (if you are installing on a new host, install Cisco DCNM-SAN). After the installation is complete, stop Cisco DCNM-SAN Server. Copy the RRD files from the old host to the new host. Place it in the database directory (on a Windows PC, the default installation location for this directory is C:\Program Files\Cisco Systems\DCM\fm\pm\db). On the new host, run PM.bat sync from the $INSTALLDIR\dcm\fm\bin folder. This creates files and a new directory structure. There is a directory for each switch for which you have collected data. Continue to collect data on a specific switch by copying the db subfolder from that switchs folder to the pm folder. Restart Cisco DCNM-SAN Server. Add the fabric to Performance Manager Collection. Reimport the enclosures on the new host. Be sure to turn off the original service on the old host.

Step 5 Step 6 Step 7 Step 8 Step 9 Step 10

Are there restrictions when using Cisco DCNM-SAN across FCIP?

Cisco DCNM-SAN will work with no restriction across an FCIP tunnel, as long as the tunnel is up. However, Cisco DCNM-SAN cannot automatically discover a Cisco SN5428 mgmt IP address in the fabric. For that switch, it will display a red slash through an FCIP device because of a timeout error. It will still see all targets, initiators, and ISLs attached to a Cisco SN5428 (or any other switch) as long as they appear in the name server or FSPF. To work around this, you can manually enter the IP address in the Switches table, and click Apply. If the community string is correct, the red slash will go away. Even if the community string is incorrect, double-clicking on the Cisco SN5428 will launch the web tool.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-19

Chapter 11 Other

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

How do I fix a "Please insure that FM server is running on localhost" message?

You may see this error message if you cannot connect to the fabric and your PC has multiple network interface cards. The problem may be that Cisco DCNM-SAN is trying to communicate through the wrong interface (you can verify this by checking the FMServer.log file). Generally it is best to let Cisco DCNM-SAN choose the interface on startup. If you are getting the above error, something may have gone wrong.

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4

Open the server.properties file in the Cisco DCNM-SAN installation directory. On a Windows platform, this file is in C:\Program Files\Cisco Systems\dcm by default. Comment out the line: snmp.localaddress. Save and exit the file. Restart Cisco DCNM-SAN server.

Note

There are some cases where you would not want to do this, and should manually select the interface that Cisco DCNM-SAN uses. For more information, see theHow do I run Cisco DCNM-SAN with multiple interfaces? section on page 11-20.

How do I run Cisco DCNM-SAN with multiple interfaces?

If your PC has multiple interfaces (NICs), the four Cisco DCNM-SAN applications detect these interfaces automatically (ignoring loopback interfaces). Cisco DCNM-SAN Client and Device Manager detect all interfaces on your PC each time you launch them, and allow you to select one. Cisco DCNM-SAN Server and Performance Manager detect on initial install, and allows you to select one. You are not prompted again to choose an interface with these two applications. There may be circumstances where you will want to change the interface you are using. For example:

If you add an interface after you have installed Cisco DCNM-SAN Server and/or Performance Manager If you decide to use a different interface than the one you initially selected If for any reason one of the Cisco DCNM-SAN applications did not detect multiple interfaces Manually specifying an interface for Cisco DCNM-SAN Server, page 11-21 Manually specifying an interface for Cisco DCNM-SAN Client or Device Manager, page 11-21

Refer to the following sections, depending on which application you want to recognize the interface.

Cisco DCNM Fundamentals Guide, Release 6.x

11-20

OL-25174-02

Chapter 11

Management Software FAQ Other

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Manually specifying an interface for Cisco DCNM-SAN Server

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

Go to the MDS 9000 folder. On a Windows platform, this folder is at C:\Program Files\Cisco Systems\MDS 9000 by default. Edit the server.properties file with a text editor. Scroll until you find the line: snmp.localaddress. If the line is commented, remove the comment character. Set the local address value to the IP address or interface name of the NIC you want to use. Save the file. Stop and restart Cisco DCNM-SAN Server.

Manually specifying an interface for Cisco DCNM-SAN Client or Device Manager

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4 Step 5

Go to the MDS 9000/bin folder. On a Windows platform, this folder is at C:\Program Files\Cisco Systems\MDS 9000 by default. Edit the DeviceManager.bat file or the FabricManager.bat file. Scroll to the line that begins with set JVMARGS= Add the parameter -Device Managerds.nmsaddress=ADDRESS, where ADDRESS is the IP address or interface name of the NIC you want to use. Save the file and relaunch Cisco DCNM-SAN Client or Device Manager.

How do I configure an HTTP proxy server?

If your network uses a proxy server for HTTP requests, make sure the Java Web Start Application Manager is properly configured with the IP address of your proxy server.

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4 Step 5

Launch the Java Web Start application. Choose File > Preferences from the Java WebStart Application Manager. Choose the Manual radio button and enter the IP address of the proxy server in the HTTP Proxy field. Enter the HTTP port number used by your proxy service in the HTTP Port field. Click OK.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-21

Chapter 11 Other

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

How do I clear the topology map?

If you have a switch that you have removed from the fabric, there will be a red X through the switchs icon. You can clear this information from the Cisco DCNM-SAN client, or from the Cisco DCNM-SAN server (which will clear the information for all clients) without having to reboot the switch.

DETAILED STEPS
Step 1

Click the Refresh Map icon in the Fabric pane. This clears the information from the client. Click Purge Down Elements in the Server menu. This clears the information from the server.

Step 2

Caution

Any devices not currently accessible (may be offline) are purged.

How can I use Cisco DCNM-SAN in a mixed software environment?

You can use Cisco DCNM-SAN version 2.0(x) to manage a mixed fabric of Cisco MDS 9000 switches. Certain 2.0 feature tabs will be empty for any switches running a software version that does not support those features.

How do I fix a "corrupted jar file" error when launching Cisco DCNM-SAN?
If you get the following error:
An error occurred while launching the application Cisco DCNM-SAN. download error:corrupted jar file at <ipaddress>\Device Managerboot.jar

(Where <ipaddress> is that of the switch) The error message you are getting indicates that the Java Web Start cache is corrupted. You can try clearing your Java Web Start cache first. To clear the Cache either run Java Web Start (from the Programs menu) and under the preferences select clear cache. Or do it manually by first making sure all Cisco DCNM-SAN or Device Manager instances are closed and then deleting .javaws/cache. In the newer JREs this directory is created under Documents and Settings\USERNAME and in the older ones it used to be under Program Files\Java Web Start. You can also browse beneath the cache folder and delete the offending IPAddress folder (e.g. cache/http/D10.0.0.1). Also, check to make sure that the host is not running a virus checker / java blocker? You also can run the uninstall program and delete .cisco_mds directory, and then reinstall Cisco DCNM-SAN.

Cisco DCNM Fundamentals Guide, Release 6.x

11-22

OL-25174-02

Chapter 11

Management Software FAQ Other

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

How do I search for devices in a fabric?

In Cisco DCNM-SAN, you can search for one or more devices by different attributes, including pWWN.

DETAILED STEPS
Step 1

Right-click the map and choose Find Elements from the drop-down menu. You see the Find Fabric dialog box as shown in Figure 11-1. Choose End Device from the left drop-down list. Choose Port WWN from the right drop-down list. You can also enter only part of the WWN and use a wildcard (*) character (for example, you can enter *fb*f8).
Figure 11-1 Find Fabric Dialog Box with End Device and Port WWN Selected

Step 2 Step 3

Step 4

Click Find in Map. To search for devices in a zone, click Find in Zones. You see the device highlighted in the Fabric pane. Right-click any device to see the attributes for that device. You can also select a link leading to a device to see the attributes for the link.

How do I search in a table?

In Cisco DCNM-SAN, you can search for devices having one or more attributes. You can enter a search string in the Find dialog box and then use Next and Previous buttons to navigate through the results.

DETAILED STEPS
Step 1

Click the Find icon from the tool bar. You see the Find dialog box.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

11-23

Chapter 11 Other

Management Software FAQ

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

Enter the search string in the Find text box. Click Selection to search in selected row(s). Check Ignore Case to ignore case sensitivity. Check Exact Match to search for the data value exactly matching the search string. Click Next to search. Click Cancel to close the dialog box.

How do I manage multiple fabrics?

To monitor and manage multiple fabrics, you must persist one or more fabrics. Do this by checking the Persist checkbox on the Server>Admin dialog Fabric tab. You must also use switches running SAN-OS Release 1.3.x or later in both fabrics, and you must use the same user/password on both fabrics. Both fabrics must not be physically connected.

How can I clear an orange X through a switch caused by license expiration?

If you are using a licensed feature and that license is allowed to expire, Cisco DCNM-SAN shows a license violation, and an orange X is placed through the switch on the Cisco DCNM-SAN map. To clear the license violation message and the orange X, stop the Cisco DCNM-SAN service on the host, and restart it again.

Cisco DCNM Fundamentals Guide, Release 6.x

11-24

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

PA R T

Cisco DCNM for LAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

12

Overview of DCNM-LAN
This chapter provides a brief overview of Cisco Data Center Network Manager for LAN (DCNM-LAN). For information about the specific Cisco Nexus products supported by DCNM-LAN, see the Cisco DCNM Release Notes, Release 5.x. This chapter includes the following sections:

DCNM-LAN Client and Server, page 12-1 Features in Cisco DCNM-LAN, Release 5.2, page 12-2 Documentation About DCNM-LAN, page 12-3

DCNM-LAN Client and Server

DCNM-LAN is a Java-based client-server application. For Java requirements, server system requirements, and client system requirements, see the Cisco DCNM Release Notes, Release 5.x. Figure 12-1 shows the DCNM-LAN client-server environment. The DCNM-LAN client communicates with the DCNM-LAN server only, never directly with managed Cisco NX-OS devices. The DCNM-LAN server uses the XML management interface of Cisco NX-OS devices to manage and monitor them. The XML management interface is a programmatic method based on the NETCONF protocol that complements the command-line interface (CLI) functionality. For more information, see the Cisco NX-OS XML Interface User Guide.
Figure 12-1 DCNM-LAN Client-Server Environment

DCNM Client

DCNM Server

Data Center network

192321

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

12-1

Chapter 12 Features in Cisco DCNM-LAN, Release 5.2

Overview of DCNM-LAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Features in Cisco DCNM-LAN, Release 5.2

Cisco DCNM-LAN Release 5.2 supports the configuration and monitoring of the following Cisco NX-OS features:

Ethernet switching
Physical and virtual ports Port channels and virtual port channels (vPCs) Loopback and management interfaces VLAN network interfaces (sometimes referred to as switched virtual interfaces or SVIs) VLANs and private VLANs (PVLAN) Spanning Tree Protocol, including Rapid Spanning Tree (RST) and Multiple Spanning Tree

Protocol (MST)
Fabric Extender Link-state tracking Serial Over LAN Chassis Internal Network Fibre-Channel-over-Ethernet Initiation Protocol (FIP) snooping Port profiles

Ethernet routing
Gateway Load Balancing Protocol (GLBP), object tracking, and keychain management Hot Standby Router Protocol (HSRP)

Network security
Access control lists IEEE 802.1X Authentication, authorization, and accounting (AAA) Role-based access control Dynamic Host Configuration Protocol (DHCP) snooping Dynamic Address Resolution Protocol (ARP) inspection IP Source Guard Traffic storm control Port security

General
Virtual Device Context Hardware resource utilization with Ternary Content Addressable Memory (TCAM) statistics Switched Port Analyzer (SPAN)

DCNM-LAN includes the following features for assistance with management of your network:

Topology viewer Network servers

Cisco DCNM Fundamentals Guide, Release 6.x

12-2

OL-25174-02OL-25174-02

Chapter 12

Overview of DCNM-LAN Platform Support

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Device groups Event browser Configuration Delivery Management Configuration Change Management Device OS Management Hardware and virtual switch inventory DCNM-LAN server user accounts Device discovery Automatic synchronization with discovered devices Statistical data collection management DCNM-LAN server and client logging DCNM-LAN server cluster administration

DCNM-LAN includes the following administrative features:

Platform Support
DCNM-LAN supports the following platforms:

Cisco Nexus 1000V switches Cisco Nexus 2000 Fabric Extenders Cisco Nexus 3000 Series switches Cisco Nexus 4000 Series switches Cisco Nexus 5000 Series switches Catalyst 6500 DCNM-LAN provides limited support for the Catalyst 6500 Series switches that runs classic IOS version 12.2(33)SXI or higher.
DCNM-LAN supports the viewing of the current configuration attributes of the device. DCNM-LAN does not support changing the configuration of the device. DCNM-LAN supports the Firewall Service Module (FWSM) version 4.0 or higher for the

Catalyst 6500 Series switches.

Cisco Nexus 7000 Series switches

Documentation About DCNM-LAN

The documentation for DCNM-LAN includes several configuration guides and other documents. For more information about the DCNM-LAN documentation, see the Obtaining Documentation and Submitting a Service Request section on page lxviii.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

12-3

Chapter 12 Documentation About DCNM-LAN

Overview of DCNM-LAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

12-4

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

13

Installing and Launching the Cisco DCNM-LAN Client

This chapter describes how to install and launch the Cisco Data Center Network Manager for LAN (DCNM-LAN) client. This chapter includes the following sections:

Information About Installing and Launching the DCNM-LAN Client, page 13-1 Prerequisites for Installing and Launching the DCNM-LAN Client, page 13-2 Secure Client Communications, page 13-2 Default Administrator Credentials, page 13-3 Downloading and Launching the DCNM-LAN Client, page 13-3 Restarting the DCNM-LAN Client, page 13-7 Logging Into the DCNM-LAN Client, page 13-7 Uninstalling the DCNM-LAN Client, page 13-8 Additional References, page 13-9 Feature History for Installing and Launching the DCNM-LAN Client, page 13-10

Information About Installing and Launching the DCNM-LAN Client

The DCNM-LAN client is a Java application. When you finish installing the DCNM-LAN client on your system, the DCNM-LAN client automatically starts. After installing the DCNM-LAN client, whenever you need to restart the DCNM-LAN client, use the DCNM-LAN client software image on your system for the quickest start. If a more recent version of the DCNM-LAN client is available, the DCNM-LAN client automatically downloads that version to your system.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

13-1

Chapter 13 Prerequisites for Installing and Launching the DCNM-LAN Client

Installing and Launching the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Prerequisites for Installing and Launching the DCNM-LAN Client

Installing and using the DCNM-LAN client have the following prerequisites:

Your system must be running a supported operating system to install and use the DCNM-LAN client software. For more information about client system requirements, see the Cisco DCNM Release Notes, Release 5.x, which are available at the following site: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_series_home.html The installation process uses Java version 1.6.0_21. If your system does not have that version of Java, the installation process will install it to your system. The DCNM-LAN client installer requires Internet access to download the Java version 1.6.0_21 JRE. If the system cannot access the Internet, use another system to download the Java installer and copy it to the system that you want to install the DCNM-LAN client on. You can download Java version 1.6.0_21 JRE from the Oracle Technology Network website. If your network environment requires a proxy connection to permit the download of the Java installer, ensure that the proxy settings are configured in Internet Options, available from the Control Panel.

Some DCNM-LAN features require a license. Before you can use licensed features, install the DCNM-LAN license. For more information about licensed features or for more information about the license installation, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Secure Client Communications

By default, communication between the DCNM-LAN client and server is unencrypted; however, you can enable Secure Sockets Layer (SSL) encryption to protect client-server communications. Enabling SSL encryption does not affect how users download, install, and log into the DCNM-LAN client. For information about enabling secure client communication, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Cisco DCNM Fundamentals Guide, Release 6.x

13-2

OL-25174-02OL-25174-02

Chapter 13

Installing and Launching the Cisco DCNM-LAN Client Default Administrator Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Default Administrator Credentials

When you install DCNM-LAN, you specify the default administrator account, which is a DCNM-LAN local user. If you use RADIUS or TACACS+ authentication servers to control access to the DCNM-LAN client, the default administrator account provides you access if no authentication servers for the current authentication mode are reachable. If no one has administrative access to DCNM-LAN, you can reset the local administrator account or change DCNM-LAN server authentication settings by reinstalling the DCNM-LAN server software. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Downloading and Launching the DCNM-LAN Client

The DCNM-LAN client is available from the web server that is included on the DCNM-LAN server. You can download and launch the DCNM-LAN client either by using a web browser or by using a command prompt. When you download and launch the DCNM-LAN client, it automatically saves an image of the software on your local system and starts the DCNM-LAN client. Later on, when you start the DCNM-LAN client, you can quickly start it by using the image on your local system. This section includes the following topics:

Using a Web Browser to Download and Launch the DCNM-LAN Client, page 13-3 Using a Command Prompt to Download and Launch the DCNM-LAN Client, page 13-5 Using a Command Prompt to Download and Launch the DCNM-LAN Client without using Java Web Start Launcher, page 13-6

Using a Web Browser to Download and Launch the DCNM-LAN Client

You can use a web browser to download and launch the DCNM-LAN client.

BEFORE YOU BEGIN

The Java version 1.6.0_21 JRE must be installed on the computer that you want to run the DCNM-LAN client on. The computer that you want to run the DCNM-LAN client on must meet the client system requirements. For details about the client system requirements, see the Cisco DCNM Release Notes, Release 5.x, available at the following site: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_series_home.html

DETAILED STEPS
Step 1

On the computer that you want to use the DCNM-LAN client on, open a web browser and go to the following address: http://server_IP_address_or_DNS_name:web_server_port/dcnm-client/index.html For example, if the DCNM-LAN server IP address is 172.0.2.1 and the web server port is 8080, use the following address:

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

13-3

Chapter 13 Downloading and Launching the DCNM-LAN Client

Installing and Launching the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
http://172.0.2.1:8080/dcnm-client/index.html

The browser shows the DCNM-LAN client page.

Step 2

Click Launch DCNM Client. The DCNM-LAN server sends the dcnm.jnlp file to the browser. This file should be opened with the Java Web Start Launcher.

Step 3

If the browser prompts you, choose to open the dcnm.jnlp file. You do not need to save the file. The DCNM-LAN client installer verifies that Java is already installed on your system. If the installer does not find the supported version of Java on the computer, the installer prompts you to install Java version 1.6.0_21.

Note

The Cisco DCNM client installer requires Internet access to download the Java version 1.6.0_21 JRE. If the system cannot access the Internet, use another system to download the Java installer, copy it to the system that you want to install the Cisco DCNM client on, install Java, and restart the Cisco DCNM client installation. You can download Java version 1.6.0_21 JRE from the Oracle Technology Network website. If your network environment requires a proxy connection to permit the download of the Java installer, ensure that the proxy settings are configured in Internet Options, available from the Control Panel.

Step 4

If the installer prompts you to install Java version 1.6.0_21, follow these steps:
a. b. c.

Click OK to begin installing the supported version of Java. If a security warning notifies you that the Java installer was digitally signed by an expired certificate, click Run to continue the installation. Complete the Java installation wizard.

Tip

To specify whether the supported version of Java is the default version used by browsers installed on the computer, choose Custom setup on the License Agreement dialog box. Later in the Java installation, on the Browser Registration dialog box, you can specify the browsers that should use the Java version that is supported by DCNM-LAN.

The DCNM-LAN client installs on the computer.

Note

You might need to wait a minute or longer while the installer installs the software.

The DCNM-LAN client login window opens. For detailed login steps, see the Logging Into the DCNM-LAN Client section on page 13-7.

Cisco DCNM Fundamentals Guide, Release 6.x

13-4

OL-25174-02OL-25174-02

Chapter 13

Installing and Launching the Cisco DCNM-LAN Client Downloading and Launching the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Using a Command Prompt to Download and Launch the DCNM-LAN Client

You can use a command prompt to download and launch the DCNM-LAN client.

BEFORE YOU BEGIN

The Java version 1.6.0_21 JRE must be installed on the computer that you want to run the DCNM-LAN client on. The computer that you want to run the DCNM-LAN client on must meet the client system requirements. For details about the client system requirements, see the Cisco DCNM Release Notes, Release 5.x, available at the following site: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_series_home.html

DETAILED STEPS
Step 1 Step 2

On the computer that you want to use the DCNM-LAN client on, access a command prompt. Use the cd command to change the directory to the bin directory under the Java version 1.6.0_21 installation directory, as follows: cd path where path is the relative or absolute path to the bin directory. For example, on Microsoft Windows, the default path to the Java version 1.6.0_21 bin directory is C:\Program Files\dcm\Java\jre1.6.0_21\bin.

Step 3

Enter the applicable command as follows:

For Microsoft Windows: javaws.exe server_IP_address_or_DNS_name:web_server_port/dcnm-client/dcnm.jnlp For RHEL: ./javaws server_IP_address_or_DNS_name:web_server_port/dcnm-client/dcnm.jnlp

The Java Web Start Launcher retrieves the dcnm.jnlp file from the DCNM-LAN server and installs the DCNM-LAN client on the computer.

Note

You might need to wait a minute or longer while the installer installs the software.

The DCNM-LAN client login window opens. For detailed login steps, see the Logging Into the DCNM-LAN Client section on page 13-7.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

13-5

Chapter 13 Downloading and Launching the DCNM-LAN Client

Installing and Launching the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Using a Command Prompt to Download and Launch the DCNM-LAN Client without using Java Web Start Launcher
You can use a command prompt to download and launch the DCNM-LAN client in standalone mode without using the Java Web Start Launcher.

BEFORE YOU BEGIN

The Java version 1.6.0_21 JRE must be installed on the computer that you want to run the DCNM-LAN client on. The computer that you want to run the DCNM-LAN client on must meet the client system requirements. For details about the client system requirements, see the Cisco DCNM Release Notes, Release 5.x, available at the following site: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_series_home.html

Note

The Cisco DCNM-SAN cross launch feature is not supported when the DCNM-LAN client is installed in standalone mode. (The DCNM-LAN client in standalone mode is not a Java Web Start application.)

DETAILED STEPS
Step 1

Access a command prompt on the computer where the DCNM-LAN server is installed and navigate to the directory where the DCNM-LAN server is installed.

On a Windows DCNM-LAN server, the DCNM-LAN server is installed in <DCNM_INSTALL_LOCATION>\dcm\dcnm\ui-client directory. The default for <DCNM_INSTALL_LOCATION> is C:\Program Files\Cisco Systems. On a RHEL DCNM-LAN server, the DCNM-LAN server is installed in <DCNM_INSTALL_LOCATION>/dcm/dcnm/ui-client directory. The default for <DCNM_INSTALL_LOCATION> is /usr/cisco. On a Windows DCNM-LAN server, run construct_DCNM_LAN_SA_Client.bat. On a RHEL DCNM-LAN server, run construct_DCNM_LAN_SA_Client.sh.

Step 2

In the ui-client directory, locate and run the construct_DCNM_LAN_SA_Client script.

Step 3 Step 4

Copy the ui-client directory to the computer that you want to run the DCNM-LAN client on. On the computer that you are preparing for the DCNM-LAN client, access a command prompt and set JAVA_HOME to the location where the Java JRE is installed. For example:

For Microsoft Windows: set JAVA_HOME=C:\Program Files\Java\jre1.6.0_21 For RHEL: export JAVA_HOME=/usr/java/jre1.6.0_21

Step 5 Step 6

On the computer that you are preparing for the DCNM-LAN client, navigate to the ui-client directory that was copied from the DCNM-LAN server. In the ui-client directory, locate and run the dcnm-client-sa script to launch the DCNM-LAN client.

On a Windows DCNM-LAN server, run dcnm-client-sa.bat. On a RHEL DCNM-LAN server, run dcnm-client-sa.sh.

Cisco DCNM Fundamentals Guide, Release 6.x

13-6

OL-25174-02OL-25174-02

Chapter 13

Installing and Launching the Cisco DCNM-LAN Client Restarting the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The DCNM-LAN client login window opens. For detailed login steps, see the Logging Into the DCNM-LAN Client section on page 13-7.

Restarting the DCNM-LAN Client

If you have previously downloaded and launched the DCNM-LAN client on a computer, you can later start the DCNM-LAN client by using one of the shortcuts that the installer added to the computer. When you start the DCNM-LAN client, it connects to the DCNM-LAN server and checks if the DCNM-LAN client that is available on the DCNM-LAN server is a newer version than the locally installed DCNM-LAN client. How the DCNM-LAN client starts varies depending upon the result of the version check, as follows:

If the locally installed DCNM-LAN client is the same version as the DCNM-LAN client that is available on the DCNM-LAN server, the DCNM-LAN client window opens quickly. If the locally installed DCNM-LAN client is older than the version of the DCNM-LAN client that is available on the DCNM-LAN server, the DCNM-LAN client automatically downloads from the DCNM-LAN server and replaces the locally installed DCNM-LAN client before the DCNM-LAN client window opens.

For detailed login steps, see the Logging Into the DCNM-LAN Client section on page 13-7.

Logging Into the DCNM-LAN Client

When you log into the DCNM-LAN client, you must specify a valid DCNM-LAN user account.

BEFORE YOU BEGIN

You should know the following information before logging into the DCNM-LAN client:

A valid DCNM-LAN username and password. The IP address or DNS name of the DCNM-LAN server. In a clustered-server deployment, this should be the IP address or DNS name of the master server. The DCNM-LAN server port number. By default, the server port number is 1099. Proxy server address, HTTP port number, and Socks port number, if a proxy server is required by your network environment.

DETAILED STEPS
Step 1

Start the DCNM-LAN client. If you have previously downloaded and launched the DCNM-LAN client on the computer, you can start the client by using one of the shortcuts added to the computer by the client installer. For more information about downloading and launching the client, see one of the following topics:

Using a Web Browser to Download and Launch the DCNM-LAN Client, page 13-3 Using a Command Prompt to Download and Launch the DCNM-LAN Client, page 13-5

The DCNM-LAN client login window opens.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

13-7

Chapter 13 Uninstalling the DCNM-LAN Client

Installing and Launching the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2

In the DCNM-LAN Server field, enter the DNS name or the IP address of the DCNM-LAN server. By default, this field lists the address or name specified the last time the client logged into a server. If you are logging into the client after downloading it, this field lists the address of the server that you downloaded the client from.

Note

If your DCNM-LAN deployment uses a clustered-server environment, enter the DNS name or IP address of the master DCNM-LAN server.

Step 3

In the Username field, enter your DCNM-LAN username. If you are logging into DCNM-LAN for the first time after installing the server, enter the local administrator name that you specified during the server installation. For more information, see the Default Administrator Credentials section on page 13-3. In the Password field, enter the password for the DCNM-LAN username that you specified. (Optional) If you need to change the DCNM-LAN server port, do the following:
a. b.

Step 4 Step 5

If the Port field is not visible, click More >>. Enter the port number in the Port field. The default DCNM-LAN server port number is 1099; however, you can specify a different port number when you install or reinstall the DCNM-LAN server.

Step 6

(Optional) If you need to use a proxy server to connect to the DCNM-LAN server, do the following:
a. b.

If the Connect to the DCNM-LAN server with a proxy server check box is not visible, click More >>. Check Connect to the DCNM-LAN server with a proxy server. The Proxy Server area appears below the check box. In the Address field, enter the IP address of the proxy server. In the HTTP Port and Socks Port fields, enter the port numbers on which the proxy server accepts HTTP and Socks connections. (Optional) If the proxy server requires authentication, check Authentication and enter a valid username and password in the fields provided.

c. d. e. Step 7

Click Login. The DCNM-LAN client opens. For information on how to use the DCNM-LAN client, see Chapter 14, Using the Cisco DCNM-LAN Client.

Uninstalling the DCNM-LAN Client

You can uninstall the DCNM-LAN client from a computer.

DETAILED STEPS
Step 1

Click Start > Control Panel > Java. The Java Control Panel dialog box opens. In the General tab, under Temporary Internet Files, click Settings.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x

13-8

OL-25174-02OL-25174-02

Chapter 13

Installing and Launching the Cisco DCNM-LAN Client Additional References

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The Temporary File Settings dialog box appears.
Step 3

Click View Applications. The Java Application Cache Viewer dialog box opens. Select the DCNM-LAN Client application and click Remove Selected Application. Java uninstalls the DCNM-LAN client image from your computer. Close the Java Application Cache Viewer. On the Temporary File Settings dialog box, click OK. On the Java Control Panel dialog box, click OK. If you want to reinstall the DCNM-LAN client, see the Downloading and Launching the DCNM-LAN Client section on page 13-3.

Step 4

Step 5 Step 6 Step 7 Step 8

Additional References
For additional information related to installing and launching the DCNM-LAN client, see the following sections:

Related Documents, page 13-9 Standards, page 13-9

Related Documents
Related Topic How to use the DCNM-LAN client Starting or stopping a DCNM-LAN server The process of deploying DCNM-LAN in your organization Installing a DCNM-LAN server Document Title Chapter 14, Using the Cisco DCNM-LAN Client Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers Cisco DCNM Installation and Licensing Guide, Release 5.x Cisco DCNM Installation and Licensing Guide, Release 5.x

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

13-9

Chapter 13 Feature History for Installing and Launching the DCNM-LAN Client

Installing and Launching the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Feature History for Installing and Launching the DCNM-LAN Client

Table 13-1 lists the release history for this feature.
Table 13-1 Feature History for Installing and Launching the DCNM-LAN Client

Feature Name Using a command prompt to download the client. Proxy support for the DCNM-LAN client.

Releases 5.0(2) 5.0(2)

Feature Information Support was added for this feature. Support was added for this feature.

Cisco DCNM Fundamentals Guide, Release 6.x

13-10

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

14

Using the Cisco DCNM-LAN Client

This chapter describes the user interface of the Cisco Data Center Network Manager for LAN (DCNM-LAN) client and how to use common features. This chapter includes the following sections:

Information About the DCNM-LAN Client, page 14-1 Opening the DCNM-LAN Client, page 14-8 Closing the DCNM-LAN Client, page 14-9 Deploying Changes, page 14-10 Working with Statistics and Charts, page 14-10 Configuring Global Preferences, page 14-15 Using Online Help, page 14-18 Additional References, page 14-18 Feature History for Using the DCNM-LAN Client, page 14-19

Information About the DCNM-LAN Client

This section describes the DCNM-LAN client and its parts. This section includes the following topics:

User Interface, page 14-2 Feature Selector Pane, page 14-2 Contents Pane, page 14-3 Summary Pane, page 14-3 Details Pane, page 14-3 Association Pane, page 14-4 Menus, page 14-5 Toolbars, page 14-6 Keyboard Commands, page 14-7 Multiple Platform Support, page 14-7

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

14-1

Chapter 14 Information About the DCNM-LAN Client

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

User Interface
The DCNM-LAN client user interface, shown in Figure 14-1, presents device status information and provides configuration tools that allow you to manage devices. It is divided into the panes shown in Figure 14-1. When you want to view information about a specific object in a managed device or want to perform a configuration task, you use the panes in the order shown in Figure 14-1.
Figure 14-1 DCNM-LAN Client User Interface

1 2

Feature Selector pane Contents pane

3 4

Summary pane Details pane

Feature Selector Pane

The Feature Selector pane, shown in Figure 14-1, allows you to see features grouped by categories and to choose the feature that you want to use or configure. The bottom section of the Feature Selector pane displays buttons for feature categories. When you choose a category, the top section of the Feature Selector pane displays a tree of features within the chosen category. In Figure 14-1, the Interfaces category is chosen, so the tree shows features that allow you to configure the interfaces of managed devices. The documentation and online help for DCNM-LAN includes many procedures that begin with choosing the applicable feature from the Feature Selector pane. For example, a procedure about configuring an Ethernet interface would start with the following step: From the Feature Selector pane, choose Interfaces > Physical > Ethernet. After you choose a feature on the tree, the Contents pane displays information about the feature.

Cisco DCNM Fundamentals Guide, Release 6.x

14-2

OL-25174-02OL-25174-02

Chapter 14

Using the Cisco DCNM-LAN Client Information About the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Contents Pane
The Contents pane, shown in Figure 14-1, displays information about the currently selected feature and provides fields for configuring that feature. The Contents pane contains two smaller panes: the Summary pane and the Details pane.

Summary Pane
The Summary pane, shown in Figure 14-1, displays an organized set of objects that you can view information about or perform actions on. The type of objects that appear depends upon the currently selected feature. For example, if you choose Interfaces > Physical > Ethernet from the Feature Selector pane, the Summary pane shows a table of devices. You can expand the managed devices to view the slots that contain network interface cards. You can expand the slots to view the interfaces they contain and key information about the status of the interfaces, such as the port mode, administrative status, and operational status. For most features, the title bar for the Summary pane shows what you have selected. After you choose the object that you want to view or configure, the Details pane displays information about the selected object, such as an Ethernet interface.
Exporting the Summary Pane

You can export the data shown in the Summary pane to a spreadsheet in Microsoft Excel 97-2003 format. To do so, click the green arrow in the upper-right corner of the Summary pane and specify the filename and location for the spreadsheet.
Filtering the Summary Pane

For many features, you can filter the objects that appear in the Summary pane. If filtering is supported for the feature that you selected, you can enable filtering from the menu bar by choosing View > Filter. In the Summary pane, the columns that you can use to filter the objects become drop-down lists. To filter the Summary pane, use the drop-down column heading lists to limit the objects that appear.

Details Pane
The Details pane, shown in Figure 14-1, shows information and configuration fields that are specific to the object that you selected in the Summary pane. The Details tab is often further divided into tabs. You can click on a tab to view its contents. This section includes the following topics:

Tabs, page 14-3 Sections, page 14-4

Tabs
Tabs organize related fields and information. For example, as shown in Figure 14-1, when you select an Ethernet interface, four tabs appear in the Details pane, such as the Port Details tab. The following two special tabs often appear in the Details pane for many of the types of objects that you can choose from the Summary pane:

StatisticsYou can use this tab to work with statistics and charts related to the selected object. For more information, see the Working with Statistics and Charts section on page 14-10.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02OL-25174-02

14-3

Chapter 14 Information About the DCNM-LAN Client

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

EventsYou can use this tab to view feature-specific events about the selected object. For more information, see the System Management Configuration Guide, Cisco DCNM for LAN, Release 5.x.

Sections
Sections provide further organization of related fields and information. The DCNM-LAN client allows you to expand and collapse sections so that you can show or hide fields and information as needed. For example, as shown in Figure 14-1, on the Port Details tab, the Basic Settings section is expanded but the Port Mode Settings section is collapsed.

Association Pane
The DCNM-LAN client also includes the Association pane, which allows you to access objects that you have configured in features that are associated with the currently selected feature. Figure 14-2 shows the Association pane. When tabs appear on the right side of the DCNM-LAN client, you can click on them to access the Association pane. For example, as shown in Figure 14-2, if you are configuring an Ethernet interface, you can use the Association pane to access the IPv4 ACLs that you can apply to the interface. If you right-click on an IPv4 ACL in the Association pane, you can choose to apply the ACL to the interface or to go to the IPv4 ACLs feature and configure the ACL.
Figure 14-2 Association Pane

Association pane

Cisco DCNM Fundamentals Guide, Release 6.x

14-4

OL-25174-02OL-25174-02

Chapter 14

Using the Cisco DCNM-LAN Client Information About the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Menus
The menu bar in the DCNM-LAN client includes the following standard menus that appear:

File Menu

NewAllows you to create new objects. The types of objects that you can create depends upon the currently selected feature. In some cases, the object selected in the Summary pane also affects what you can create. DeploySaves your changes to the DCNM-LAN server and deploys configuration changes to managed devices. ExitCloses the DCNM-LAN client.

View Menu

ToolbarsAllows you to show or hide the toolbars that are available for the currently selected feature. For more information, see the Toolbars section on page 14-6. RefreshForces the DCNM-LAN client to retrieve updated information from the DCNM-LAN server. FilterEnables or disables the filtering option for the Summary pane.

Tools Menu

PreferencesOpens the Global Preferences dialog box. For more information, see the Configuring Global Preferences section on page 14-15. DebugOpens the DCNM-LAN Client Logging dialog box, which allows you to configure the logging level for the DCNM-LAN client.

Note

We recommend that you use the default client logging level unless you are troubleshooting a specific problem or are asked to change client logging levels by the Cisco technical support staff.

Go Menu

TopologySelects the Topology button on the Feature Selector pane. InventorySelects the Inventory button on the Feature Selector pane. Virtual DevicesSelects the Virtual Devices button on the Feature Selector pane. InterfacesSelects the Interfaces button on the Feature Selector pane. SwitchingSelects the Switching button on the Feature Selector pane. FCoESelects the FCoE button on the Feature Selector pane. RoutingSelects the Routing button on the Feature Selector pane. SecuritySelects the Security button on the Feature Selector pane. Configuration Change ManagementSelects the Configuration Change Management button on the Feature Selector pane. Device OS ManagementSelects the Device OS Management button on the Feature Selector pane.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02OL-25174-02

14-5

Chapter 14 Information About the DCNM-LAN Client

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Configuration Delivery ManagementSelects the Configuration Delivery Management button on the Feature Selector pane. DCNM-LAN Server AdministrationSelects the DCNM-LAN Server Administration button on the Feature Selector pane. Network ServersSelects the Network Servers button on the Feature Selector pane. Event BrowserSelects the Event Browser button on the Feature Selector pane.

Actions Menu
The items on the Actions menu reflect what you can do, depending upon the feature you are using and the object that is selected in the Summary pane. For some features, such as Inventory, the Actions menu does not appear in the menu bar.

Help Menu

Help ContentsOpens the online help system to the Welcome page. Context HelpOpens the online help system to a page that applies to the feature currently selected in the Feature Selector pane. Show DCNM-LAN Instance IDOpens a dialog box that displays the license ID for your DCNM-LAN server. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. View LicensesOpens a dialog box that displays information about license files currently installed with your DCNM-LAN server. About Data Center Network ManagerOpens a dialog box that displays information about your DCNM-LAN server, including the software version and implementation version.

Toolbars
The DCNM-LAN client provides several standard toolbars plus additional, feature-specific toolbars that are available only when you have selected the applicable feature. The following table lists actions that you can take to configure toolbars. Action Show or hide a toolbar Rearrange toolbars Float a toolbar Control whether a toolbar can be hidden, rearranged, or floated How To Right-click on the toolbar area and then choose the toolbar that you want to show or hide. On a toolbar that you want to move, click on the left end of the toolbar and drag it to where you want it. On the toolbar that you want to float, click on the left end of the toolbar and drag it off of the toolbar area. Right-click on the toolbar area and then choose the option that you want to control.

Cisco DCNM Fundamentals Guide, Release 6.x

14-6

OL-25174-02OL-25174-02

Chapter 14

Using the Cisco DCNM-LAN Client Information About the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Keyboard Commands
You can use the keyboard to perform many of the commands that you can perform with menu items or toolbars. The menus show the keyboard equivalent of most menu items. For example, the following list shows some common menu items and the matching keyboard command:

DeployCtrl + S RefreshF5 FilterCtrl + F Online helpF1 ExitCtrl + Q

Multiple Platform Support

DCNM-LAN supports several types of Cisco Nexus platforms; however, some of the features supported in DCNM-LAN are not supported or applicable to all platforms. This section describes how DCNM-LAN handles unsupported features in the user interface.

Unsupported FeaturesIf a platform does not support a particular feature, the platform is not displayed for that feature. For example, if you choose Security > Access Control > Time-range from the Feature Selector pane, the Summary pane displays only the platform types that support the Time-range feature. In this case, the Cisco Nexus 1000V does not support this feature, so any managed Cisco Nexus 1000V platforms are not displayed in the Summary pane. Similarly, the Time-range association pane does not include any Cisco Nexus 1000V platforms.

Unsupported AttributesSometimes a platform supports a feature, but does not support a particular attribute in that feature. In this case, the attribute is grayed-out or a N/A (Not Applicable) value is displayed in the field or cell. If all attributes grouped in a particular section are not supported, N/A is added to the section title, and DCNM-LAN does not allow you to expand the section. If all attributes in a tab are not supported for a particular platform, the tab is displayed, but if you click on it, a message appears stating that the attribute is not supported.

Unsupported ChartsIf a platform does not support some attributes in a chart, DCNM-LAN grays out those attributes. If a platform does not support any attributes in a chart, when you select the chart, DCNM-LAN displays a message stating that the chart is not supported. Unsupported OptionsIf a platform does not support an option, the option is not displayed, for example, in drop-down lists. Unsupported Operations If a platform does not support an option for a specific operation on a context or toolbar menu, the option is grayed-out.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02OL-25174-02

14-7

Chapter 14 Opening the DCNM-LAN Client

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Opening the DCNM-LAN Client

You can open the DCNM-LAN client after you have installed the DCNM-LAN client on the computer that you are using.

BEFORE YOU BEGIN

Install the DCNM-LAN client on the computer that you are using. For more information about installing the DCNM-LAN client, see Chapter 13, Installing and Launching the Cisco DCNM-LAN Client.

DETAILED STEPS
Step 1

From the start menu, choose All Programs > Cisco DCNM Client > Cisco DCNM LAN.

Note

If the DCNM-LAN client is not available on the All Programs menu, you can launch the DCNM-LAN client from the DCNM-LAN server website. For more information, see Chapter 13, Installing and Launching the Cisco DCNM-LAN Client.

A dialog box displays login fields.

Step 2

In the DCNM Server field, enter the IP address or hostname of the DCNM-LAN server. You can use the hostname only if your DNS server has an entry for the DCNM-LAN server hostname. If you have previously logged into the server with the current client installation, you may be able to choose the IP address or hostname from the drop-down list.

Note

If your DCNM-LAN deployment uses a clustered-server environment, enter the DNS name or IP address of the master DCNM-LAN server.

Step 3 Step 4 Step 5

In the Username field, enter the name of the DCNM-LAN server user account that you want to use to access the DCNM-LAN client. In the Password field, enter the password for the user account that you specified. (Optional) If you need to change the DCNM-LAN server port, do the following:
a. b.

If the Port field is not visible, click More >>. Enter the port number in the Port field. The default DCNM-LAN server port number is 1099; however, you can specify a different port number when you install or reinstall the DCNM-LAN server.

Step 6

(Optional) If you need to use a proxy server to connect to the DCNM-LAN server, do the following:
a. b.

If the Connect to the DCNM-LAN server with a proxy server check box is not visible, click More >>. Check Connect to the DCNM server with a proxy server. The Proxy Server area appears below the check box. In the Address field, enter the IP address of the proxy server. In the HTTP Port and Socks Port fields, enter the port numbers on which the proxy server accepts HTTP and Socks connections.

c. d.

Cisco DCNM Fundamentals Guide, Release 6.x

14-8

OL-25174-02OL-25174-02

Chapter 14

Using the Cisco DCNM-LAN Client Closing the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
e. Step 7

(Optional) If the proxy server requires authentication, check Authentication and enter a valid username and password in the fields provided.

Click Login. The DCNM-LAN client user interface appears. If a dialog box displays a message about device credentials, you have not configured device credentials for the user account that you specified.

Step 8

If a dialog box shows a message that your device credentials are not set, do one of the following:

If you want to set device credentials now, click Yes. If you do not want to set device credentials now, click No.

Note

For information about setting device credentials, see the Administering Devices and Credentials section on page 17-1.

Closing the DCNM-LAN Client

You can close the DCNM-LAN client when you are done using it.

DETAILED STEPS
Step 1

From the menu bar, choose File > Exit. A dialog box displays a confirmation message. (Optional) If you have not deployed your changes, do one of the following:

Step 2

If you want to save your changes, including deploying configuration changes to managed devices, check Save pending changes. If you want to discard your changes, uncheck Save pending changes.

Step 3

Click Yes. If you started any statistical data collection processes during the DCNM-LAN client session, a dialog box displays the collection processes.

Step 4

If a dialog box displays the statistical data collection processes that you started, do the following:
a.

Decide which statistical collection processes that you want to stop.

Note

We recommend that you stop any unnecessary statistical collection processes when you log out of the DCNM-LAN client.

b. c.

Check the collection processes that you want to stop. If you want to stop all of your collection processes, click Select All. Click Ok.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02OL-25174-02

14-9

Chapter 14 Deploying Changes

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Deploying Changes
When you use the DCNM-LAN client to make configuration changes to managed devices or to the DCNM-LAN server, you may need to deploy the changes or the DCNM-LAN client may deploy them automatically, depending upon what changes you have made.

Automatic deploymentIf the DCNM-LAN client deploys a change automatically, the Deploying configuration message appears briefly. For example, if you delete an access rule from an ACL, the DCNM-LAN client immediately deploys this configuration change to the managed device that has the ACL. Manual deploymentIf the DCNM-LAN client is storing a configuration change, on the toolbar, the Deploy button is available. For example, if you change the sequence number of an access rule of an ACL, the DCNM-LAN client stores this configuration change until you manually deploy it to the managed device that has the ACL. To remind you of the necessity to deploy changes that the DCNM-LAN client is storing, the procedures in the DCNM-LAN documentation set include a deployment step.

Deploying server changes saves your changes on the DCNM-LAN server. For example, if you add a DCNM-LAN server user account, deploying your changes adds the user account to the DCNM-LAN server and does not affect managed devices. Deploying configuration changes to a managed device causes the DCNM-LAN server to update the running configuration of the device.

Note

DCNM-LAN does not update the startup configuration of a managed device. When you want to replace the startup configuration of a managed device with the running configuration, you can log into the command-line interface of the device and copy the running configuration to the startup configuration. When you close the DCNM-LAN client and you have not deployed your changes, you can deploy them without canceling the process of closing the DCNM-LAN client. For more information, see the Closing the DCNM-LAN Client section on page 14-9.

Working with Statistics and Charts

This section describes how to use the statistical charts available on a Statistics tab. This section includes the following topics:

Information about Statistics and Charts, page 14-11 Licensing Requirements for Statistics and Charts, page 14-11 Accessing a Chart, page 14-11 Starting Statistical Monitoring for a Chart, page 14-12 Stopping Statistical Monitoring for a Chart, page 14-12 Using a Chart, page 14-13 Using an Overview Chart, page 14-14 Exporting a Chart, page 14-15

Cisco DCNM Fundamentals Guide, Release 6.x

14-10

OL-25174-02OL-25174-02

Chapter 14

Using the Cisco DCNM-LAN Client Working with Statistics and Charts

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Information about Statistics and Charts

You can use a Statistics tab to start and stop statistical monitoring for an object and to work with charts of statistical data about the selected object. For each chart, the DCNM-LAN client also provides overview charts, which allow you to see historical trends and to control the time scale of the standard chart. When you start monitoring for a new chart, DCNM-LAN creates a new statistical collection process that appears in the Statistical Data Collection feature. For more information, see the Administering Statistical Data Collection section on page 25-1.

Licensing Requirements for Statistics and Charts

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement Real-time monitoring requires no license. Cisco DCNM-LAN requires a LAN Enterprise license for the following features:

Maintaining a history of statistical data Using overview charts

For information about obtaining and installing a Cisco DCNM-LAN LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Accessing a Chart
You can access any chart. The charts that are available for a particular Statistics tab depend upon the feature and object selected.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose the feature for which you want to use a statistical chart. For example, choose Interfaces > Physical > Ethernet. From the Summary pane, select an object. The Statistics tab appears in the Details pane.

Step 2

Note

If no Statistics tab appears, DCNM-LAN does not provide a statistical chart for the object that you selected.

Step 3

Click the Statistics tab. In the Statistics tab, one or more charts may appear.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02OL-25174-02

14-11

Chapter 14 Working with Statistics and Charts

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

A dialog box may appear to confirm if you want to view charts for statistical collections that DCNM-LAN is running for the object that you selected in the Summary pane. For more information, see the Configuring Monitoring Preferences section on page 14-16.

Step 4 Step 5

If the chart for the data that you want to monitor does not appear, from the toolbar, choose New Chart and then choose the chart that you want. Click the title bar of the chart that you want to work with. The chart status appears in the lower left corner of the chart pane. If the chart is not active, you must start statistical monitoring for the chart before you can use it. For more information, see the Starting Statistical Monitoring for a Chart section on page 14-12.

Starting Statistical Monitoring for a Chart

You can start statistical monitoring for a chart in the Statistics tab for any of the device configuration features that support statistical monitoring.

Note

Each time that you start monitoring for a new chart, DCNM-LAN creates a new statistical collection process that appears in the Statistical Data Collection feature.

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4

Access the chart for which you want to start statistical monitoring. For more information, see the Accessing a Chart section on page 14-11. From the chart pane, click Select Parameters, check at least one statistical parameter that you want to appear in the chart, and click Select Parameters again. From the Monitor toolbar, choose the icon to start the collection process. The chart starts graphing the selected parameters.

Note

When you close the DCNM-LAN client without stopping the statistical collection processes that you started, a dialog box prompts you to decide whether to stop the statistical collections or let them continue. We recommend that you stop any unnecessary statistical collection processes when you log out of the DCNM-LAN client.

Stopping Statistical Monitoring for a Chart

You can stop statistical monitoring for a chart in the Statistics tab.

Note

When you stop monitoring for a chart, DCNM-LAN stops the corresponding statistical collection process that appears in the Statistical Data Collection feature.

Cisco DCNM Fundamentals Guide, Release 6.x

14-12

OL-25174-02OL-25174-02

Chapter 14

Using the Cisco DCNM-LAN Client Working with Statistics and Charts

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1 Step 2

Access the chart for which you want to stop statistical monitoring. For more information, see the Accessing a Chart section on page 14-11. From the Monitor toolbar choose the icon.

Note

If the chart that you want to stop does not appear, use the Statistical Data Collection feature to stop the collection process. For more information, see the Starting Statistical Monitoring for a Chart section on page 14-12.

Using a Chart
The DCNM-LAN client provides the following options for using a chart:

Changing parameters Setting the charting frequency Controlling the magnification of the chart data Showing, moving, and hiding threshold lines Tearing the chart away from the DCNM-LAN client window

This procedure provides basic instructions for using each of these options.

Note

For information about using an overview chart, see the Using an Overview Chart section on page 14-14.

DETAILED STEPS
Step 1 Step 2 Step 3 Step 4 Step 5

Access the chart that you want to use. For more information, see the Accessing a Chart section on page 14-11. If the chart is not active, you must start statistical monitoring for the chart before you can use it. For more information, see the Starting Statistical Monitoring for a Chart section on page 14-12. (Optional) To change parameters, click Select Parameters, check the statistics parameters that you want to collect, and click Select Parameters again. (Optional) To set the frequency with which DCNM-LAN retrieves statistical data for the selected object, from the Select Frequency drop-down list on the Monitor toolbar, choose the new frequency. (Optional) To control the magnification, or zoom, of the chart, do one of the following:

To zoom in on a portion of the chart, position the mouse pointer at one end of the portion, click and hold the left mouse button, drag the mouse pointer to the other end of the portion, and release the mouse button. To zoom in on a portion of the chart, position the mouse pointer at one end of the portion and then click and drag the mouse pointer to the other end of the portion. To change to the previous zoom, click the icon.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02OL-25174-02

14-13

Chapter 14 Working with Statistics and Charts

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 6

To change to the next zoom, click the

icon. icon. icon.

To reset the zoom to the default magnification, click the

(Optional) To show, move, or hide threshold lines, do one of the following:

To show or hide threshold lines, on the Monitor toolbar, click the To move the lower threshold line, click and drag the To move the lower threshold line, click and drag the icon. icon.

Step 7

(Optional) To tear the chart away from the DCNM-LAN client window, click on the red line that appears below the chart title.

Using an Overview Chart

You can use an overview chart to view the historical trend of the statistical data of the current chart and to set the time scale of the standard chart.

BEFORE YOU BEGIN

Ensure that any device with data that you want to view on an overview chart is included on the list of DCNM-LAN-licensed devices. For more information, see the Licensing Requirements for Statistics and Charts section on page 14-11.

DETAILED STEPS
Step 1 Step 2

Access the chart that contains the overview chart that you want to use. For more information, see the Accessing a Chart section on page 14-11. If the chart is not active, you must start statistical monitoring for the chart before you can use its overview chart. For more information, see the Starting Statistical Monitoring for a Chart section on page 14-12. Click Show Overview Chart. In a new window, the overview chart displays the historical trends of the charted data. To set the time scale of the chart, at the bottom of the overview chart window, click the desired time scale button. The time scale buttons are as follows:

Step 3

Step 4

RTReal time 1dOne day 2dTwo days 5dFive days 15dFifteen days 1mOne month 3mThree months

Step 5

To close the overview chart, click Show Overview Chart again.

Cisco DCNM Fundamentals Guide, Release 6.x

14-14

OL-25174-02OL-25174-02

Chapter 14

Using the Cisco DCNM-LAN Client Configuring Global Preferences

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Exporting a Chart
You can export a chart as a JPG image or as a comma-separated value (CSV) file. When you export a chart as a JPG image, the image is of the chart as it appears when you export the image. When you export a chart as a CSV file, the file contains all data from the statistical collection for the chart.

DETAILED STEPS
Step 1 Step 2

Access the chart that you want to use. For more information, see the Accessing a Chart section on page 14-11. If the chart is not active, you must start statistical monitoring for the chart before you can export an image of it. For more information, see the Starting Statistical Monitoring for a Chart section on page 14-12. If you want to export an image, configure the chart to show the data that you want to appear in the image. For more information, see the Using a Chart section on page 14-13. Right-click on the chart. Choose one of the following:

Step 3 Step 4 Step 5

Export as CSV Export as JPG

Step 6

Specify the location and filename, and then click Save. The DCNM-LAN client exports the chart in the file format that you specified.

Configuring Global Preferences

Using the Global Preferences dialog box, you can configure several preferences for how the DCNM-LAN client displays data and fields. The sections on the Global Preferences are as follows:

MonitoringControls the default frequency of statistical data retrieval from managed devices and whether statistical charts open automatically. For more information, see the Configuring Monitoring Preferences section on page 14-16. EventsControls the maximum age of events that the DCNM-LAN client fetches from the DCNM-LAN server when you start the DCNM-LAN client. For more information, see the Configuring the Maximum Age of Events Fetched from the Server section on page 14-16. Pre ProvisionControls whether the DCNM-LAN client displays some settings only when other settings are made or whether the DCNM-LAN client always displays all settings. For more information, see the Configuring Preprovisioning section on page 14-17.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02OL-25174-02

14-15

Chapter 14 Configuring Global Preferences

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Configuring Monitoring Preferences

You can configure the default frequency for statistical data retrieval from monitored devices. The default frequency for statistical data retrieval is 30 seconds. This frequency determines the initial data retrieval frequency for a new chart. Users can override the default frequency by configuring the chart-specific setting. You can also configure whether the DCNM-LAN client automatically opens statistical charts when you access the Statistics tab of an object for which DCNM-LAN is already collecting statistical data.

BEFORE YOU BEGIN

Determine how often you want DCNM-LAN to retrieve statistical data by default. Consider how important it is to your organization that charts update frequently. If very current charting data is important to your organization, consider using a short data retrieval frequency.

DETAILED STEPS
Step 1

From the menu bar, choose Tools > Preferences. The Global Preferences dialog box appears. Under Monitoring, the Default Monitoring Frequency drop-down list displays the current frequency for statistical data retrieval. The default polling frequency is 30 seconds. If you want to configure the default frequency of statistical data retrieval, from the Default Monitoring Frequency drop-down list, choose the new data retrieval frequency. If you want to configure the default behavior when you access the Statistics tab of an object for which DCNM-LAN is already collecting statistical data, do one of the following:

Step 2 Step 3

If you want the client to show charts without asking for confirmation, check the Load history charts by default check box. If you want the client to prompt you for confirmation before it opens statistical charts, uncheck the Load history charts by default check box.

Step 4

Click Ok.

Configuring the Maximum Age of Events Fetched from the Server

You can configure the maximum age of events that the DCNM-LAN client fetches from the DCNM-LAN server when you start the DCNM-LAN client. This setting affects how old the events are that the DCNM-LAN client displays in the Event Browser and on feature-specific Events tabs. By default, the DCNM-LAN client fetches events that occurred up to 1 hour prior to the DCNM-LAN client startup. You can configure the DCNM-LAN client to fetch events that are up to 24 hours old.

DETAILED STEPS
Step 1

From the menu bar, choose Tools > Preferences. The Global Preferences dialog box appears. Under Events, the Fetch events before drop-down list displays the current maximum age of events.

Cisco DCNM Fundamentals Guide, Release 6.x

14-16

OL-25174-02OL-25174-02

Chapter 14

Using the Cisco DCNM-LAN Client Configuring Global Preferences

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2

From the Fetch events before drop-down list, choose the new maximum age of events.

Note

To prevent the DCNM-LAN client from fetching any old events, choose zero (0) hours as the maximum age of events. When you choose zero hours, the DCNM-LAN client shows only the events that the DCNM-LAN server receives after you start the DCNM-LAN client.

Step 3

Click Ok.

Configuring Preprovisioning
Preprovisioning refers to configuring a managed device with settings for modes or protocols that are not enabled. The preprovisioning preference affects the following sections of the DCNM-LAN client interface:

Interfaces > Physical > Ethernet > Device > Slot > Interface, Port Details tab, Port Mode Settings section When you enable preprovisioning, the DCNM-LAN client displays all port mode fields regardless of the setting in the Mode drop-down list. When you disable preprovisioning, the DCNM-LAN client displays only the port mode settings that are relevant to the currently selected port mode. For example, if preprovisioning is disabled and you choose Trunk from the Mode drop-down list, the DCNM-LAN client displays only the Trunk settings and hides the Access, PVLAN Host, and PVLAN Promiscuous fields. Additionally, the dialog boxes for configuring the Access VLAN field and the Native VLAN field include the Create in the Device check box. When you enable preprovisioning, you can uncheck this check box if you want DCNM-LAN to configure the device to refer to a VLAN that is not currently configured. When you disable preprovisioning, this check box is always checked and DCNM-LAN creates the VLAN specified, if it does not already exist.

Switching > Spanning Tree > Device, Configuration tab, Global Settings section When you enable preprovisioning, the DCNM-LAN client displays MST settings regardless of the settings in the Protocol drop-down list. When you disable preprovisioning, the DCNM-LAN client displays the MST Setting fields unless you choose MST from the Protocol drop-down list.

DETAILED STEPS
Step 1

From the menu bar, choose Tools > Preferences. The Global Preferences dialog box appears. Under Pre Provision, the Pre Provision check box appears. Do one of the following:

Step 2

If you want to enable preprovisioning, ensure that the Pre Provision check box is checked. If you want to disable preprovisioning, ensure that the Pre Provision check box is unchecked.

Step 3

Click Ok.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02OL-25174-02

14-17

Chapter 14 Using Online Help

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Using Online Help

Online help has the following features:

ContentsThe organization of DCNM-LAN online help is shown in the Contents tab of the online help window. When a topic has subtopics, the book icon appears to the left of the topic in the contents. You can expand and collapse individual topics in the contents. You can also collapse or expand all topics.

IndexDCNM-LAN online help includes an index, which allows you to look up subjects alphabetically and open related topics directly from the index. FavoritesDCNM-LAN online help allows you to add specific topics to the Favorites tab. Favorites are stored locally on the computer that you use to access online help.

To access the welcome page in online help, from the menu bar, choose Help > Help Contents. DCNM-LAN online help includes context-sensitive help. To access context-sensitive help for a feature, follow these steps:
Step 1 Step 2

Select a specific feature from the Feature Selector pane in the DCNM-LAN client. For example, choose Security > Access Control > IPv4 ACL. Do one of the following:

Press F1. From the toolbar, click the question mark icon.

Online help for the selected feature appears in a browser window. DCNM-LAN uses the default browser application on the computer that runs the DCNM-LAN client.

Additional References
For additional information related to using the DCNM-LAN client, see the following sections:

Related Documents, page 14-18 Standards, page 14-19

Related Documents
Related Topic Installing and launching the DCNM-LAN client Document Title Chapter 13, Installing and Launching the Cisco DCNM-LAN Client

Information about using specific DCNM-LAN features Obtaining Documentation and Submitting a Service Request, page lxviii

Cisco DCNM Fundamentals Guide, Release 6.x

14-18

OL-25174-02OL-25174-02

Chapter 14

Using the Cisco DCNM-LAN Client Feature History for Using the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Feature History for Using the DCNM-LAN Client

Table 14-1 lists the release history for this feature.
Table 14-1 Feature History for Installing and Launching the DCNM-LAN Client

Feature Name Global preferences Multiple platform support

Releases 5.0(2) 5.0(2)

Feature Information Support was added for the Load history charts by default check box. Information was added about how the DCNM-LAN client supports management of different Cisco NX-OS device types.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02OL-25174-02

14-19

Chapter 14 Feature History for Using the DCNM-LAN Client

Using the Cisco DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

14-20

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

15

Administering DCNM-LAN Authentication Settings

This chapter describes how to administer Cisco Data Center Network Manager for LAN (DCNM-LAN) authentication settings. This chapter includes the following sections:

Information About Administering DCNM-LAN Authentication Settings, page 15-1 Licensing Requirements for Administering DCNM-LAN Authentication Settings, page 15-4 Prerequisites for Administering DCNM-LAN Authentication Settings, page 15-4 Guidelines and Limitations for Administering DCNM-LAN Authentication Settings, page 15-5 Configuring DCNM-LAN Authentication Settings, page 15-5 Viewing DCNM-LAN Local Users, page 15-12 Verifying Authentication Server Settings, page 15-12 Field Descriptions for DCNM-LAN Authentication Settings, page 15-13 Additional References, page 15-14 Feature History for DCNM-LAN Authentication Settings, page 15-15

Information About Administering DCNM-LAN Authentication Settings

DCNM-LAN authentication settings determine how a DCNM-LAN server authenticates users who attempt to access the server with the DCNM-LAN client. They also determine the user role for the user, which affects what the user can configure in the DCNM-LAN client. This section contains the following topics:

Users and User Roles, page 15-2 Local Authentication and DCNM-LAN Local Users, page 15-2 RADIUS and TACACS+ Authentication, page 15-2 User Role Assignment by RADIUS and TACACS+, page 15-3 Fallback to Local Authentication, page 15-3 Password Recovery, page 15-3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

15-1

Chapter 15 Information About Administering DCNM-LAN Authentication Settings

Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Users and Device Credentials, page 15-4 Virtualization Support, page 15-4

Users and User Roles

DCNM-LAN implements user-based access to allow you to control who can access a DCNM-LAN server by using the DCNM-LAN client. User access is secured by a password. DCNM-LAN supports strong passwords. When you ensure that each person who accesses DCNM-LAN has a unique user account, user-based access allows you to determine what actions are taken by each user. In addition, DCNM-LAN allows you to assign a role to each user. Roles determine what actions a user can take in the DCNM-LAN client. As described in Table 15-1, DCNM-LAN supports two user roles.
Table 15-1 DCNM-LAN User Roles

DCNM-LAN Role User

Description

Cannot change DCNM-LAN authentication mode Cannot add or delete DCNM-LAN local user accounts Can change the details of its own local user account Can use all other features Has full control of DCNM-LAN authentication settings Can use all other features

Administrator

Local Authentication and DCNM-LAN Local Users

The DCNM-LAN database contains any DCNM-LAN local users that you create.

Note

DCNM-LAN server users are local to the DCNM-LAN server. Creating, changing, and removing DCNM-LAN server users has no effect on user accounts on managed devices. A DCNM-LAN server uses local users to grant access in the following cases:

When the authentication mode is local When no authentication server for the current authentication mode is reachable.

You can use local authentication as the primary authentication mode. If you specify RADIUS or TACACS+ as the primary authentication mode, the DCNM-LAN server always falls back to local authentication if no authentication server for the current authentication mode is reachable.

RADIUS and TACACS+ Authentication

You can configure DCNM-LAN to authenticate users with either the RADIUS or TACACS+ AAA protocol.

Cisco DCNM Fundamentals Guide, Release 6.x

15-2

OL-25174-02OL-25174-02

Chapter 15

Administering DCNM-LAN Authentication Settings Information About Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DCNM-LAN supports primary, secondary, and tertiary authentication servers for RADIUS and TACACS+. Only a primary server is required. For each authentication server, you can specify the port number that the server listens to for authentication requests. During authentication, if the primary server for the current authentication mode does not respond to the authentication request, the DCNM-LAN server sends the authentication request to the secondary server. If the secondary server does not respond, DCNM-LAN sends the authentication request to the tertiary server. If none of the servers configured for the current authentication mode responds to an authentication request, the DCNM-LAN server falls back to local authentication.

User Role Assignment by RADIUS and TACACS+

DCNM-LAN supports the assignment of a user role by the RADIUS or TACACS+ server that grants a user access to the DCNM-LAN client. The user role assigned to a user is in effect for the current session in the DCNM-LAN client only. To assign a DCNM-LAN user role by RADIUS, configure the RADIUS server to return the RADIUS vendor-specific attribute 26/9/1, which is the Cisco-AV-Pair attribute. To assign a DCNM-LAN user role by TACACS+, the TACACS+ server must return a cisco-av-pair attribute-value pair. If an authentication response does not assign the user role, DCNM-LAN assigns the User role. Table 15-2 shows the supported attribute-value pair values for each DCNM-LAN user role.
Table 15-2 DCNM-LAN User Role Assignment Values

DCNM-LAN Role User Administrator

RADIUS Cisco-AV-Pair Value

shell:roles = "network-operator" shell:roles = "network-admin"

TACACS+ Shell cisco-av-pair Value

cisco-av-pair=shell:roles="network-operator" cisco-av-pair=shell:roles="network-admin"

Fallback to Local Authentication

Local authentication always is the fallback method for RADIUS and TACACS+ authentication modes. If none of the servers configured for the current authentication mode is available, the DCNM-LAN server uses the local database to authenticate login requests. This behavior is designed to help you prevent accidental lockout from DCNM-LAN. For users who need fallback support, the usernames of their local user accounts must be identical to their usernames on the authentication servers. Also, we recommend that their passwords in the local user accounts should be identical to their passwords on the authentication servers in order to provide transparent fallback support. Because the user cannot determine whether an authentication server or the local database is providing the authentication service, using usernames and passwords on authentication servers that are different than the usernames and passwords in the local database means that the user cannot be certain which username and password should be given.

Password Recovery
If no one can log into the DCNM-LAN client as a user with a DCNM-LAN Administrator role, you can reset passwords by using one of the following scripts:

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

15-3

Chapter 15 Licensing Requirements for Administering DCNM-LAN Authentication Settings

Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

For Microsoft Windows, use dcnm_root_directory/dcm/dcnm/bin/pwreset.bat (by default, dcnm_root_directory is c:\Program Files\Cisco Systems\dcm\dcnm\bin). For Linux, use dcnm_root_directory/dcm/dcnm/bin/pwreset.sh (by default, the dcnm_root_directory is /usr/local/cisco).

To reset a password, run the script for the operating system that you are using, and then enter the user ID to be reset and the password to be used for it. Alternatively, you can reinstall the DCNM-LAN server, which allows you to specify the username and password for a local user account that is assigned the Administrator role. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Users and Device Credentials

Each DCNM-LAN server user has unique device credentials, regardless of whether the user authenticates with a local user account or an account on a RADIUS or TACACS+ server. This feature allows you to maintain accounting logs on managed devices that reflect the actions of each DCNM-LAN server user. For more information, see the Information About Devices and Credentials section on page 17-1.

Virtualization Support
Cisco NX-OS support for virtual device contexts has no effect on DCNM-LAN server users. DCNM-LAN server users can configure any managed device.

Licensing Requirements for Administering DCNM-LAN Authentication Settings

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement Administering Cisco DCNM-LAN authentication settings requires no license. Any feature not included in a license package is bundled with the Cisco DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM-LAN LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Administering DCNM-LAN Authentication Settings

Administering DCNM-LAN authentication settings has the following prerequisites:

You must ensure that every authentication server that you want to use with DCNM-LAN is configured to accept authentication requests from the DCNM-LAN server. If you have deployed DCNM-LAN in a clustered-server environment, ensure that every authentication server is configured to accept requests from each DCNM-LAN server in the cluster.

Cisco DCNM Fundamentals Guide, Release 6.x

15-4

OL-25174-02OL-25174-02

Chapter 15

Administering DCNM-LAN Authentication Settings Guidelines and Limitations for Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

To add, delete, or modify DCNM-LAN local users, you must be logged into the DCNM-LAN client with a user account that is assigned the Administrator DCNM-LAN role.

Guidelines and Limitations for Administering DCNM-LAN Authentication Settings

Administering DCNM-LAN authentication settings has the following configuration guidelines and limitations:

Create a DCNM-LAN user account for each person who uses the DCNM-LAN client. Do not allow people to share a user account. Delete unused DCNM-LAN user accounts. Grant an administrator user account only to those who need to perform administrator tasks in the DCNM-LAN client. We recommend that you use strong passwords. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.

Configuring DCNM-LAN Authentication Settings

This section includes the following topics:

Configuring the Authentication Mode, page 15-5 Adding a DCNM-LAN Local User, page 15-6 Changing the Password of a DCNM-LAN Local User, page 15-7 Changing the Full Name, Role, or Description of a DCNM-LAN Local User, page 15-8 Deleting a DCNM-LAN Server User, page 15-8 Adding Authentication Servers, page 15-9 Changing Authentication Server Settings, page 15-10 Removing an Authentication Server, page 15-11

Configuring the Authentication Mode

You can configure the mode that the DCNM-LAN server uses to authenticate DCNM-LAN client users.

BEFORE YOU BEGIN

Log into the DCNM-LAN client with a user account that has the Administrator user role. If you want to enable RADIUS or TACACS+ authentication mode, you must configure at least one authentication server for the desired authentication mode.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

15-5

Chapter 15 Configuring DCNM-LAN Authentication Settings

Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1 Step 2 Step 3 Step 4 Step 5

From the Feature Selector pane, choose DCNM Server Administration > DCNM Authentication Settings. If necessary, expand the Authentication Mode section. Choose the authentication mode. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server. Restart the DCNM-LAN server. For more information, see the Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers.

Adding a DCNM-LAN Local User

You can add a DCNM-LAN local user account.

Note

Adding a DCNM-LAN local user account does not affect the user account configuration on any Cisco NX-OS device.

BEFORE YOU BEGIN

Log into the DCNM-LAN client with a user account that has the Administrator user role. Determine the username and password for the new DCNM-LAN local user account.

Note

We recommend that you use a strong password. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.

DETAILED STEPS
Step 1 Step 2

From the Feature Selector pane, choose DCNM Server Administration > DCNM Authentication Settings. If necessary, expand the DCNM Local Users section. A table of users appears in the Cisco DCNM Local Users section. From the menu bar, choose Actions > Add User. A new row appears at the bottom of the list of users. By default, all fields in the new row are blank. In the DCNM User Name column of the new row, enter the username. The username can be 1 to 198 characters. Entries can contain case-sensitive letters, numbers, and symbols. (Optional) In the Full Name column, double-click the entry and add a name. For example, enter the real name of the person who will use the DCNM-LAN local user account. The maximum length is 255 case-sensitive letters, numbers, and symbols. In the DCNM Role column, double-click the entry and choose the role. By default, the role is User.

Step 3

Step 4 Step 5

Step 6

Cisco DCNM Fundamentals Guide, Release 6.x

15-6

OL-25174-02OL-25174-02

Chapter 15

Administering DCNM-LAN Authentication Settings Configuring DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 7 Step 8 Step 9 Step 10

In the Password column, double-click the entry and then click the down-arrow button. In the New Password field and the Confirm Password field, enter the password. The password can be 1 to 255 characters. Entries can contain case-sensitive letters, numbers, and symbols. Click OK. (Optional) In the Description column, double-click the entry and add a description of the user account. For example, you could use this entry to provide e-mail and telephone contact details of the person who will be using this DCNM-LAN server user account. The maximum length is 255 case-sensitive letters, numbers, and symbols. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 11

Changing the Password of a DCNM-LAN Local User

You can change the password of a DCNM-LAN local user.

BEFORE YOU BEGIN

An Administrator role is required if you want to change the password of a local user account other than the account that you use to log into the DCNM-LAN client. If your user account is a local user account and it has the User role, you can change the password of your account only. Determine what the new password should be.

Note

We recommend that you use a strong password. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.

DETAILED STEPS
Step 1 Step 2

From the Feature Selector pane, choose DCNM Server Administration > DCNM Server Authentication Settings. If necessary, expand the DCNM Local Users section. A table of users appears in the DCNM Local Users section. In the User Name column, click the username for the user account that you want to change. The row of the username that you clicked is highlighted. In the Password column, double-click the entry and then click the down-arrow button. In the New Password field and the Confirm Password field, enter the new password. The password can be 1 to 255 characters. Entries can contain case-sensitive letters, numbers, and symbols. Click OK. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 3

Step 4 Step 5 Step 6 Step 7

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

15-7

Chapter 15 Configuring DCNM-LAN Authentication Settings

Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Changing the Full Name, Role, or Description of a DCNM-LAN Local User

You can change the full name, role, or description of a DCNM-LAN local user.

Note

You cannot change the username. Instead, add a local user account with the desired username and remove the local user account with the unwanted username.

BEFORE YOU BEGIN

Determine what the new full name or description should be. An Administrator role is required if you want to change the full name, role, or description of a local user account other than the local user account that you use to log into the DCNM-LAN client. If your user account is a local user account and it has the User role, you can change the full name and description for your account only.

DETAILED STEPS
Step 1 Step 2

From the Feature Selector pane, choose DCNM Server Administration > DCNM Authentication Settings. If necessary, expand the DCNM Local Users section. A table of users appears in the Cisco DCNM Local Users section. In the User Name column, click the username of the local user account that you want to change. The row of the username that you clicked is highlighted. (Optional) In the Full Name column, double-click the entry and enter the new name. The maximum length is 255 case-sensitive letters, numbers, and symbols. (Optional) In the DCNM Role column, double-click the entry and choose the new role. You can choose Administrator or User. (Optional) In the Description column, double-click the entry and enter the new description of the user account. The maximum length is 255 case-sensitive letters, numbers, and symbols. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 3

Step 4 Step 5 Step 6 Step 7

Deleting a DCNM-LAN Server User

You can remove a DCNM-LAN local user account.

BEFORE YOU BEGIN

Log into the DCNM-LAN client with a user account that has the Administrator user role. Ensure that you are removing the correct DCNM-LAN local user account.

Cisco DCNM Fundamentals Guide, Release 6.x

15-8

OL-25174-02OL-25174-02

Chapter 15

Administering DCNM-LAN Authentication Settings Configuring DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1 Step 2

From the Feature Selector pane, choose DCNM Server Administration > DCNM Authentication Settings. If necessary, expand the DCNM Local Users section. A table of users appears in the DCNM Local Users section. In the User Name column, click the username of the user account that you want to remove. The row of the username that you clicked is highlighted. From the menu bar, choose Actions > Delete User. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 3

Step 4 Step 5

Adding Authentication Servers

You can add RADIUS and TACACS+ servers to the DCNM-LAN authentication settings.

BEFORE YOU BEGIN

Note

You must ensure that every authentication server that you want to use with DCNM-LAN is configured to accept authentication requests from the DCNM-LAN server. If you have deployed DCNM-LAN in a clustered-server environment, ensure that every authentication server is configured to accept requests from each DCNM-LAN server in the cluster. Ensure that you have the following information about each authentication server that you want to add:

AAA protocol: RADIUS or TACACS+ Server IPv4 address or DNS name that can be resolved by the DCNM-LAN server. Secret key. Port number on which the server accepts authentication requests. (RADIUS only) Port number on which the server accepts accounting messages. Authentication protocol: PAP, CHAP, MSCHAP, or ASCII. (Optional) Username and password of a valid user account on the server for server verification.

Determine whether the server should be a primary, secondary, or tertiary server, which depends upon your authentication server failover strategy.

DETAILED STEPS
Step 1 Step 2

From the Feature Selector pane, choose DCNM Server Administration > DCNM Authentication Settings. If necessary, expand the Authentication Servers section. The Authentication Server Settings table shows RADIUS and TACACS+ server settings. If necessary, expand the RADIUS or TACACS+ server rows.

Step 3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

15-9

Chapter 15 Configuring DCNM-LAN Authentication Settings

Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 4

For each authentication server that you want to add, follow these steps:
a.

Choose the row in which you want to add the server.

Note

The DCNM-LAN client does not allow you to add a secondary server if you have not added a primary server. In addition, you cannot add a tertiary server if you have not added a secondary server.

b.

Double-click the Server Name field and enter the server IPv4 address or DNS hostname.

Note

If you enter a hostname that the DCNM-LAN server cannot resolve, the Server Name field is highlighted in red.

c. d. e. Step 5

Double-click the Secret Key field and enter the secret key (sometimes called a shared secret) of the authentication server. (Optional) If you need to change the default Authentication Port or Accounting Port (RADIUS only), double-click the applicable port field and enter the new port number. Double-click the Authentication Method field and choose the authentication protocol that DCNM-LAN must use when sending authentication requests to the authentication server.

(Optional) If you want to verify that the DCNM-LAN server can authenticate a user with a new authentication server, follow these steps:
a.

To the right of the row for the authentication server that you want to verify, click Verify. A Verification dialog box appears. Enter a username and password for a valid user account on the authentication server. Click Verify.

b. c.

The DCNM-LAN client displays a message indicating whether the verification attempt succeeded or failed. A verification failure may mean that the authentication server is unavailable or that the authentication settings are incorrect.
Step 6

From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Changing Authentication Server Settings

You can change the settings for authentication servers that you have already configured in the DCNM-LAN client. If you have more than one RADIUS or TACACS+ server, you can change which server is primary, secondary, or tertiary.

DETAILED STEPS
Step 1 Step 2

From the Feature Selector pane, choose DCNM Server Administration > DCNM Authentication Settings. If necessary, expand the Authentication Servers section. The Authentication Server Settings table shows RADIUS and TACACS+ server settings. If necessary, expand the RADIUS or TACACS+ server rows.

Step 3

Cisco DCNM Fundamentals Guide, Release 6.x

15-10

OL-25174-02OL-25174-02

Chapter 15

Administering DCNM-LAN Authentication Settings Configuring DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 4 Step 5 Step 6

(Optional) If you want to change the settings of an authentication server, double-click each field that you need to change and enter the changes. (Optional) If you want to reorder RADIUS or TACACS+ servers, right-click a server and choose Move Up or Move Down, as needed. (Optional) If you want to verify that the DCNM-LAN server can authenticate a user with an authentication server, follow these steps:
a.

To the right of the row for the authentication server that you want to verify, click Verify. A Verification dialog box appears. Enter a username and password for a valid user account on the authentication server. Click Verify.

b. c.

The DCNM-LAN client displays a message indicating whether the verification attempt succeeded or failed. A verification failure may mean that the authentication server is unavailable or that the authentication settings are incorrect.
Step 7

From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Removing an Authentication Server

You can remove a RADIUS or TACACS+ authentication server from the DCNM-LAN authentication settings.

BEFORE YOU BEGIN

You cannot remove all authentication servers for the current authentication mode. Instead, change the authentication mode first and then remove all the authentication servers.

DETAILED STEPS
Step 1 Step 2

From the Feature Selector pane, choose DCNM Server Administration > DCNM Authentication Settings. If necessary, expand the Authentication Servers section. The Authentication Server Settings table shows RADIUS and TACACS+ server settings. If necessary, expand the RADIUS or TACACS+ server rows. Right-click the authentication server that you want to remove and choose Remove Server. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 3 Step 4 Step 5

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

15-11

Chapter 15 Viewing DCNM-LAN Local Users

Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing DCNM-LAN Local Users

To view DCNM-LAN server user accounts, from the Feature Selector pane, choose DCNM Server Administration > DCNM Authentication Settings and then, if necessary, expand the Cisco DCNM Local Users section. DCNM-LAN server user accounts, including usernames and descriptions, appear in the Contents pane. Passwords appear masked for security. For information about the fields that appear, see the Field Descriptions for DCNM-LAN Authentication Settings section on page 15-13.

Verifying Authentication Server Settings

You can verify that the DCNM-LAN server can authenticate a user with a particular authentication server that you have configured.

DETAILED STEPS
Step 1 Step 2

From the Feature Selector pane, choose DCNM Server Administration > DCNM Authentication Settings. If necessary, expand the Authentication Servers section. The Authentication Server Settings table shows RADIUS and TACACS+ server settings. Click Verify. A Verification dialog box appears. Enter a username and password for a valid user account on the authentication server. To the right of the row for the authentication server that you want to verify, click Verify. The DCNM-LAN client displays a message indicating whether the verification attempt succeeded or failed. A verification failure may mean that the authentication server is unavailable or that the authentication settings are incorrect.

Step 3

Step 4 Step 5

Cisco DCNM Fundamentals Guide, Release 6.x

15-12

OL-25174-02OL-25174-02

Chapter 15

Administering DCNM-LAN Authentication Settings Field Descriptions for DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Field Descriptions for DCNM-LAN Authentication Settings

This section includes the following field descriptions for the DCNM-LAN Authentication Settings feature:

Authentication Mode Section, page 15-13 DCNM-LAN Local Users Section, page 15-13 Authentication Servers Section, page 15-14

Authentication Mode Section

Table 15-3 Authentication Mode Section

Field Local RADIUS

Description Whether DCNM-LAN authenticates users with the local user database only. Whether DCNM-LAN authenticates users with a RADIUS server. When no configured RADIUS server is reachable, DCNM-LAN falls back to using the local database for user authentication. Whether DCNM-LAN authenticates users with a TACACS+ server. When no configured TACACS+ server is reachable, DCNM-LAN falls back to using the local database for user authentication.

TACACS+

DCNM-LAN Local Users Section

Table 15-4 DCNM-LAN Local Users Section

Field DCNM-LAN User Name

Description Display only. Name of the DCNM-LAN server user account. This name can be used to log into the DCNM-LAN client when the authentication mode is local or when no authentication server for the current authentication mode is reachable. Entries are case sensitive. Valid characters are all letters, numbers, and symbols. The minimum length is 1 character. The maximum length is 198 characters. Other name for the user account, such as the name of the person who uses the DCNM-LAN server user account. This name cannot be used to log into the DCNM-LAN client. Valid characters are all letters, numbers, and symbols. The maximum length is 255 characters. This field is blank by default. Role of the user account. Valid values are User and Administrator. For more information, see Table 15-1. By default, a DCNM-LAN server user account is assigned the role of User. Password for the DCNM-LAN server user. This field is always masked for security. Entries are case sensitive. Valid characters are all letters, numbers, and symbols. The minimum length is 1 character. The maximum length is 255 characters.

Full Name

DCNM-LAN Role

Password

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

15-13

Chapter 15 Additional References

Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 15-4 DCNM-LAN Local Users Section (continued)

Field Description

Description Description of the DCNM-LAN server user. Valid characters are all letters, numbers, and symbols. The maximum length is 255 characters. This field is blank by default.

Authentication Servers Section

Table 15-5 Authentication Servers Section

Field Server Name

Description DNS name or IPv4 address of the authentication server.

DNS nameIf you specify a DNS name, the DCNM-LAN server must be able to resolve the IP address of the server. Valid DNS names characters are alphanumeric. IPv4 addressIf you specify an IP address, valid entries are in dotted decimal format.

Secret Key Authentication Port

Shared secret of the authentication server. Valid entries are case-sensitive letters, numbers, and symbols. TCP or UDP port number that the authentication server listens to for authentication requests. By default, the authentication port for a RADIUS server is UDP port 1812 and the authentication port for a TACACS+ server is TCP port 49. UDP port number that the RADIUS authentication server listens to for authentication requests. By default, the accounting port for a RADIUS server is UDP port 1813. Authentication protocol that the DCNM-LAN server uses in authentication requests to the authentication server. Supported authentication methods are as follows:

Accounting Port

Authentication Method

PAP CHAP MSCHAP ASCII

Additional References
For additional information related to administering DCNM-LAN authentication settings, see the following sections:

Related Documents, page 15-15 Standards, page 15-15

Cisco DCNM Fundamentals Guide, Release 6.x

15-14

OL-25174-02OL-25174-02

Chapter 15

Administering DCNM-LAN Authentication Settings Feature History for DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Related Documents
Related Topic Logging into the DCNM-LAN client Document Title Opening the DCNM-LAN Client, page 14-8

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Feature History for DCNM-LAN Authentication Settings

Table 15-6 lists the release history for this feature.
Table 15-6 Feature History for DCNM-LAN Server Users

Feature Name DCNM-LAN Authentication Settings

Releases 5.0(2)

Feature Information No change from Release 4.2.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

15-15

Chapter 15 Feature History for DCNM-LAN Authentication Settings

Administering DCNM-LAN Authentication Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

15-16

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

16

Administering Device Discovery

This chapter describes how to administer the Device Discovery feature in the Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Device Discovery, page 16-1 Licensing Requirements for Device Discovery, page 16-6 Prerequisites for Device Discovery, page 16-7 Guidelines and Limitations for Device Discovery, page 16-7 Performing Device Discovery, page 16-8 Viewing the Status of Device Discovery Tasks, page 16-12 Where to Go Next, page 16-12 Field Descriptions for Device Discovery, page 16-13 Device System-Message Logging Level Reference, page 16-14 Additional References for Device Discovery, page 16-18 Feature History for Device Discovery, page 16-19

Information About Device Discovery

This section includes the following topics:

Device Discovery, page 16-2 Discovery Protocols, page 16-2 Credentials and Discovery, page 16-3 Discovery Process, page 16-3 Cisco NX-OS System-Message Logging Requirements, page 16-4 Automatic Logging-Level Configuration Support, page 16-5 VDC Support, page 16-5

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-1

Chapter 16 Information About Device Discovery

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Device Discovery
The Device Discovery feature creates devices in DCNM-LAN by connecting to a Cisco NX-OS device and retrieving data from the device, including its running configuration. DCNM-LAN can also discover Cisco NX-OS devices and network servers that are neighbors of the first device, which is known as the seed device.

Note

Staring from Cisco NX-OS Release 5.2.2(a) the Cisco DCNM-LAN supports the discovery of the following modules:

N7K-F248XP-25 Line Card N55-M16FP 16-Port FC GEM N7K-C7010-FAB2 Fabric 2 module N7K-C7018-FAB2 Fabric 2 module N55-D160L3-V2 Daughter Card N55-M160L3-V2 Line Card N3K-C3048TP-1GE Layer 3 switch N3K-C3016Q- 40GE Layer 3 switch

If the device supports virtual device contexts (VDCs), DCNM-LAN retrieves the running configuration of each VDC that is configured on the physical device. DCNM-LAN displays each VDC as a device, including the default VDC. If the Cisco NX-OS device has only the default VDC, then device discovery creates only one device in DCNM-LAN. When DCNM-LAN connects to a device to retrieve its configuration, it uses the XML management interface, which uses the XML-based Network Configuration Protocol (NETCONF) over Secure Shell (SSH). For more information, see the Cisco NX-OS XML Interface User Guide.

Discovery Protocols
DCNM-LAN uses a variety of protocols to discover devices and servers in your data center network. This section includes the following topics:

Cisco Discovery Protocol, page 16-2 Link Layer Discovery Protocol, page 16-3 Fibre Channel, page 16-3

Cisco Discovery Protocol

Device discovery uses the Cisco Discovery Protocol (CDP) to find devices that are connected to the initial device in the discovery process. CDP exchanges information between adjacent devices over the data link layer. The exchanged information is helpful in determining the network topology and physical configuration outside of the logical or IP layer. CDP allows DCNM-LAN to discover devices that are one or more hops beyond the seed device in the discovery process. When you start the discovery process using the Device Discovery feature, you can limit the number of hops that the discovery process can make.

Cisco DCNM Fundamentals Guide, Release 6.x

16-2

OL-25174-02OL-25174-02

Chapter 16

Administering Device Discovery Information About Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
After DCNM-LAN discovers a Cisco NX-OS device using CDP, it connects to the device and retrieves information, such as the running configuration of the device. The information collected allows DCNM-LAN to manage the device. DCNM-LAN supports CDP hops on some Cisco switches that run Cisco IOS software. Although DCNM-LAN cannot manage these devices, the Topology feature allows you to see unmanaged devices and the CDP links between unmanaged devices and managed devices.

Link Layer Discovery Protocol

Device discovery uses Link Layer Discovery Protocol (LLDP) to discover the network adapters of servers that are connected to Cisco NX-OS devices. For more information, see Chapter 20, Configuring Network Servers.

Fibre Channel
To discover network elements in a storage area network (SAN), DCNM-LAN uses Fibre Channel. DCNM-LAN can discover SAN switches, servers, and storage arrays.

Credentials and Discovery

Device discovery requires that you provide a username and password for a user account on the seed device. To successfully complete the discovery of a Cisco NX-OS device, the user account that you specify must be assigned to either the network-admin or the vdc-admin role. If you want to discover devices that are one or more hops from the seed device, all devices in the chain of hops must be configured with a user account of the same username and password. All Cisco NX-OS devices in the chain of hops must assign the user account to the network-admin or the vdc-admin role.

Discovery Process
DCNM-LAN discovers devices in several phases, as follows:
1. 2. 3.

CDP neighbor discoveryDiscovers the topology of the interconnected devices, beginning with the seed device and preceding for the number of CDP hops specified when you initiate discovery. Supported device selectionDetermines which of the discovered devices are supported by DCNM-LAN. Discovery continues for the supported devices only. Inventory discoveryDiscovers the inventory of the devices selected in the previous phase. For example, if the device is a Cisco Nexus 7000 Series switch, inventory discovery determines the supervisor modules, I/O modules, power supplies, and fans. If the device is a Cisco Nexus 1000V switch, inventory discovery finds the Virtual Supervisor Module and Virtual Ethernet Modules. Device configuration discoveryDiscovers the details of feature configuration on each device, such as interfaces, access control lists, and VLANs. Network discoveryAssociates network features with the device configuration details discovered in the previous phase.

4. 5.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-3

Chapter 16 Information About Device Discovery

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco NX-OS System-Message Logging Requirements

To monitor and manage devices, DCNM-LAN depends partly on system messages that it retrieves from managed devices. This section describes the system-message requirements that all Cisco NX-OS devices must meet before they can be managed and monitored by DCNM-LAN. This section includes the following topics:

Interface Link-Status Events Logging Requirement, page 16-4 Logfile Requirements, page 16-4 Logging Severity-Level Requirements, page 16-4

Interface Link-Status Events Logging Requirement

Devices must be configured to log system messages about interface link-status change events. This requirement ensures that DCNM-LAN receives information about interface link-status changes. The following two commands must be present in the running configuration on the device:

logging event link-status enable logging event link status default

To ensure that these commands are configured on the device, perform the steps in the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8.

Logfile Requirements
Devices must be configured to store system messages that are severity level 6 or lower in the log file. Although you can specify any name for the log file, we recommend that you do not change the name of the log file. When you change the name of the log file, the device clears previous system messages. The default name of the log file is messages. If you use the default name for the log file, the following command must be present in the running configuration on the device: logging logfile messages 6 To ensure that this command is configured on the device, perform the steps in the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8.

Logging Severity-Level Requirements

DCNM-LAN has minimum severity level requirements for some Cisco NX-OS logging facilities. All enabled features on a Cisco NX-OS have a default logging level. The logging level required by DCNM-LAN varies per logging facility but is often higher than the default logging level in Cisco NX-OS. For more information, see the Automatic Logging-Level Configuration Support section on page 16-5.

Cisco DCNM Fundamentals Guide, Release 6.x

16-4

OL-25174-02OL-25174-02

Chapter 16

Administering Device Discovery Information About Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Automatic Logging-Level Configuration Support

DCNM-LAN provides support for automatic logging level configuration for all supported Cisco NX-OS releases with the exception of Cisco NX-OS Release 4.0, which is available on Cisco Nexus 7000 Series switches only. This section describes how DCNM-LAN supports automatic logging-level configuration. For information about manually configuring logging levels for Cisco NX-OS Release 4.0, see the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8.

During Device Discovery

During device discovery, if DCNM-LAN finds that a logging level on a discovered device is below the minimum logging-level requirement for that logging facility, DCNM-LAN raises the logging level to meet the minimum requirement. If logging levels meet or exceed the requirements, DCNM-LAN does not change the logging levels during discovery.

At Feature Enablement in the DCNM-LAN Client

If you use the DCNM-LAN client to enable a feature on a device and the default logging level for the feature does not meet the minimum requirement, the DCNM-LAN client warns you that it will configure the logging level on the device to meet the requirement. If you reject the logging level change, DCNM-LAN does not enable the feature.

During Auto-Synchronization with Managed Devices

If you use another means, such as the command-line interface (CLI), to enable a feature on a managed device and the default logging level for the feature does not meet the minimum requirement, DCNM-LAN automatically configures the logging level to meet the requirement after DCNM-LAN detects that the feature is enabled. If you use the CLI or any other method to lower a logging level below the minimum requirement of DCNM-LAN, after DCNM-LAN detects the logging level change, it changes the state of that device to unmanaged. When this occurs, the Devices and Credentials feature shows that logging levels are the reason that the device is unmanaged. You can use the Devices and Credentials feature to discover the device again. During rediscovery, DCNM-LAN sets logging levels that do not meet the minimum requirements.

VDC Support
When DCNM-LAN discovers a Cisco NX-OS device that supports VDCs, it determines how many VDCs are on the Cisco NX-OS device. In DCNM-LAN, each VDC is treated as a separate device. The status of each VDC is tracked separately and you can configure each VDC independently of other VDCs on a Cisco NX-OS device. Before discovering a Cisco Nexus 7000 Series device that has nondefault VDCs, ensure that each VDC meets the prerequisites for discovery. For more information, see the Prerequisites for Device Discovery section on page 16-7.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-5

Chapter 16 Licensing Requirements for Device Discovery

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Licensing Requirements for Device Discovery

The following table shows the licensing requirements for this feature: Product DCNM-LAN License Requirement The Device Discovery feature requires no license. Any feature not included in a license package is bundled with the DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Cisco DCNM Fundamentals Guide, Release 6.x

16-6

OL-25174-02OL-25174-02

Chapter 16

Administering Device Discovery Prerequisites for Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Prerequisites for Device Discovery

Prior to performing device discovery, you should be familiar with the following:

VDCs, if you are discovering Cisco Nexus 7000 Series devices. CDP The DCNM-LAN server must be able to connect to devices that it discovers. Cisco NX-OS devices must be running a supported release of Cisco NX-OS. For information about supported releases of Cisco NX-OS, see the Cisco DCNM Release Notes, Release 5.x. The Cisco NX-OS device must have the minimal configuration that is required to enable device discovery to succeed. For more information, see the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8. For a Cisco Nexus 7000 Series device, each VDC that you want to discover must have a management interface configured. DCNM-LAN supports discovery of VDCs that are configured with a management interface that is the mgmt0 interface, which is an out-of-band virtual interface, or with an in-band Ethernet interface that is allocated to the VDC. To allow DCNM-LAN to discover devices that are CDP neighbors, CDP must be enabled both globally on each device and specifically on the device interfaces used for device discovery. For a Cisco Nexus 7000 Series device, CDP must be enabled globally in each VDC and on the management interface that each VDC is configured to use. Discovery of network servers requires that LLDP is enabled globally on devices connected to network servers and specifically on the device interfaces connected to the network adapters on network servers.

The Device Discovery feature has the following prerequisites:

Guidelines and Limitations for Device Discovery

The Device Discovery feature has the following configuration guidelines and limitations:

Ensure that Cisco NX-OS devices that you want to discover have been prepared for discovery. For more information, see the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8. DCNM-LAN can manage only devices that run Cisco NX-OS. For more information about supported device operating systems and supported device hardware, see the Cisco DCNM Release Notes, Release 5.x. CDP-based discovery of devices requires that all devices in the chain of CDP hops use the same username and password specified for the seed device. If your security practices do not allow the same username and password to be used on each device, you can perform device discovery for each device individually. Devices that are CDP hops but which are not running Cisco IOS software appear in the Topology feature but cannot be managed by DCNM-LAN.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-7

Chapter 16 Performing Device Discovery

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Performing Device Discovery

This section includes the following topics:

Verifying the Discovery Readiness of a Cisco NX-OS Device, page 16-8 Discovering Devices, page 16-10 Rediscovering Devices, page 16-11

Verifying the Discovery Readiness of a Cisco NX-OS Device

Before you perform device discovery with DCNM-LAN, you should perform the following procedure on each Cisco NX-OS device that you want to manage and monitor with DCNM-LAN. This procedure helps to ensure that device discovery succeeds and that DCNM-LAN can effectively manage and monitor the device.

Note

If you are preparing a physical device that supports virtual device contexts (VDCs), remember that DCNM-LAN considers each VDC to be a device. You must verify discovery readiness for each VDC that you want to manage and monitor with DCNM-LAN.

DETAILED STEPS
Step 1 Step 2 Step 3

Log into the CLI of the Cisco NX-OS device. Use the configure terminal command to access global configuration mode. Ensure that an RSA or DSA key exists so that secure shell (SSH) connections can succeed. To do so, use the show ssh key rsa or show ssh key dsa command. If you need to generate a key, use the ssh key command.

Note

You must disable the SSH server before you can generate a key. To do so, use the no feature ssh command.

Step 4

Ensure that the SSH server is enabled. To do so, use the show ssh server command. If the SSH server is not enabled, use the feature ssh command to enable it. Ensure that CDP is enabled globally and on the interface that DCNM-LAN uses to connect to the device. Use the show run cdp all command to see whether CDP is enabled. Verify that the logging event link-status default and logging event link-status enable commands are configured.
switch(config)# show running-config all | include "logging event link-status" logging event link-status default logging event link-status enable

Step 5 Step 6

If either command is missing, enter it to add it to the running configuration.

Cisco DCNM Fundamentals Guide, Release 6.x

16-8

OL-25174-02OL-25174-02

Chapter 16

Administering Device Discovery Performing Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

The logging event link-status enable command is included in the default Cisco NX-OS configuration. The show running-config command displays the default configuration only if you use the all keyword.

Step 7

Verify that the device is configured to log system messages that are severity 6 or lower.

Note

The default name of the log file is messages; however, we recommend that you use the log-file name currently configured on the device. If you change the name of the log file, the device clears previous system messages.

switch(config)# show running-config all | include logfile logging logfile logfile-name 6

If the logging logfile command does not appear or if the severity level is less than 6, configure the logging logfile command.
switch(config)# logging logfile logfile-name 6

Step 8

If the device is a Cisco Nexus 7000 Series switch that is running Cisco NX-OS Release 4.0, you must manually verify that the logging level configuration of the device meets the DCNM-LAN logging level requirements. To do so, follow these steps:
a.

Determine which nondefault features are enabled on the device.

switch(config)# show running-config | include feature feature feature1 feature feature2 feature feature3 . . .

b.

View the logging levels currently configured on the device. The show logging level command displays logging levels only for features that are enabled. The Current Session Severity column lists the current logging level.
switch(config)# show logging level Facility Default Severity ----------------------aaa 3 aclmgr 3 . . . Current Session Severity -----------------------5 3

Note

You can use the show logging level command with the facility name when you want to see the logging level of a single logging facility, such as show logging level aaa.

c.

Determine which logging levels on the device are below the minimum DCNM-LAN required logging levels. To do so, compare the logging levels displayed on page 16-9 to the minimum DCNM-LAN required logging levels that are listed in Table 16-2. For each logging facility with a logging level that is below the minimum DCNM-LAN required logging level, configure the device with a logging level that meets or exceeds the DCNM-LAN requirement.

d.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-9

Chapter 16 Performing Device Discovery

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
switch(config)# logging level facility severity-level

The facility argument is the applicable logging-facility keyword from Table 16-2, and severity-level is the applicable minimum DCNM-LAN required logging level or higher (up to 7).
e. Step 9

Use the show logging level command to verify your changes to the configuration.

Copy the running configuration to the startup configuration to save your changes.
switch(config)# copy running-config startup-config [########################################] 100% switch(config)#

Discovering Devices
You can discover one or more devices. When a discovery task succeeds, DCNM-LAN retrieves the running configuration and status information of discovered Cisco NX-OS devices. Use this procedure for the following purposes:

To discover devices that are not currently managed by DCNM-LAN. For example, you should use this procedure when DCNM-LAN has not yet discovered any devices, such as after a new installation. To discover devices that you have added to your network without rediscovering devices that DCNM-LAN already has discovered. To rediscover the topology when CDP links have changed without rediscovering devices that DCNM-LAN has already discovered.

Note

You must successfully discover a Cisco NX-OS device before you can use DCNM-LAN to configure the device.

BEFORE YOU BEGIN

Ensure that you have configured the Cisco NX-OS device so that the DCNM-LAN server can connect to it and successfully discover it. For more information, see the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8. Determine the IPv4 address of the device that you want DCNM-LAN to connect to when it starts the discovery task. This is the seed device for the discovery. Determine whether you want to discover devices that are CDP neighbors of the seed device. If so, determine the maximum number of hops from the seed device that the discovery process can make.

Note

The discovery process can perform complete discovery of neighbors only if the neighboring devices are configured with the same credentials as the seed device.

Cisco DCNM Fundamentals Guide, Release 6.x

16-10

OL-25174-02OL-25174-02

Chapter 16

Administering Device Discovery Performing Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Device Discovery. The discovery tasks appear in the Discovery Tasks area of the Contents pane. In the Seed Device field, enter the IPv4 address of the device that you want DCNM-LAN to connect to when it starts the discovery task. Valid entries are in dotted decimal format. In the User Name field, enter the username of a user account on the device. The user account must have a network-admin or vdc-admin role. In the Password field, enter the password for the user account that you entered in the User Name field. For Catalyst 6500 devices, enter the enable password in the Enable Password field to allow for IOS privileged EXEC mode commands.

Step 2 Step 3 Step 4

Step 5

(Optional) If you want DCNM-LAN to discover devices that are CDP neighbors of the seed device, in the Maximum Hops of Neighbors to Discover field, enter the desired maximum number of hops. By default, the maximum hops is 0 (zero). Ensure that Rediscover Configuration and Status for Existing Devices is unchecked. By default, this check box is unchecked. By leaving this check box unchecked, you enable DCNM-LAN to use previously discovered devices as CDP hops without retrieving their running configuration and status information.

Step 6

Step 7

Click Start Discovery. After a short delay, the discovery task appears at the bottom of the list of tasks in the Discovery Tasks area. DCNM-LAN updates the task status periodically.

Step 8

Wait until the status for the task is Successful. This step may take several minutes. After the status is Successful, you can use DCNM-LAN to configure and monitor the discovered devices. You do not need to save your changes.

Rediscovering Devices
You can rediscover one or more devices.

Note

Rediscovery replaces any configuration data that DCNM-LAN has for a Cisco NX-OS device with the configuration data retrieved during the rediscovery. If you need to discover one or more devices without retrieving configuration and status information for already discovered devices, see the Discovering Devices section on page 16-10. You must successfully discover a Cisco NX-OS device before you can use DCNM-LAN to configure the device.

BEFORE YOU BEGIN

Ensure that you have configured the Cisco NX-OS device so that the DCNM-LAN server can connect to it. For more information, see the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-11

Chapter 16 Viewing the Status of Device Discovery Tasks

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Device Discovery. The discovery tasks and their status appear in the Discovery Tasks area of the Contents pane. In the Seed Device field, enter the IPv4 address of the device that you want DCNM-LAN to connect to when it starts the discovery task. Valid entries are in dotted decimal format. In the User Name field, enter the username of a user account on the device. The user account must have a network-admin or vdc-admin role. In the Password field, enter the password for the user account that you entered in the User Name field. For Catalyst 6500 devices, enter the enable password in the Enable Password field to allow for IOS privileged EXEC mode commands.

Step 2 Step 3 Step 4

Step 5

(Optional) If you want DCNM-LAN to rediscover devices that are CDP neighbors of the seed device, in the Maximum Hops of Neighbors to Discover field, enter the desired maximum number of hops. By default, the maximum hops is 0 (zero). Check Rediscover Configuration and Status for Existing Devices. By default, this check box is unchecked. By checking this check box, you enable DCNM-LAN to replace any configuration and status information that it has about a previously discovered device with the running configuration and status information retrieved from the device.

Step 6

Step 7

Click Start Discovery. After a short delay, the discovery task appears at the bottom of the list of tasks in the Discovery Tasks area. DCNM-LAN updates the task status periodically.

Step 8

Wait until the status for the task is Successful. This step may take several minutes. After the status is Successful, you can use DCNM-LAN to configure and monitor the discovered devices. You do not need to save your changes.

Viewing the Status of Device Discovery Tasks

To view the status of device discovery tasks, from the Feature Selector pane, choose DCNM Server Administration > Device Discovery. The tasks, including the task status, appear in the Discovery Tasks area in the Contents pane. For information about the fields that appear, see the Field Descriptions for Device Discovery section on page 16-13.

Where to Go Next
View the discovered devices and configure unique device credentials, as needed. For more information, see the Administering Devices and Credentials section on page 17-1.

Cisco DCNM Fundamentals Guide, Release 6.x

16-12

OL-25174-02OL-25174-02

Chapter 16

Administering Device Discovery Field Descriptions for Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Field Descriptions for Device Discovery

This section includes the following field descriptions for the Device Discovery feature:

Device Discovery Content Pane, page 16-13 Related Fields, page 16-14

Device Discovery Content Pane

Table 16-1 Device Discovery Content Pane

Field
Discovery Setting

Description IPv4 address of the first device that you want to discover. Valid entries are in dotted decimal format. By default, this field is blank. Name of the device user account that the DCNM-LAN server uses to access the device. The user account must have network-admin or vdc-admin privileges on the device. By default, this field is blank. Password for the device user account specified in the User Name field. By default, this field is blank. Enable password for Catalyst 6500 devices to allow for IOS privileged EXEC mode commands. Largest permissible number of CDP hops between the DCNM-LAN server and the device. If the server connects to the device but exceeds this number of hops, the discovery fails. The default setting is 0 (zero), which disables the discovery of neighboring devices. Whether the discovery task you are configuring is to replace an existing device discovery that has already completed. By default, this check box is unchecked.

Seed Device User Name

Password Enable Password Maximum Hops of Neighbors to Discover

Rediscover Configuration and Status for Existing Devices

Discovery Tasks

Task ID Owner

Display only. Number assigned to the discovery task. The task ID indicates the order in which discovery tasks occurred. Display only. DCNM-LAN server user account used to start the discovery task. Display only. Date and time of the most recent update to the Status field. Display only. Why the discovery task was created. Display only. State of the discovery task. Valid values are as follows:

Seed Device IP Address Display only. IPv4 address of the seed device. Discovered Time Reason Status

In progressThe discovery tasks are ongoing. SuccessfulThe discovery task completed without errors. FailedThe discovery task completed with errors.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-13

Chapter 16 Device System-Message Logging Level Reference

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Related Fields
For information about fields that configure devices, see the Administering Devices and Credentials section on page 17-1.

Device System-Message Logging Level Reference

This section provides information about the minimum device logging-level requirements of DCNM-LAN. DCNM-LAN has logging-level requirements for only a subset of the logging facilities of supported devices. If a Cisco NX-OS logging facility is not specified in this section, DCNM-LAN does not have a requirement for that logging facility.

Note

DCNM-LAN provides automatic device logging-level support. For more information, see the Automatic Logging-Level Configuration Support, page 16-5. This section provides the following topics that document DCNM-LAN minimum logging levels per supported device type:

Cisco Nexus 7000 NX-OS Logging Levels per DCNM-LAN Feature, page 16-15 Cisco Nexus 5000 NX-OS Logging Levels per DCNM-LAN Feature, page 16-16 Cisco Nexus 4000 NX-OS Logging Levels per DCNM-LAN Feature, page 16-17 Cisco Nexus 1000V NX-OS Logging Levels per DCNM-LAN Feature, page 16-18

Cisco DCNM Fundamentals Guide, Release 6.x

16-14

OL-25174-02OL-25174-02

Chapter 16

Administering Device Discovery Device System-Message Logging Level Reference

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco Nexus 7000 NX-OS Logging Levels per DCNM-LAN Feature

Table 16-2 Cisco Nexus 7000 NX-OS Logging Levels per Cisco DCNM-LAN Feature

Cisco DCNM-LAN Feature AAA

Enabled Logging Facility Cisco Nexus 7000 NX-OS by Default? Keyword Logging Facility AAA RADIUS TACACS+ Yes Yes No Yes No No aaa radius tacacs+ cdp lldp dhcp

Cisco NX-OS Default Logging Level 3 3 3 2 2 2

Minimum Cisco DCNM-LANRequired Logging Level1 5 5 5 6 5 6

Device Discovery Topology DHCP snooping Dynamic ARP Inspection IP Source Guard Dot1X Ethernet Interfaces Traffic Storm Control Gateway Load Balancing Protocol (GLBP) Hot Standby Router Protocol (HSRP) Inventory

CDP LLDP DHCP snooping

802.1X Ethernet port manager GLBP HSRP engine Module Platform System manager

No Yes No No Yes Yes Yes Yes Yes No Yes Yes No Yes No No

dot1x ethpm glbp hsrp module platform sysmgr track port-channel port-security monitor spanning-tree udld vdc_mgr vpc interface-vlan

2 5 3 3 5 5 3 3 5 2 3 3 5 6 2 2

5 5 6 6 5 5 3 6 6 5 6 6 5 6 6 5

Object Tracking Port-Channel Interfaces Port security SPAN Spanning Tree Virtual Device Contexts (VDCs) Virtual Port Channel (vPC) VLAN Network Interfaces

Object tracking Port-channel interfaces Port security SPAN Spanning tree VDC manager VPC Interface VLAN

Unidirectional Link Detection (UDLD) UDLD

1. Minimum Cisco DCNM-LAN logging levels appear in bold text for Cisco Nexus 7000 NX-OS logging facilities that have a default logging level that is too low.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-15

Chapter 16 Device System-Message Logging Level Reference

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco Nexus 5000 NX-OS Logging Levels per DCNM-LAN Feature

Table 16-3 Cisco Nexus 5000 NX-OS Logging Levels per Cisco DCNM-LAN Feature

Cisco DCNM-LAN Feature AAA

Enabled Logging Facility Cisco Nexus 5000 NX-OS by Default? Keyword Logging Facility AAA RADIUS TACACS+ Yes Yes No Yes No Yes Yes Yes Yes Yes Yes Yes Yes No No No aaa radius tacacs+ cdp lldp ethpm fex sysmgr pfm nohms port-channel monitor spanning-tree udld vpc interface-vlan

Cisco NX-OS Default Logging Level 3 3 3 2 2 5 5 3 5 2 5 3 3 5 2 2

Minimum Cisco DCNM-LANRequired Logging Level1 5 5 5 6 5 5 5 3 5 2 6 6 6 5 6 5

Device Discovery Topology Ethernet Interfaces Traffic Storm Control Fabric Extender Inventory

CDP LLDP Ethernet port manager FEX System manager Platform NOHMS

Port-Channel Interfaces SPAN Spanning Tree Virtual Port Channel VLAN Network Interfaces

Port-channel interfaces SPAN Spanning tree VPC Interface VLAN

Unidirectional Link Detection (UDLD) UDLD

1. Minimum Cisco DCNM-LAN logging levels appear in bold text for Cisco Nexus 5000 NX-OS logging facilities that have a default logging level that is too low.

Cisco DCNM Fundamentals Guide, Release 6.x

16-16

OL-25174-02OL-25174-02

Chapter 16

Administering Device Discovery Device System-Message Logging Level Reference

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco Nexus 4000 NX-OS Logging Levels per DCNM-LAN Feature

Table 16-4 Cisco Nexus 4000 NX-OS Logging Levels per Cisco DCNM-LAN Feature

Cisco DCNM-LAN Feature AAA

Enabled Logging Facility Cisco Nexus 4000 NX-OS by Default? Keyword Logging Facility AAA RADIUS TACACS+ Yes Yes No Yes Yes Yes Yes No Yes Yes Yes No No aaa radius tacacs+ cdp ethpm fip-snooping sysmgr lstsvc port-channel monitor spanning-tree udld interface-vlan

Cisco NX-OS Default Logging Level 3 3 3 2 5 2 3 2 5 3 3 5 2

Minimum Cisco DCNM-LANRequired Logging Level1 5 5 5 6 5 5 3 4 6 6 6 5 5

Device Discovery Topology Ethernet Interfaces Traffic Storm Control FIP Snooping Inventory Link State Tracking Port-Channel Interfaces SPAN Spanning Tree VLAN Network Interfaces

CDP Ethernet port manager FIPSM System manager LST Port-channel interfaces SPAN Spanning tree Interface VLAN

Unidirectional Link Detection (UDLD) UDLD

1. Minimum Cisco DCNM-LAN logging levels appear in bold text for Cisco Nexus 4000 NX-OS logging facilities that have a default logging level that is too low.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-17

Chapter 16 Additional References for Device Discovery

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco Nexus 1000V NX-OS Logging Levels per DCNM-LAN Feature

Table 16-5 Cisco Nexus 1000V NX-OS Logging Levels per Cisco DCNM-LAN Feature

Cisco DCNM-LAN Feature AAA

Cisco Nexus 1000V NX-OS Logging Facility AAA RADIUS TACACS+

Enabled Logging by Facility Default? Keyword Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes aaa radius tacacs+ cdp ethpm ifmgr vim module platform sysmgr msp port-channel port-profile vms monitor

Cisco NX-OS Default Logging Level 3 3 3 2 5 5 5 5 5 3 5 5 5 5 3

Minimum Cisco DCNM-LANRequired Logging Level1 5 5 5 6 5 5 5 5 5 3 5 6 5 5 6

Device Discovery Topology Ethernet Interfaces Virtual Ethernet Interfaces Inventory

CDP Ethernet port manager Ifmgr VIM Module Platform System manager

Virtual Switches Port-Channel Interfaces Port Profiles SPAN

MSP Port-channel interfaces Port profile VMS SPAN

1. Minimum Cisco DCNM-LAN logging levels appear in bold text for Cisco Nexus 1000V NX-OS logging facilities that have a default logging level that is too low.

Additional References for Device Discovery

For additional information related to device discovery, see the following sections:

Related Documents, page 16-18 Standards, page 16-19

Related Documents
Related Topic Device and Credentials Document Title Chapter 17, Administering Devices and Credentials

Cisco DCNM Fundamentals Guide, Release 6.x

16-18

OL-25174-02OL-25174-02

Chapter 16

Administering Device Discovery Feature History for Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Related Topic Network servers Cisco NX-OS XML management interface Document Title Chapter 20, Configuring Network Servers Cisco NX-OS XML Interface User Guide

Standards
Standards NETCONF protocol over the Secure Shell (SSH) Title RFC 4742

Feature History for Device Discovery

Table 16-6 lists the release history for this feature.
Table 16-6 Feature History for Device Discovery

Feature Name Discovery of various supported devices LLDP discovery Fibre Channel discovery Automatic logging-level configuration support

Releases 5.2(2a) 5.0(2) 5.0(2) 5.0(2)

Feature Information Support was added for this feature. Support was added for this feature. Support was added for this feature. Support was added for this feature.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

16-19

Chapter 16 Feature History for Device Discovery

Administering Device Discovery

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

16-20

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

17

Administering Devices and Credentials

This chapter describes how to administer Cisco NX-OS devices and the credentials that are used by the Cisco Data Center Network Manager for LAN (DCNM-LAN) server to authenticate itself to the devices. This chapter includes the following sections:

Information About Devices and Credentials, page 17-1 Licensing Requirements for Devices and Credentials, page 17-2 Prerequisites for Administering Devices and Credentials, page 17-3 Guidelines and Limitations for Devices and Credentials, page 17-3 Configuring Devices and Credentials, page 17-3 Viewing Device Credentials and Status, page 17-9 Field Descriptions for Devices and Credentials, page 17-10 Additional References for Devices and Credentials, page 17-11 Feature History for Devices and Credentials, page 17-11

Information About Devices and Credentials

This section includes the following topics:

Devices, page 17-1 Credentials, page 17-2 Device Status, page 17-2 VDC Support, page 17-2

Devices
The Devices and Credentials feature allows you to administer the management state of devices. If the managed physical device supports virtual device contexts (VDCs), DCNM-LAN represents each VDC as a device. If you need to retrieve the running configuration and status information of a single VDC on a physical device with multiple VDCs, rather than performing device discovery for all the VDCs on the physical device, you can use the Devices and Credentials feature to rediscover the single device that represents the changed VDC.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

17-1

Chapter 17 Licensing Requirements for Devices and Credentials

Administering Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Credentials
Devices and Credentials supports the ability to secure each managed device with different credentials. DCNM-LAN allows you to configure unique credentials for each discovered device or use default credentials when you do not configure unique credentials for a device. If some managed devices share the same credentials but others do not, you can configure unique credentials for some devices and configure the default credentials with the credentials that are shared by some of the managed devices. Devices and Credentials associates a unique set of device credentials with each DCNM-LAN server user which means that the accounting logs on managed devices reflect the actions of each DCNM-LAN server user. If you log into the DCNM-LAN client as a user who does not have device credentials configured, the DCNM-LAN client prompts you to configure device credentials for the user account. If support for accounting is not important to your organization, you must still configure each DCNM-LAN server user with device credentials, even if the credentials specified for each user are the same.

Device Status
The Devices and Credentials feature shows the status each device. The possible status are as follows:

ManagedDCNM-LAN can connect to the device using Secure Shell (SSH), configure the running configuration of the device, and retrieve logs and other data from it. This status is possible only for devices that run a supported release of Cisco NX-OS and that are configured properly to support discovery by DCNM-LAN. For more information, see the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8. UnmanagedDCNM-LAN does not manage the device or monitor the status of the device. UnreachableDCNM-LAN cannot connect to the device, which was a managed device prior to becoming unreachable. Common causes for this status are as follows:
A network issue is preventing the DCNM-LAN server from contacting the device. SSH is disabled on the device. All terminal lines on the device are in use.

VDC Support
For devices that support VDCs, DCNM-LAN treats each VDC on a physical device as a separate device; therefore, DCNM-LAN can maintain unique credentials for each VDC on a device. DCNM-LAN tracks the status of each VDC separately, as well.

Licensing Requirements for Devices and Credentials

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement Device and Credentials requires no license. Any feature not included in a license package is bundled with the Cisco DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Cisco DCNM Fundamentals Guide, Release 6.x

17-2

OL-25174-02OL-25174-02

Chapter 17

Administering Devices and Credentials Prerequisites for Administering Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Prerequisites for Administering Devices and Credentials

Performing device discovery with the Devices and Credentials feature has the following prerequisites:

The DCNM-LAN server must be able to connect to a device that you want to discover. Cisco NX-OS devices must be running a supported release of Cisco NX-OS. For information about supported releases of Cisco NX-OS, see the Cisco DCNM Release Notes, Release 5.x. The Cisco NX-OS device must have the minimal configuration that is required to enable device discovery to succeed. For more information, see the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8.

Guidelines and Limitations for Devices and Credentials

The Devices and Credentials feature has the following configuration guidelines and limitations:

Discovering a device by using the Devices and Credentials feature does not support CDP-based discovery of neighboring devices. To use CDP-based discovery, see the Administering Device Discovery section on page 16-1. Be careful when you change the default credentials or device-specific credentials. Incorrect credentials prevent DCNM-LAN from managing devices.

Configuring Devices and Credentials

This section includes the following topics:

Adding a Device, page 17-3 Discovering a Device, page 17-4 Unmanaging a Device, page 17-5 Deleting a Device, page 17-5 Configuring Default Device Credentials, page 17-6 Clearing Default Device Credentials, page 17-7 Configuring Unique Credentials for a Device, page 17-7 Clearing Unique Credentials for a Device, page 17-8

Adding a Device
You can add a device. After you add a device, you can discover it. For more information, see the Discovering a Device section on page 17-4.

BEFORE YOU BEGIN

Determine the IPv4 address for the device. Determine whether DCNM-LAN can communicate with the device using the default device credentials or whether you need to add unique device credentials when you add the device to DCNM-LAN.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

17-3

Chapter 17 Configuring Devices and Credentials

Administering Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials. The discovered devices appear in the Devices area of the Contents pane. From the menu bar, choose Actions > New Device. A blank row appears in the Devices area on the Contents pane. In the IP Address column for the new device, enter the IPv4 address that DCNM-LAN must use to connect to the device. Press Enter. (Optional) If you need to add unique device credentials, in the User Credentials column, double-click the entry for the device that you added, click the down-arrow button, and configure the unique device credentials. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server. The status of the new device is Unmanaged.

Step 2

Step 3 Step 4 Step 5

Step 6

Discovering a Device
You can discover a device. Discovering an unmanaged device changes its status to Managed. During the discovery, DCNM-LAN retrieves the running configuration of the device. If you are rediscovering a device, the configuration data that DCNM-LAN retrieves replaces any existing configuration data for the device. Whenever the configuration data that DCNM-LAN has for the device is not accurate, such as when a device administrator has used the command-line interface to change the running configuration, you can use this procedure to update the configuration data that DCNM-LAN has for the device.

Note

Discovering a device does not affect the running configuration of the device.

BEFORE YOU BEGIN

Ensure that you have either configured the device entry with unique device credentials or that DCNM-LAN can use the default device credentials to connect to the device. For more information, see the Configuring Default Device Credentials section on page 17-6.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials. The discovered devices appear in the Devices area of the Contents pane. Click the device that you want to discover. From the menu bar, choose Actions > Discover. The device discovery begins. The status of the device changes to Discovering.

Step 2 Step 3

Cisco DCNM Fundamentals Guide, Release 6.x

17-4

OL-25174-02OL-25174-02

Chapter 17

Administering Devices and Credentials Configuring Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 4

Wait for the status to change to Managed. Typically, the device discovery occurs in less than 5 minutes. After the status changes to Managed, you can use DCNM-LAN to configure the device. You do not need to save your changes.

Unmanaging a Device
You can change the status of a device to unmanaged.

BEFORE YOU BEGIN

Ensure that you are changing the status of the correct device. DCNM-LAN cannot control the running configuration of an unmanaged device.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials. The discovered devices appear in the Devices area of the Contents pane. Click the device whose status you want to change to unmanaged. From the menu bar, choose Actions > Unmanage. After a short delay, the status of the device changes to Unmanaged. You do not need to save your changes.

Step 2 Step 3

Deleting a Device
You can delete a device. When you delete a device, you delete all configuration data about the device from DCNM-LAN. You should consider deleting devices that you do not intend to manage with DCNM-LAN. Additionally, if a network administrator of a device that supports VDCs uses the command-line interface of the device to delete a VDC, you should delete from DCNM-LAN the device that represented the VDC.

Note

Deleting a device does not affect the running configuration of the device.

BEFORE YOU BEGIN

Ensure that you are deleting the correct device.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials. The discovered devices appear in the Devices area of the Contents pane.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

17-5

Chapter 17 Configuring Devices and Credentials

Administering Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2 Step 3

Click the device that you want to delete. From the menu bar, choose Actions > Delete. The device disappears from the Devices area. You do not need to save your changes.

Configuring Default Device Credentials

You can configure the default credentials, which DCNM-LAN uses to authenticate itself when it connects to discovered Cisco NX-OS devices. DCNM-LAN uses the default device credentials to communicate with each discovered device that you have not configured with unique device credentials.

Note

Device credentials are unique for each DCNM-LAN server user.

BEFORE YOU BEGIN

Determine what the default device credentials should be. All Cisco NX-OS devices that DCNM-LAN uses the default credentials to communicate with must have a network administrator account configured with a username and password that are identical to the default credentials that you configure in DCNM-LAN.

Note

We recommend that you use a strong password. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials. The Default Credentials area appears in the Contents pane, above the Devices area, which lists the discovered devices.

Step 2

In the User Name field, enter the username for the default credentials. A valid username can be 1 to 32 characters. Valid characters are numbers, symbols, and case-sensitive letters.

Note Step 3 Step 4

Cisco NX-OS supports usernames that are a maximum of 28 characters.

To the right of the Password field, click the down-arrow button. In the Password field and the Confirm Password field, enter the password for the default credentials. Valid passwords are numbers, symbols, and case-sensitive letters.

Note Step 5

Cisco NX-OS supports passwords that are a maximum of 64 characters.

Click OK.

Cisco DCNM Fundamentals Guide, Release 6.x

17-6

OL-25174-02OL-25174-02

Chapter 17

Administering Devices and Credentials Configuring Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 6

From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Clearing Default Device Credentials

You can clear the default device credentials.

Note

If you clear the default device credentials, DCNM-LAN can connect to discovered devices only if you have configured unique credentials for each managed device.

BEFORE YOU BEGIN

If you intend to use DCNM-LAN without default device credentials, you should ensure that DCNM-LAN is configured with unique device credentials for each discovered device before you perform this procedure. For more information, see the Configuring Unique Credentials for a Device section on page 17-7.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials. The Default Credentials area appears in the Contents pane, above the Devices area, which lists the discovered devices.

Step 2

In the Default Credentials area, click Clear. The User Name field and the Password field clear. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 3

Configuring Unique Credentials for a Device

You can configure credentials that are unique to a discovered device. When unique credentials exist for a discovered device, DCNM-LAN uses them when it connects to the device rather than using the default device credentials.

Note

Device credentials are unique for each DCNM-LAN server user.

BEFORE YOU BEGIN

Determine the username and password for a network administrator user account on the discovered device.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

17-7

Chapter 17 Configuring Devices and Credentials

Administering Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

We recommend that you use a strong password. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials. The discovered devices appear in the Devices area of the Contents pane. In the User Credentials column for the device, double-click the entry and then click the down-arrow button. In the User Name field, enter the username. Valid usernames are between 1 and 32 characters. Valid characters are numbers, symbols, and case-sensitive letters.

Step 2 Step 3

Note Step 4

Cisco NX-OS supports usernames that are a maximum of 28 characters.

In the Password field and the Confirm Password field, enter the password. Valid passwords are numbers, symbols, and case-sensitive letters.

Note Step 5 Step 6

Cisco NX-OS supports passwords that are a maximum of 64 characters.

Click OK. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Clearing Unique Credentials for a Device

You can clear unique credentials for a discovered device.

Note

If you clear the unique credentials for a discovered device, DCNM-LAN uses the default credentials to connect to the device.

BEFORE YOU BEGIN

If you intend to operate DCNM-LAN without unique credentials for the device, you should ensure that DCNM-LAN is configured with default device credentials before you perform this procedure. For more information, see the Configuring Default Device Credentials section on page 17-6.

Cisco DCNM Fundamentals Guide, Release 6.x

17-8

OL-25174-02OL-25174-02

Chapter 17

Administering Devices and Credentials Viewing Device Credentials and Status

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials. Discovered devices appear in the Devices area of the Contents pane. In the User Credentials column for the device, double-click the entry and then click the down-arrow button. In the User Name field, delete all text. In the Password field, delete all text. In the Confirm Password field, delete all text. Click OK. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

Viewing Device Credentials and Status

To view the status for devices and whether credentials are configured for the device, from the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials. The default credentials appears in the Default Credentials area in the Contents pane. Information about devices, including credentials and status, appear in the Devices area in the Contents pane. The Reason field provides a brief message that explains the device status. The following table provides information about how to resolve the issue indicated by the message. Reason Success Authentication failure Unsupported platform Resolution Not applicable. DCNM-LAN is managing the device. Ensure that the credentials are correct for the device. Ensure that DCNM-LAN can reach the device. Verify that the device is a supported platform and that it is running a supported release of Cisco NX-OS. For information about supported platforms and Cisco NX-OS releases, see the Cisco DCNM Release Notes, Release 5.x. Cisco Nexus 7000 Series devices only. The sequence numbers of accounting and system message log messages are not in a proper format. Clear the log files on the device and discover the device again. A DCNM-LAN user changed the device status to Unmanaged. Discover the device again. Discover the device again. If the error reoccurs, clean the DCNM-LAN database. For more information about cleaning the database, see Chapter 29, Maintaining the Cisco DCNM-LAN Database. Discover the device again. Discover the device again. For more information, see the Automatic Logging-Level Configuration Support section on page 16-5.

Device sync up failure

Unmanaged manually Error when executing database query

Auto synchronization for device is disabled by user Logging levels required by DCNM-LAN are not configured on the device

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

17-9

Chapter 17 Field Descriptions for Devices and Credentials

Administering Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Reason Error in SSH connection Unreachable Discovery failed because server node stopped/crashed Syslog messages logging disabled on device Resolution Ensure that SSH is enabled on the device and that it is functioning properly. Discover the device again. Ensure that you specify the correct IP address for the device. Ensure that DCNM-LAN can contact the device. Discover the device again. Discover the device again. Discover the device again.

For information about the fields that appear, see the Field Descriptions for Devices and Credentials section on page 17-10.

Field Descriptions for Devices and Credentials

This section includes the following field descriptions for Devices and Credentials:

Device and Credentials Content Pane, page 17-10

Device and Credentials Content Pane

Table 17-1 Device and Credentials Content Pane

Field
Default Credentials

Description Name of the Cisco NX-OS device user account that the DCNM-LAN server uses to access any device that it is discovering or that it is managing. On the device, the user account must be assigned to the network-admin or vdc-admin role. By default, this field is blank.
Note

User Name

The information in the User Credentials field in the Devices area overrides the information in the Default Credentials section.

Password
Devices

Password for the Cisco NX-OS device user account specified in the User Name field. By default, this field is blank. Display only. IPv4 address of the Cisco NX-OS device. Display only. Name of the Cisco NX-OS device. The Cisco NX-OS user account that DCNM-LAN uses to connect to the Cisco NX-OS device.
Note

IP Address Name User Credentials

If you configure this field, DCNM-LAN uses the user account that you configure when it connects to the device. If this field is blank, DCNM-LAN uses the user account specified in the Default Credentials area. By default, this field is blank.

Cisco DCNM Fundamentals Guide, Release 6.x

17-10

OL-25174-02OL-25174-02

Chapter 17

Administering Devices and Credentials Additional References for Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 17-1 Device and Credentials Content Pane (continued)

Field Status

Description Display only. Whether the DCNM-LAN server can connect to and configure the device. Valid values are as follows:

ManagedThe DCNM-LAN server can configure the device. UnmanagedThe DCNM-LAN server cannot configure the device. UnreachableThe DCNM-LAN server cannot reach the device.

Reason

Display only. Provides a brief explanation for the device status. For more information, see the Viewing Device Credentials and Status section on page 17-9.

Additional References for Devices and Credentials

For additional information related to the Devices and Credentials feature, see the following sections:

Related Documents, page 17-11 Standards, page 17-11

Related Documents
Related Topic Cisco NX-OS XML management interface Document Title Cisco NX-OS XML Interface User Guide

Standards
Standards NETCONF protocol over the Secure Shell (SSH) Title RFC 4742

Feature History for Devices and Credentials

Table 17-2 lists the release history for this feature.
Table 17-2 Feature History for Devices and Credentials

Feature Name Reason field

Releases 5.0(2)

Feature Information The Reason field was added to the Devices and Credentials feature.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

17-11

Chapter 17 Feature History for Devices and Credentials

Administering Devices and Credentials

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

17-12

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

18

Administering DCNM-LAN Licensed Devices

This chapter describes how to use the Cisco Data Center Network Manager for LAN (DCNM-LAN) Licensed Devices feature. This chapter includes the following sections:

Information About DCNM-LAN Licensed Devices, page 18-1 Licensing Requirements for Administering DCNM-LAN Licensed Devices, page 18-2 Prerequisites for Administering DCNM-LAN Licensed Devices, page 18-2 Guidelines and Limitations for Administering DCNM-LAN Licensed Devices, page 18-2 Configuring DCNM-LAN Licensed Devices, page 18-2 Viewing DCNM-LAN Licensed Devices, page 18-4 Field Descriptions for DCNM-LAN Licensed Devices, page 18-4 Additional References, page 18-5 Feature History for DCNM-LAN Licensed Devices, page 18-5

Information About DCNM-LAN Licensed Devices

The DCNM-LAN Licensed Devices feature allows you to control which physical devices you can manage with licensed DCNM-LAN features. The feature maintains a list of licensed devices. If a device is on this list, you can manage licensed DCNM-LAN features on the device. You can add as many devices to licenses as your licenses support. For example, if you install two LAN Enterprise licenses that each support five devices, you can add a total of ten devices to the list of licensed devices. You can also remove devices from the list of licensed devices and replace them with other devices. When you try to use a DCNM-LAN licensed feature to configure a device that you have not added to the list of licensed devices, the DCNM-LAN client does not allow you to use the feature to configure the unlicensed device.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

18-1

Chapter 18 Licensing Requirements for Administering DCNM-LAN Licensed Devices

Administering DCNM-LAN Licensed Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Licensing Requirements for Administering DCNM-LAN Licensed Devices

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement DCNM-LAN Licensed Devices requires an Enterprise LAN license. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Administering DCNM-LAN Licensed Devices

Administering DCNM-LAN Licensed Devices has the following prerequisites:

You must install one or more LAN Enterprise licenses. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. You must discover the devices that you want to add to the list of DCNM-LAN-licensed devices. For more information, see the Discovering Devices section on page 16-10.

Guidelines and Limitations for Administering DCNM-LAN Licensed Devices

Administering DCNM-LAN Licensed Devices has the following configuration guidelines and limitations:

You can add only managed devices to the list of licensed devices. You can add to the list of licensed devices only as many devices as permitted by all of the LAN Enterprise licenses that you have installed. When you remove a device from the list of licensed devices, the device is removed from DCNM-LAN. If the physical device supports virtual device contexts (VDCs), all the VDCs on the device are removed from DCNM-LAN. To continue managing the device, you must discover the device. For more information, see the Discovering Devices section on page 16-10.

Configuring DCNM-LAN Licensed Devices

This section includes the following topics:

Adding Devices to the Licensed Devices List, page 18-3 Removing Devices from the Licensed Devices List, page 18-3

Cisco DCNM Fundamentals Guide, Release 6.x

18-2

OL-25174-02OL-25174-02

Chapter 18

Administering DCNM-LAN Licensed Devices Configuring DCNM-LAN Licensed Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Adding Devices to the Licensed Devices List

You can add managed devices to the list of DCNM-LAN-licensed devices.

BEFORE YOU BEGIN

You must have installed at least one Cisco DCNM Enterprise LAN license. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. If you have already added as many devices as the maximum number of devices allowed by your licenses, you must remove one or more devices from the list of licensed devices before you can add other devices to the list. For more information, see the Removing Devices from the Licensed Devices List section on page 18-3.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > DCNM Licensed Devices. The Contents pane displays the list of licensed devices. From the menu bar, choose Actions > New. The DCNM-LAN client adds a row to the list and the Available Devices dialog box lists available and selected physical devices.

Step 2

Step 3 Step 4

From the Available Devices list, choose the physical devices that you want to add to the license and then click Add. Click OK. The Contents pane displays a list of licensed devices, including the devices that you added. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server. You can begin using licensed DCNM-LAN features when you manage the device.

Step 5

Removing Devices from the Licensed Devices List

You can remove one or more physical devices from the list of DCNM-LAN licensed devices when you no longer need to use licensed DCNM-LAN features to manage the devices.

Note

When you remove a physical device from the list of licensed devices, the device and all of its VDCs are removed from DCNM-LAN. To continue managing the device, you must discover the device. For more information, see the Discovering Devices section on page 16-10.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > DCNM Licensed Devices. The Contents pane displays the list of licensed devices. For each device that you want to remove from the list of licensed devices, follow these steps:
a.

Step 2

Choose the device that you want to remove from the list of licensed devices.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

18-3

Chapter 18 Viewing DCNM-LAN Licensed Devices

Administering DCNM-LAN Licensed Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
b.

From the menu bar, choose Actions > Delete. The DCNM-LAN client displays a confirmation dialog box. Click Yes. The DCNM-LAN client removes the device from the list of licensed devices.

c.

Note

Devices that you remove from the list of licensed devices are no longer managed by DCNM-LAN.

Step 3

(Optional) To continue managing devices that you removed from the list of licensed devices, discover the devices. For more information, see the Discovering Devices section on page 16-10.

Viewing DCNM-LAN Licensed Devices

To view the list of DCNM-LAN licensed devices, from the Feature Selector pane, choose DCNM Server Administration > DCNM Licensed Devices. The list of DCNM-LAN licensed devices appears in the Contents pane. For information about the fields that appear, see the Field Descriptions for DCNM-LAN Licensed Devices section on page 18-4.

Field Descriptions for DCNM-LAN Licensed Devices

This section includes the following field descriptions for DCNM-LAN Licensed Devices:

DCNM-LAN Licensed Devices Content Pane, page 18-4

DCNM-LAN Licensed Devices Content Pane

Table 18-1 DCNM-LAN Licensed Devices Content Pane

Field Total License Count

Description Display only. Sum of devices licensed by all Cisco DCNM Enterprise LAN licenses installed. For example, if you installed two licenses that each support 5 devices, this field would display 10. Display only. Sum of Nexus 7000 devices licensed (permanent license) by all Cisco DCNM Enterprise LAN licenses installed.

Total N7K Permanent License Count

Total N7K Trial License Display only. Sum of Nexus 7000 devices licensed (trial license) by all Cisco Count DCNM Enterprise LAN licenses installed. Total N5K, N4K, N3K, N1K License Count Total Remaining License Count Total Remaining N7K License Count Display only. Sum of Nexus 5000, Nexus 4000, Nexus 3000, and Nexus 1000 devices licensed by all Cisco DCNM Enterprise LAN licenses installed. Display only. Sum of remaining licenses Display only. Sum of remaining Nexus 7000 device licenses.

Cisco DCNM Fundamentals Guide, Release 6.x

18-4

OL-25174-02OL-25174-02

Chapter 18

Administering DCNM-LAN Licensed Devices Additional References

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 18-1 DCNM-LAN Licensed Devices Content Pane (continued)

Field Total Remaining N5K, N4K, N3K, N1K License Count Switch Name Virtual Devices

Description Display only. Sum of remaining Nexus 5000, Nexus 4000, Nexus 3000, and Nexus 1000 device licenses. Display only. Name of a licensed physical device. You can use licensed DCNM-LAN features on the device. Display only. Each virtual device context (VDC) that is configured on the physical device. If the physical device does not support VDCs, this field is empty.

Additional References
For additional information related to administering DCNM-LAN Licensed Devices, see the following sections:

Related Documents, page 18-5 Standards, page 18-5

Related Documents
Related Topic Installing a Cisco DCNM Enterprise LAN license Document Title Cisco DCNM Installation and Licensing Guide, Release 5.x

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Feature History for DCNM-LAN Licensed Devices

Table 18-2 lists the release history for this feature.
Table 18-2 Feature History for DCNM-LAN Licensed Devices

Feature Name DCNM-LAN Licensed Devices

Releases 5.0(2)

Feature Information No change from Release 4.2.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

18-5

Chapter 18 Feature History for DCNM-LAN Licensed Devices

Administering DCNM-LAN Licensed Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

18-6

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

19

Working with Topology

This chapter describes how to use the Topology feature in Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Topology, page 19-1 Licensing Requirements for Topology, page 19-8 Prerequisites for Topology, page 19-8 Guidelines and Limitations, page 19-8 Using the Topology Feature, page 19-8 Related Documents, page 19-30 Feature History for Topology, page 19-31

Information About Topology

The Topology feature provides you with a topology map of supported Cisco NX-OS devices. The topology map also shows switches that run Cisco IOS software, such as the Catalyst 6500 series switches. For Nexus 7000 Series devices, the map shows details about virtual device contexts (VDCs). When Cisco Data Center Network Manager for LAN (DCNM-LAN) receives new information, the DCNM-LAN client updates the map dynamically. By default, updates occur once a minute. You can see changes occur to the status of links and devices, such as links going down or VDC creation, deletion, or modification. Because the map is always current, you can use it to troubleshoot ongoing network management issues. You can modify and save the layout of device icons. The map also provides you quick access to configuring features for a managed device. This section includes the following topics:

Map Views, page 19-2 Layouts, page 19-5 vPC Support, page 19-6 DCNM-SAN Support, page 19-6 FabricPath Support, page 19-6 Device Groups, page 19-7

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-1

Chapter 19 Information About Topology

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Network Servers, page 19-7

Map Views
The topology map includes four views of your topology as described in the following topics:

Physical View, page 19-2 PortChannel and vPC, page 19-3 Logical vPC View, page 19-4 L2 View, page 19-5

Physical View
The Physical View (see Figure 19-1) shows the physical connections between discovered devices. This is the default topology view.
Figure 19-1 Physical View of the Topology Map

Cisco DCNM Fundamentals Guide, Release 6.x

19-2

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Information About Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

PortChannel and vPC

The PortChannel and vPC view (see Figure 19-2) shows all physical connections and all logical connections among discovered devices, including port channel links, virtual port channel (vPC) links, and vPC peer links. Physical links appear in gray in this view.
Figure 19-2 PortChannel and vPC View of the Topology Map

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-3

Chapter 19 Information About Topology

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Logical vPC View

The Logical vPC View (see Figure 19-3) shows vPC links and vPC peer links among discovered devices, without showing the physical connections.
Figure 19-3 Logical vPC View of the Topology Map

Cisco DCNM Fundamentals Guide, Release 6.x

19-4

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Information About Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

L2 View
The L2 view (see Figure 19-4) shows VLANs configured among discovered devices. Beginning with Cisco DCNM-LAN Release 5.1, the VSAN Overlay is a part of the L2 view. The VSAN Overlay feature enables you to view the Fibre Channel (FC) and Fibre Channel over Ethernet (FCoE) links that are active for a given VSAN or a range of VSANs. It also provides a visual representation of forwarding and non-forwarding links between Cisco Nexus devices in a data center network for configured VLANs.
Figure 19-4 L2 View of the Topology Map

Layouts
The topology map enables you to move devices to where you want them. You can save the layout so that the next time you use the topology map, devices are where you placed them. The DCNM-LAN client saves topology layouts as local user data on the computer that runs the DCNM-LAN client. When you are using the DCNM-LAN client, you do not have access to topology layouts that you saved on other computers or that you saved while logged in to the computer under a different username. In addition to saved layouts, when you are using the Physical View, you can load one of the following layouts:

SpringDevices appear in locations determined by weighting the connections, which often produces a layout with minimal or no crossed connections. TreeDevices appear in a tree unless connections create loops among the devices, in which case devices appear in a spanning tree, that is, a grid in which most of the connections follow the grid layout.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-5

Chapter 19 Information About Topology

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

vPC Support
The topology map provides the following additional vPC-specific features:

vPC creationYou can launch the vPC Creation Wizard from the PortChannel and vPC view. See the Launching the vPC Wizard section on page 19-28. Quick access to the vPC featureYou can access the configuration for a specific vPC from the PortChannel and vPC view or the Logical vPC View. See the Managing a vPC section on page 19-28. vPC configuration inconsistencyYou can see vPC links and vPC peer links that have configuration inconsistencies. You can open the Resolve Configuration Consistency dialog box from the topology map. See the Finding and Resolving vPC Configuration Inconsistencies section on page 19-29.

DCNM-SAN Support
The DCNM-LAN topology map supports Cisco Data Center Network Manager for SAN (DCNM-SAN) by providing the features described in the following topics:

Common Topology, page 19-6 Access to DCNM-SAN Features, page 19-6

Common Topology
The topology map can show storage area network (SAN) connections and devices in addition to Ethernet LAN connections and devices. You can use the DCNM-LAN topology map to view your entire data center network.

Access to DCNM-SAN Features

When a SAN device, such as a Cisco MDS 9000 Family Multilayer Switch, appears in the topology map in the DCNM-LAN client, you can use the topology map to launch the Cisco DCNM-SAN client and configure the SAN device. The Cisco DCNM-SAN cross launch feature is only supported by the DCNM-LAN client when the Cisco DCNM-SAN is installed in Server mode. Cross launch is not supported by the DCNM-LAN client when the Cisco DCNM-SAN is installed in Standalone mode. In addition, cross launch is not supported when the DCNM-LAN client is in standalone mode. For information about installing the DCNM-LAN client in standalone mode, see Chapter 13, Installing and Launching the Cisco DCNM-LAN Client. For information about installing Cisco DCNM-SAN and DCNM-LAN on the same server system, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

FabricPath Support
FabricPath support for L2MP capable devices, running the L2MP-ISIS protocol, is available in the L2 View of the Topology drawer. The L2 View contains a dialog box that allows you to select the type of graph to display. When you select the Fabricpath view in the dialog box, you can display the following types of graphs:

Cisco DCNM Fundamentals Guide, Release 6.x

19-6

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Information About Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Multi-destination A multi-destination or broadcast graph represents broadcast traffic and unknown unicast traffic in the topology.

Reachability L2MP-ISIS automatically computes the switch ID reachability for each node in the network. Unicast A unicast graph displays equal cost routes between nodes in a network. Multicast A multicast graph displays the multicast traffic from a specified device to all hosts that are listening to a particular IGMP group.

In addition, the FabricPath Topology Wizard can be launched from the L2 View. The FabricPath Topology Wizard allows you to do many operations, such as add to the FabricPath topology, display inventory, and display end devices.

Note

The FabricPath Topology Wizard is not supported in Cisco NX-OS Release 5.1(1).

Note

Starting from Cisco DCNM Release 6.1(1) the fabric path suppport feature will be available for the Cisco Nexus 55xx series switches. Starting from Cisco DCNM Release 6.1(1) the fabric path suppport feature will be licensed.

To launch the wizard, you need to select more than one device and right-click to display a context menu that lists the available operations. You can select multiple devices by holding down the shift key and clicking on the appropriate devices displayed on the graph. Alternatively, you may hold down the left mouse key and drag over the appropriate devices.

Device Groups
Device groups allow you to simplify the visualization of interconnections between groups of devices in the topology map. You can categorize devices into device groups that you define, which allows you to focus on a limited number of devices when you view the topology. You can manage device groups using the topology map, which allows you to create groups, delete groups, and move devices among groups; however, the Device Groups feature is especially useful for assigning multiple devices to groups easily. For more information about device groups, see Chapter 21, Configuring Device Groups.

Network Servers
The topology map can show network servers. You can use the Network Servers feature to associate host bus adapters (HBAs) and Ethernet network adapters that DCNM-LAN discovered with the Link Layer Discovery Protocol (LLDP) to network servers. For more information, see Chapter 20, Configuring Network Servers.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-7

Chapter 19 Licensing Requirements for Topology

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Licensing Requirements for Topology

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement The Topology feature requires no license; however, the Logical vPC View of the topology map requires a LAN Enterprise license. Any feature not included in a license package is bundled with the Cisco DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Topology

Topology has the following prerequisites:

The topology map shows only devices that DCNM-LAN has discovered. For full support on the topology map, discovered devices should have the applicable discovery protocols enabled, both globally and on active interfaces. For more information about the discovery protocols used by DCNM-LAN, see Chapter 16, Administering Device Discovery.

Guidelines and Limitations

Topology has the following configuration guidelines and limitations:

While the Topology feature is an unlicensed feature, you must have a LAN Enterprise license to manage the nondefault VDCs of Cisco Nexus 7000 Series switches that appear in the topology. The Topology feature displays changes to the topology periodically as determined by the polling frequency for accounting and system logs. By default, the polling frequency is one minute. For more information, see the Information About Auto-Synchronization with Devices section on page 23-1.

Using the Topology Feature

This section includes the following topics:

Opening the Topology Map, page 19-9 Understanding Device Icons and Links, page 19-10 Using the Viewing Tools, page 19-12 Showing, Hiding, and Using the Details Pane, page 19-13 Moving Devices in the Topology Map, page 19-14 Loading a Layout, page 19-15 Reloading the Previously Saved Layout, page 19-16 Showing a Virtual or Physical Chassis, page 19-16 Showing or Hiding Network Servers, page 19-17 Managing a Network Server, page 19-17

Cisco DCNM Fundamentals Guide, Release 6.x

19-8

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Showing or Hiding Device Groups, page 19-18 Expanding or Collapsing Device Groups, page 19-18 Creating a Device Group, page 19-19 Moving a Device Between Device Groups, page 19-19 Removing a Device from a Device Group, page 19-20 Copy Run to Start, page 19-21 Deleting a Device Group, page 19-22 Exporting the Topology as a JPG Image, page 19-22 Accessing DCNM-LAN Features from the Topology Map, page 19-23 Accessing Cisco DCNM-SAN Features from the Topology Map, page 19-24 Accessing Cisco FabricPath Features from the Topology Map, page 19-25 Launching the vPC Wizard, page 19-28 Managing a vPC, page 19-28 Finding and Resolving vPC Configuration Inconsistencies, page 19-29 Accessing Remotely Connected CNAs from the Topology Map, page 19-29 Using VSAN Overlay, page 19-30

Opening the Topology Map

You can open the topology map to view the topology of discovered devices.

Note

Before discovery, if you are working with FabricPath, you must use the Command-Line-Interface (CLI) to accomplish the following:

Install the Enhanced Layer 2 license on the device. See the Cisco NX-OS Licensing Guide for complete information on installing this license. Install the FabricPath feature set on the device. See the Cisco Configuring Feature Set for FabricPath Guide for complete information on installing the feature set. Configure the FabricPath feature set so that it can be enabled in a custom VDC. See the Cisco Configuring Feature Set for FabricPath Guide for complete information on configuring the feature set.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. Buttons for each of the available topology views appear above the topology map.

Step 2

(Optional) If you want to change topology views, click the topology view name. The topology map shows the view of the topology that you selected. (Optional) If you want to use a view-specific option, see the following table:

Step 3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-9

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

View Feature Show/Hide all VDCs

Available In View

How to Use Right-click in the map and choose Show All VDCs or Hide All VDCs. When you view all VDCs, Cisco Nexus 7000 Series devices appear as gray boxes that contain device icons for each VDC configured on the Cisco Nexus 7000 Series device.

Physical View

Show/Hide End Devices Filter VLANs

Physical View L2 View L2 View

Right-click in the map and choose Show End Devices or Hide End Devices.
1.

If the VLANs box does not appear on the map, click the Filter icon on the topology toolbar. Enter a list of VLAN IDs. You can specify a single VLAN ID, a range of VLAN IDs, or comma-separated IDs and ranges. Click Filter. On the map, find the VLANs box. Check or uncheck the Show Non-Forwarding Link (Blocking & Disabled) as needed. On the map, find the gray box that contains the Show vPC check box and the Show Port Channel check box. You may need to scroll the map or zoom out to find the gray box. Check or uncheck the check boxes as needed.

2.

3.

Show/Hide non-forwarding links

L2 View

1. 2.

Show/Hide vPCs or port channels

PortChannel and vPC

1.

2.

Understanding Device Icons and Links

To understand the device icons and links shown in the topology map, you can open the legend. The legend presents information about the device icons and links shown in the currently selected topology view.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. Buttons for each of the available topology views appear above the topology map.

Step 2

(Optional) If you want to change topology views, click the topology view name.

Cisco DCNM Fundamentals Guide, Release 6.x

19-10

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The topology map shows the view of the topology that you selected. The topology toolbar appears on the left side of the topology map.
Step 3

From the topology toolbar, click the

icon.

The Legend dialog box displays information about the device icons and links that may appear in the currently selected topology view.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-11

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Using the Viewing Tools

You can use the pan, select, zoom, and search tools to view the topology map. The following table describes the viewing tools that are available in the topology toolbar, which is on the left side of the topology map. Viewing Tool Icon and Name Pan

How to Use Moves, or pans, the map.

1. 2. 3. 4.

Click the

icon.

Click anywhere on the topology map, and hold down the mouse button. Drag the map in any direction. Release the mouse button. Click the icon.

Select

Allows you to select a device, link, or port icon.

1. 2.

Click the device, link, or port icon that you want to work with. A balloon displays information about the icon that you clicked.

Zoom in Rect

Zooms to a specific portion of the map.

1. 2.

Click the

icon.

Click on the map and drag a rectangle over the area that you want to see, and release the mouse button. icon. icon.

Zoom In Zoom Out Fit to View Reset Zoom Load Layout Reload Layout Show Device Groups Search

Zooms in. Click the Zooms out. Click the

Fits the entire topology of discovered devices within the topology map. Click the icon. Resets the zoom to the default magnification. Click the Loads a layout. Loads the most recently saved layout. See the Reloading the Previously Saved Layout section on page 19-16. Shows or hides device groups. See the Showing or Hiding Device Groups section on page 19-18. Allows you to use the device search tool, so that you can search for a device by its name.
1. 2. 3. Tip

icon.

To show the Search tool on the map, click the

icon.

In the Device box, enter all or some of the name of the device that you want to search for, and then click the icon. To hide the Search tool, click the icon again. You can move the Search tool on the topology map by clicking and dragging it when you have the Select tool enabled.

Save Layout

Saves changes that you have made to the device icon layout. See the Moving Devices in the Topology Map section on page 19-14.

Cisco DCNM Fundamentals Guide, Release 6.x

19-12

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Viewing Tool Icon and Name Hide/Show Details Legend Export as JPG

How to Use Shows and hides the details pane. See the Showing, Hiding, and Using the Details Pane section on page 19-13. Opens the Legend dialog box. See the Understanding Device Icons and Links section on page 19-10. Saves the topology map as a JPG image file. See the Exporting the Topology as a JPG Image section on page 19-22.

Showing, Hiding, and Using the Details Pane

You can show or hide the Details pane within the topology map. When you are showing the Details pane, you can use the sections within the Details pane to learn about the devices and connections in the topology.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Tip

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear. icon.

Step 2

To show or hide details, click the

When you choose to show details, the Details pane appears between the topology toolbar and the topology map.

Tip Step 3

Ensure that the Select tool is selected. To select the Select tool, click the

icon.

To use the sections within the Details pane, see the following table: Section VDC View Available In

How to Use Explore the VDC View tree to see which Cisco Nexus 7000 Series devices contain VDCs. To see details about a device, click on it and see the Properties section. Explore the vPC tree to see a categorized listing of all logical connections in the topology map. To see details about a vPC, vPC peer link, or a port channel, click on it and see the Properties section.

Physical View L2 View Port Channel and vPC Logical vPC

vPC

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-13

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Section Overview Available In

How to Use
Tip

All views

To view the Overview section, you may need to click the Overview tab in the Properties section. The Overview and Properties sections share the same section title bar.

The Overview section shows a thumbnail view of the whole topology. A blue rectangle indicates the portion of the topology that is currently shown in the map.

To change which portion of the topology is shown in the map, in the overview, click where you want the map to show. To zoom in or out, click a corner of the blue rectangle and drag it until the map is enlarged or shrunk as you want. To view the Properties section, you may need to click the Properties tab in the Overview section. The Overview and Properties sections share the same section title bar. Do one of the following:
In the VDC View section, click on a physical or

Properties

All views

Tip

1.

virtual device.
In the vPC section, click on a logical connection. In the topology map, click on a device, link, or

port.
2.

In the Properties section, view the properties of the object that you selected.

Moving Devices in the Topology Map

You can move device icons that are shown in the topology map. The position of devices is shared by all the topology views, that is, if you move a device and then change to another topology view, the device remains where you moved it to. You can also save the layout, which you can reload later if you make additional changes and want to revert to your last save. For more information, see the Reloading the Previously Saved Layout section on page 19-16. The saved layout becomes the default layout that you see in the topology map when you start the DCNM-LAN client.

Cisco DCNM Fundamentals Guide, Release 6.x

19-14

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

The DCNM-LAN client saves topology layouts as local user data on the computer that runs the DCNM-LAN client. When you are using the DCNM-LAN client, you do not have access to topology layouts that you saved on other computers or that you saved while logged in to the computer under a different username.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear. icon.

Step 2 Step 3

From the topology toolbar, choose the

Find and move device icons as needed. To move an icon, click on the device icon, hold down the mouse button, drag the icon to the new location, and release the mouse button. You can zoom and pan as needed to find icons. For more information, see the Using the Viewing Tools section on page 19-12. (Optional) If you want to save the changes to the device icon layout, click the icon.

Step 4

Loading a Layout
When you are using the Physical View, you can choose to load a layout. The position of devices is shared by all the topology views. This behavior allows you to use any of the layouts in all views by loading the layout in the Physical View and then choosing another view.

Note

If you are using a different view than the Physical View, the icon on the topology toolbar acts the same as the icon. For information about using the icon, see the Reloading the Previously Saved Layout section on page 19-16.

BEFORE YOU BEGIN

Determine which physical devices, if any, that you want to specify as core switches. When you load a layout other than a saved layout, core switches appear at the top of the topology map, and devices that are one CDP hop from the core switches appear just below them.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-15

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2 Step 3

(Optional) For each physical device that you want to appear at the top of the layout, right-click on the device icon and choose Make as Core Switch. From the topology toolbar, click the The Layout drop-down list appears. icon.

Step 4

From the Layout drop-down list, choose the layout that you want to load. The Physical View of the topology map changes to the layout that you selected. Any devices that you specified as core switches appear at the top of the map, with devices that are one CDP hop away from the core switches appearing just below them.

Reloading the Previously Saved Layout

You can load the most recently saved layout. This feature allows you to undo changes to device placement that you have made since you last saved the layout.

Note

The DCNM-LAN client saves topology layouts as local user data on the computer that runs the DCNM-LAN client. When you are using the DCNM-LAN client, you do not have access to topology layouts that you saved on other computers or that you saved while logged in to the computer under a different username.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear. icon.

Step 2

From the topology toolbar, choose the

The topology map changes to the most recent layout that you saved.

Showing a Virtual or Physical Chassis

For a Cisco Nexus 1000V device, you can specify whether the topology map shows the virtual chassis or the physical chassis of the device. By default, the topology map shows the virtual chassis.

Cisco DCNM Fundamentals Guide, Release 6.x

19-16

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Step 2

Find the Cisco Nexus 1000V device icon. The topology map displays either the virtual chassis or the physical chassis. Right-click on the device icon and choose the applicable option:

Step 3

Show Virtual Chassis Show Physical Chassis

Showing or Hiding Network Servers

You can show or hide the network servers that are connected to a specific device. By default, the topology map hides network servers.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Step 2 Step 3

Find the device that is connected to network servers that you want to show or hide. Right-click on the device and choose one of the following:

To show connected network servers, choose Show End Devices. To hide connected network servers, choose Hide End Devices.

Managing a Network Server

You can use the topology map to access the Network Servers feature for a network server that appears on the map.

BEFORE YOU BEGIN

The network server must be showing in the topology map.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-17

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2

Find the network server that you want to manage with the Network Servers feature.

Tip

If the network server does not appear on the map, right-click a device that it is connected to and choose Show End Devices.

Step 3

Right-click on the server and choose Manage Server. The DCNM-LAN client opens to the Network Servers feature. If the server that you chose represents a managed server or an Ethernet adapter on a discovered server, the client opens to the Servers contents pane. If the server that you chose represents a host bus adapter (HBA) that is not correlated or bound to a server, the client opens to the Static Server-Adapter Mapping contents pane.

Showing or Hiding Device Groups

You can show or hide device groups. When device groups are hidden, the topology map shows all discovered devices and connections. When your device groups are shown, you can expand and collapse device groups individually or all at once.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

The icon on the topology toolbar controls whether device groups appear on the topology map. When the icon appears to be pushed in, the topology map shows device groups. When the icon does not appear to be pushed in, the topology map hides device groups.
Step 2

Click the

icon to change between hiding and showing device groups, as needed.

Expanding or Collapsing Device Groups

You can expand and collapse individual device groups or all device groups.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View.

Cisco DCNM Fundamentals Guide, Release 6.x

19-18

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear. icon.

Step 2 Step 3

If device groups do not appear on the topology map, from the topology toolbar, click the Do one of the following:

If you want to expand a single device group, right-click on the device group icon and choose Expand Device Group. If you want to expand all device groups, right-click on a blank area of the map and choose Expand all Device Groups. If you want to collapse a single device group, right-click on the title of the device group and choose Collapse Device Group. If you want to collapse all device groups, right-click on a blank area of the map and choose Collapse all Device Groups.

Creating a Device Group

You can create a custom device group on the topology map.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2

Right-click on a blank area of the map and choose New Device Group. A dialog box appears, with a field for specifying a name for the new device group. Type a name for the device group and click OK. The new device group appears on the topology map.

Step 3

Moving a Device Between Device Groups

You can move devices from one device group to another device group on the topology map.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-19

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

If a device group is empty after you move a device out of the group, DCNM-LAN deletes the device group.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear. icon.

Step 2 Step 3 Step 4 Step 5 Step 6

If device groups do not appear on the topology map, from the topology toolbar, click the Find the device group that you want to move the device out of. If the device group is collapsed, double-click the device group to expand it. Right-click on the device that you want to move out of the group and choose Cut. Find the device group that you want to move the device into.

Tip Step 7

You do not need to expand the device group before moving the device into the group.

Right-click the device group and choose Paste.

Tip

If the device group is expanded, you must click on the title of the device group.

A warning dialog box confirms that you want to move the device group.
Step 8

Click Yes. DCNM-LAN adds the device to the second device group and removes it from the first device group. If the first device group is empty after moving the device, DCNM-LAN deletes the first device group.

Removing a Device from a Device Group

You can remove devices from a custom device group. All devices that you remove from a custom group are added to the default device group.

Cisco DCNM Fundamentals Guide, Release 6.x

19-20

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear. icon.

Step 2 Step 3 Step 4 Step 5

If device groups do not appear on the topology map, from the topology toolbar, click the Find the device group that you want to remove a device from. If the device group is collapsed, double-click the device group to expand it.

Right-click on the device that you want to remove from the group and choose Remove from Group. If you are removing the only device from the group, a warning dialog box confirms that you want to remove the device group.

Step 6

If the warning appears, click Yes. DCNM-LAN removes the device from the custom device group and adds the device to the default device group.

Copy Run to Start

In the Physical View, you can copy the running configuration to the startup configuration on one or more selected devices.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear. icon.

Step 2 Step 3 Step 4 Step 5 Step 6

If device groups do not appear on the topology map, from the topology toolbar, click the Above the topology map, select Physical View. Select the devices that you want to copy the running configuratiion from. If the device group is collapsed, double-click the device group to expand it. Right-click the device that you want to copy the running configuration from.

If you want to copy the running configuration to the startup configuration, choose Copy Run to Start. DCNM-LAN copies the running configuration to the startup configuration.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-21

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

If you want to copy the running configuration to a file in the bootflash directory, choose Copy Run to File in Bootflash. In the dialog box that appears, enter the name of the file to copy to and click OK to complete the operation. DCNM-LAN copies the running configuration to the specified file.

Deleting a Device Group

You can delete a custom device group from the topology map. Devices that belong to a custom device group that you delete automatically become members of the default device group.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear. icon.

Step 2 Step 3 Step 4

If device groups do not appear on the topology map, from the topology toolbar, click the Find the device group that you want to delete. Right-click on the device group and choose Delete Group.

DCNM-LAN removes the device group from the topology map. The devices that were in the deleted device group are now members of the default device group.

Note

If there are no custom device groups after you delete the device group, the topology map automatically hides devices groups because all devices are in the default device group.

Exporting the Topology as a JPG Image

You can export, or save, a JPG image of the topology map. You can export either the entire topology map or only the visible portion of the topology map.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Cisco DCNM Fundamentals Guide, Release 6.x

19-22

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2

View the portion of the topology map that you want to save. For more information, see the Using the Viewing Tools section on page 19-12. Arrange the device icons as desired. For more information, see the Moving Devices in the Topology Map section on page 19-14. From the topology toolbar, click the icon.

Step 3

Step 4

A dialog box prompts you to choose whether you want to export the entire topology map or only the visible portion of the map.
Step 5

Do one of the following:

To export the entire topology map as a JPG image, click Yes. To export only the visible portion of the topology map, click No.

Step 6

Specify the location and filename of the JPG image and click Save. The JPG image of the visible portion of the topology map is saved.

Accessing DCNM-LAN Features from the Topology Map

You can use the topology map to access other DCNM-LAN features for managed devices. From the topology map, you can access features that are found in the following Feature Selector drawers:

Inventory Virtual Devices Interfaces Routing Switching Security

You can also use the topology map to access the Device Discovery feature.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2

If you want to access a DCNM-LAN feature for a specific managed device, do the following:
a.

Find the device in the topology map.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-23

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
b.

Right-click the device and choose the feature that you want to configure. The feature that you selected appears in the Contents pane. The device that you selected on the topology map is selected in the Summary table for the feature.

Step 3

If you want to access the Device Discovery feature, right-click a blank area on the map and choose Discover Devices. The Device Discovery feature appears in the Contents pane.

Accessing Cisco DCNM-SAN Features from the Topology Map

You can use the topology map to access features in the Cisco DCNM-SAN client for a managed SAN device. If Cisco DCNM-SAN has not discovered the device, accessing the Cisco DCNM-SAN client through the topology map will cause Cisco DCNM-SAN to discover the SAN device. The Cisco DCNM-SAN features that you can access include the following:

Zones, zone sets, and zone set membership Port channel interfaces Fibre Channel physical and logical interfaces Fibre Channel over IP tunnels Events

Note

The Cisco DCNM-SAN cross launch feature is only supported by the DCNM-LAN client when the Cisco DCNM-SAN is installed in Server mode. Cross launch is not supported by the DCNM-LAN client when the Cisco DCNM-SAN is installed in Standalone mode. In addition, cross launch is not supported when the DCNM-LAN client is in standalone mode.

BEFORE YOU BEGIN

The Cisco DCNM-SAN client must be installed on the computer that is running the DCNM-LAN client.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2 Step 3

Find the SAN device in the topology map. Right-click the device and choose the feature that you want to configure. The Cisco DCNM-SAN client opens to the feature that you selected.

Cisco DCNM Fundamentals Guide, Release 6.x

19-24

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Accessing Cisco FabricPath Features from the Topology Map

You can use the topology map to access features of the Cisco FabricPath. This section includes the following topics:

Multi-destination, page 19-25 Device Reachability, page 19-25 Unicast, page 19-26 Multicast, page 19-27

Multi-destination
A multi-destination or broadcast graph represents broadcast traffic and unknown unicast traffic in the topolgy. You can view the multi-destination information for a specific topology.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2

Above the map, click L2 View. The dialog box appears in the Contents pane. In the dialog box, choose the Fabricpath view. Enter the Topology ID and click Fetch. The graph that is displayed is filtered based upon the Topology ID. Check Select type of graph to enable the selection for the Multi-destination graph. Check the Multi-destination option. From the Anchor drop-down list, choose a device. The selected device is the entry point for the graph. From the Graph ID drop-down list, choose an ID. The Graph ID is a forwarding tag for the graph. Click Fetch to view the graph.

Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9

Device Reachability
L2MP-ISIS automatically computes the switch ID reachability for each node in the network. You can view the reachability information for a specific topology.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-25

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2

Above the map, click L2 View. The dialog box appears in the Contents pane. In the dialog box, choose the Fabricpath view. Enter the Topology ID. The graph that is displayed is filtered based upon the Topology ID. Check Select type of graph to enable the selection for the Reachability graph. Check the Reachability option. From the Anchor drop-down list, choose a device. The selected device is the entry point for the graph. Click Fetch to view the graph.

Step 3 Step 4 Step 5 Step 6 Step 7 Step 8

Note

Devices in the graph that appear as red colored icons indicate that the device is not reachable for the selected topology.

Unicast
A unicast graph displays equal cost routes between nodes in a network. You can view the unicast information for a specific topology.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2

Above the map, click L2 View. The dialog box appears in the Contents pane. In the dialog box, choose the Fabricpath view. Enter the Topology ID. The graph that is displayed is filtered based upon the Topology ID. Check Select type of graph to enable the selection for the Unicast graph.

Step 3 Step 4 Step 5

Cisco DCNM Fundamentals Guide, Release 6.x

19-26

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 6 Step 7 Step 8 Step 9

Check the Unicast option. From the Anchor drop-down list, select a device. The selected device is the entry point for the graph. From the Destination drop-down list, select a device. The selected device is the destination for the graph. Click Fetch to view the graph.

Note

If the resulting graph does not trace the path from the source to the destination, then one of the following may be the cause:

Islands in the L2MP cloud. DCNM-LAN might not manage intermediate devices.

Multicast
A multicast graph displays the multicast traffic from a specified device to all hosts that are listening to a particular IGMP group. You can view the multicast information for a specific topology.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Note

To see the names of topology toolbar icons, move the mouse pointer to the icon and wait briefly for the name of the icon to appear.

Step 2

Above the map, click L2 View. The dialog box appears in the Contents pane. In the dialog box, choose the Fabricpath view. Enter the Topology ID. The graph that is displayed is filtered based upon the Topology ID. Check Select type of graph to enable the selection for the Multicast graph. Check the Multicast option. From the Anchor drop-down list, choose a device. The selected device is the entry point for the graph. From the Graph ID drop-down list, choose an ID. The Graph ID is a forwarding tag for the graph. In the Source field, enter the multicast originating device. The multicast originating device is specified as an IP address or as * (wildcard). In the IGMP field, enter the IGMP group address.

Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-27

Chapter 19 Using the Topology Feature

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 11 Step 12

In the VLAN field, enter multicast-associated VLAN information. Click Fetch to view the graph.

Launching the vPC Wizard

From the topology map, you can launch the vPC wizard to create a vPC.

BEFORE YOU BEGIN

Determine which two devices you want to use as the vPC peer switches.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. Above the map, click PortChannel and vPC. The map shows the PortChannel and vPC view of the topology. From the topology toolbar, choose the Press and hold the Shift key. Click the device that you want to use as a vPC peer switch. Right-click either device and choose Launch vPC Wizard. The vPC Creation Wizard dialog box appears. For more information about using this wizard, see the Interfaces Configuration Guide, Cisco DCNM for LAN, Release 5.x. icon.

Step 2

Step 3 Step 4 Step 5 Step 6 Step 7

Click one device that you want to use as a vPC peer switch.

Managing a vPC
From the topology map, you can access the vPC feature for a specific vPC link.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. Above the map, click one of the following views:

Step 2

PortChannel and vPC Logical vPC View

Step 3 Step 4

Find the vPC link for the vPC that you want to manage. Use the step that applies to the view that you selected:

Cisco DCNM Fundamentals Guide, Release 6.x

19-28

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Using the Topology Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

PortChannel and vPCRight-click the ellipse on the vPC link and choose Manage vPC. Logical vPC ViewRight-click the vPC link and choose Manage vPC.

The vPC feature appears. The vPC that you want to manage is selected in the summary table. For more information about the vPC feature, see the Interfaces Configuration Guide, Cisco DCNM for LAN, Release 5.x.

Finding and Resolving vPC Configuration Inconsistencies

You can use the topology map to find vPCs that have configuration inconsistencies and open the Resolve Configuration Inconsistency dialog box.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. Above the map, click one of the following views:

Step 2

PortChannel and vPC Logical vPC View

Step 3

Find the vPC for which you want to resolve configuration inconsistencies. If a vPC link has configuration inconsistencies, a red ellipse appears over the link. If you use the PortChannel and vPC view, vPC peer links with configuration inconsistencies also show a red ellipse.

Step 4

(Optional) If you want to resolve configuration inconsistencies now, do one of the following:

To resolve configuration inconsistencies for the vPC link and the vPC peer link, right-click the red ellipse on the vPC link and choose Launch Configuration Consistency. To resolve configuration inconsistencies for the vPC peer link only, right-click the red ellipse on the vPC link and choose Launch Configuration Consistency.

The Resolve Configuration Inconsistency dialog box opens. For more information about using the Resolve Configuration Inconsistencies dialog box, see the Interfaces Configuration Guide, Cisco DCNM for LAN, Release 5.x.

Accessing Remotely Connected CNAs from the Topology Map

You can use the topology map to access servers connected to Cisco Nexus 4000 Series switches.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. The topology toolbar appears on the left side of the topology map.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-29

Chapter 19 Related Documents

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 2

Right-click on the switch and then choose Show End Devices. The Contents pane displays all the servers that are connected to the switch. It displays only the pWWN of the servers because the IP address is not available as a part of the enode information in FIP snooping.

Using VSAN Overlay

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Topology > Topology View. The topology map appears in the Contents pane. Above the map, click L2 View. The dialog box appears in the Contents pane. In the dialog box, click VSAN. Enter the range to search (valid values are between 1 and 4094). Check View mapped VLANs to view the VLANs. Click Fetch.

Step 2

Step 3 Step 4 Step 5 Step 6

Related Documents
For additional information related to the topology map, see the following sections: Related Topic VDCs vPCs Configuring LLDP on managed devices Device discovery Device groups Network servers Document Title Virtual Device Context Configuration Guide, Cisco DCNM for LAN, Release 5.x Interfaces Configuration Guide, Cisco DCNM for LAN, Release 5.x System Management Configuration Guide, Cisco DCNM for LAN, Release 5.x Chapter 16, Administering Device Discovery Chapter 21, Configuring Device Groups Chapter 20, Configuring Network Servers

Cisco DCNM Fundamentals Guide, Release 6.x

19-30

OL-25174-02OL-25174-02

Chapter 19

Working with Topology Feature History for Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Feature History for Topology

Table 19-1 lists the release history for this feature.
Table 19-1 Feature History for Topology

Feature Name Common topology Network servers DCNM-SAN support Device groups VSAN Overlay

Releases 5.0(2) 5.0(2) 5.0(2) 5.0(2) 5.1(0)

Feature Information Support for SAN devices and connections was added. Support for showing network servers was added. Support for launching the Cisco DCNM-SAN client was added. Support for device groups was added. Support for VSAN overlay was added as a part of the L2 view. Support for discovering servers that are either directly connected to Cisco Nexus 5000 Series switches or CNAs. Support for FabricPath was added. Support for Datacenter Grouping was added.

Discovery of servers connected to Cisco Nexus 5.1(0) 5000 series switches via CNAs FabricPath support Datacenter Grouping 5.1(0) 6.0

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

19-31

Chapter 19 Feature History for Topology

Working with Topology

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

19-32

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

20

Configuring Network Servers

This chapter describes how to configure the Network Servers feature in Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Network Servers, page 20-1 Licensing Requirements for Network Servers, page 20-2 Prerequisites for Network Servers, page 20-3 Guidelines and Limitations for Network Servers, page 20-3 Configuring Network Servers, page 20-3 Viewing Server Connectivity Information, page 20-11 The Total Number Server Adapters label displays the number of servers available in network., page 20-12 Additional References, page 20-16 Feature History for Network Servers, page 20-17

Information About Network Servers

During device discovery, DCNM-LAN can discover the host bus adapters (HBAs) and Ethernet network adapters of the network servers that are connected to Cisco NX-OS devices in your network. DCNM-LAN uses the Link Layer Discovery Protocol (LLDP) to retrieve information about the Ethernet network adapters from network servers; however, the information retrieved by LLDP is not adequate for DCNM-LAN to determine if the discovered network adapters are part of the same network server. Beginning with DCNM-LAN Release 5.1, you can use DCNM-LAN to discover the servers for the following scenarios:

Servers having Converged Network Adapters (CNAs) that are directly connected to Cisco Nexus 5000 Series switches. Servers having CNAs that are connected to a Nexus 2000 which is in turn connected to Nexus 5000 Series switch. Servers having CNAs that are directly connected to Nexus 7000 Series switch.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

20-1

Chapter 20 Licensing Requirements for Network Servers

Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

Because LLDP is not supported on Nexus 2000 Series switches that are connected to Nexus 7000 Series switches, Cisco DCNM-LAN cannot discover servers having CNAs connected to Nexus 2000 Series switches which are in turn connected to Nexus 7000 Series switches. You can see the discovered CNA adapters in the Static Server-Adapter Mapping feature pane. DCNM-LAN does not allow you to automatically correlate adapters that are connected to Cisco Nexus 5000 Series switches via CNA. However, you can manually correlate the CNA adapters that belong to a network server. For more information about the discovery process, see Chapter 16, Administering Device Discovery. The Network Servers feature allows you to associate HBAs and Ethernet network adapters that DCNM-LAN discovered with LLDP to servers. The topology map can show the network servers that you define.

Note

DCNM-LAN supports discovery and management of VMware ESX servers (including the virtual machines that are hosted on the ESX servers), Linux servers, and Windows 2008 servers only. The Network Servers feature also allows you to view server connectivity information.

Automatic Correlation of Adapters to Servers

If you provide DCNM-LAN with a valid username and password that it can use to log into a network server, DCNM-LAN can automatically associate the network adapters of a network server, which allows DCNM-LAN to retrieve enough information from the network server to determine which discovered adapters are a part of the same network server. The DCNM-LAN topology view displays a graphical representation of the associations between adapters and servers. A network server is considered managed if DCNM-LAN can successfully log into the server and retrieve the connectivity information. To more easily manage your network servers, you can use the DCNM-LAN server correlation feature to set up the login credentials for multiple servers. You can configure multiple servers to use the same credentials or unique credentials for each server.

Manual Correlation of Adapters to Servers

If you cannot provide DCNM-LAN with credentials to log into a network server, you can manually correlate, or bind, adapters to a network server.

Licensing Requirements for Network Servers

The following table shows the licensing requirements for this feature:

Cisco DCNM Fundamentals Guide, Release 6.x

20-2

OL-25174-02OL-25174-02

Chapter 20

Configuring Network Servers Prerequisites for Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Product Cisco DCNM-LAN

License Requirement Network Servers requires no license. Any feature not included in a license package is bundled with the Cisco DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Network Servers

The Network Servers feature has the following prerequisites:

LLDP must be enabled on network servers. DCNM-LAN must have discovered the network adapters of a server before you can use the Network Servers feature to correlate adapters automatically or bind them manually to a server.

Guidelines and Limitations for Network Servers

The Network Servers feature has the following configuration guidelines and limitations:

DCNM-LAN can discover the network servers that run a Linux operating system. DCNM-LAN can automatically correlate the network servers for HBA ports that are manufactured by Emulex or Qlogic only. DCNM-LAN can automatically correlate the adapters on the Linux operating system and ESX servers only. DCNM-LAN supports CNAs that are manufactured by Emulex or Qlogic only. Because the CNA does not advertise the IP address of the server, you must manually correlate one CNA before you can trigger the automatic correlation of subsequent entries.

Configuring Network Servers

This section includes the following topics:

Configuring Default Server Credentials, page 20-4 Clearing Default Server Credentials, page 20-4 Configuring Unique Credentials for a Server, page 20-5 Clearing Unique Credentials for a Server, page 20-6 Correlating Servers, page 20-6 Correlating a Server to Adapters Automatically, page 20-9 Binding Adapters to a Server Manually, page 20-10 Unbinding an Adapter from a Server, page 20-10

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

20-3

Chapter 20 Configuring Network Servers

Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Configuring Default Server Credentials

You can configure the default server credentials, which DCNM-LAN uses to authenticate itself when it connects to a newly discovered server. DCNM-LAN uses the default server credentials to communicate with each discovered server that you have not configured with unique server credentials.

Note

Server credentials are unique for each DCNM-LAN user.

BEFORE YOU BEGIN

Determine what the default server credentials should be. All servers that DCNM-LAN uses the default server credentials to communicate with must have a user account configured with a username and password that are identical to the default server credentials that you configure in DCNM-LAN.

Note

We recommend that you use a strong password. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Servers > Server Credentials. The Server Credentials area appears in the Contents pane, above the Servers area, which lists the discovered servers.

Step 2 Step 3 Step 4 Step 5 Step 6

In the User Name field, enter the username for the default server credentials. A valid username can be 1 to 32 characters. Valid characters are numbers, symbols, and case-sensitive letters. To the right of the Password field, click the down-arrow button. In the Password field and the Confirm Password field, enter the password for the default credentials. Valid passwords are numbers, symbols, and case-sensitive letters. Click OK. From the menu bar, choose File > Deploy to save the default credentials.

Clearing Default Server Credentials

You can clear the default server credentials.

Note

If you clear the default server credentials, DCNM-LAN can connect to discovered servers only if you have configured unique credentials for each managed server.

Cisco DCNM Fundamentals Guide, Release 6.x

20-4

OL-25174-02OL-25174-02

Chapter 20

Configuring Network Servers Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
BEFORE YOU BEGIN
If you intend to use DCNM-LAN without default server credentials, you should ensure that DCNM-LAN is configured with unique server credentials for each discovered server before you perform this procedure. For more information, see the Configuring Unique Credentials for a Server section on page 20-5.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Servers > Server Credentials. The Server Credentials area appears in the Contents pane, above the Servers area, which lists the discovered servers.

Step 2

In the Default Credentials area, click Clear. The User Name field and the Password field clear. From the menu bar, choose File > Deploy to save your changes to the DCNM-LAN server.

Step 3

Configuring Unique Credentials for a Server

You can configure credentials that are unique to a discovered server. When unique credentials exist for a discovered server, DCNM-LAN uses them when it connects to the server rather than using the default server credentials.

Note

Server credentials are unique for each DCNM-LAN user.

BEFORE YOU BEGIN

Determine the username and password for a user account on the discovered server.

Note

We recommend that you use a strong password. Common guidelines for strong passwords include a minimum password length of eight characters and at least one letter, one number, and one symbol. For example, the password Re1Ax@h0m3 has ten characters and contains uppercase and lowercase letters in addition to one symbol and three numbers.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Servers > Server Credentials. The discovered servers appear in the Servers area of the Contents pane. In the User Credentials column for the server, double-click the entry and then click the down-arrow button. In the User Name field, enter the username. Valid usernames are between 1 and 32 characters. Valid characters are numbers, symbols, and case-sensitive letters. In the Password field and the Confirm Password field, enter the password. Valid passwords are numbers, symbols, and case-sensitive letters.

Step 2 Step 3 Step 4

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

20-5

Chapter 20 Configuring Network Servers

Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 5 Step 6

Click OK. From the menu bar, choose File > Deploy to save the server credentials to the DCNM-LAN server.

Clearing Unique Credentials for a Server

You can clear unique credentials for a discovered server.

Note

If you clear the unique credentials for a discovered server, DCNM-LAN uses the default credentials to connect to the server.

BEFORE YOU BEGIN

If you intend to operate DCNM-LAN without unique credentials for the server, ensure that DCNM-LAN is configured with default server credentials before you perform this procedure. For more information, see the Configuring Default Server Credentials section on page 20-4.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Servers > Server Credentials. Discovered servers appear in the Servers area of the Contents pane. In the Servers area, click the server that has credentials that you want to clear. From the menu bar, choose Actions > Clear Credentials. A confirmation dialog box appears. Click Yes. From the menu bar, choose File > Deploy to save your changes to the DCNM-LAN server.

Step 2 Step 3

Step 4 Step 5

Correlating Servers
Correlating servers helps you manage a range of servers. An operation performed on a range of servers applies the operation to all the servers in that range.

BEFORE YOU BEGIN

Ensure that the following have been confirmed and set for your appropriate platform.

For Windows Server 2003:

Only Windows Server 2003 R2 (5.2.3970 or higher version) is supported. WinRM system utility is installed.

(Available from Windows Server installation CD or Microsoft Support site.)

Telnet service is enabled and running. User level privileges are enabled.

Cisco DCNM Fundamentals Guide, Release 6.x

20-6

OL-25174-02OL-25174-02

Chapter 20

Configuring Network Servers Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
NICs have been identified.

To verify that the NICs have been identified, you can use the iponfig /all CLI command.
HBAs have been identified.

To verify that the HBAs have been identified, you can use the winrm e wmi/root/wmi/MSFC_FibrePortHBAAttributes CLI command.

Note

Command output may display an error if an HBA is not installed on the server. This is expected. Ignore the error.

For Windows Server 2008:

Windows Server 2008 Standard, Enterprise, and R2 (6.0.6001 or higher version) is supported. WinRM system utility is installed. Telnet service is enabled and running. User level privileges are enabled. NICs have been identified.

To verify that the NICs have been identified, you can use the iponfig /all CLI command.
HBAs have been identified.

To verify that the HBAs have been identified, you can use the winrm e wmi/root/wmi/MSFC_FibrePortHBAAttributes CLI command.

Note

Command output may display an error if an HBA is not installed on the server. This is expected. Ignore the error.

For RHEL:
RHEL 4.5 is supported. SSH is enabled. User level privileges are enabled. NICs have been identified.

To verify that the NICs have been identified, you can use the ifconfig -a CLI command.
HBAs have been identified.

To verify that Qlogic HBAs have been identified, you can use the grep adapter-port /proc/scsi/qla2xxx/* CLI command. To verify that Emulex HBAs have been identified, you can use the find /sys/class/scsi_host/ -name port_name and the find /sys/class/fc_host/ -name port_name CLI commands. View the consolidated information by using cat on the resulting files.

For VMware ESX:

ESX 3.5 or higher version is supported. SSH is enabled. NICs have been identified.

To verify that the NICs have been identified, you can use the esxcfg-nics -l CLI command.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

20-7

Chapter 20 Configuring Network Servers

Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
HBAs have been identified.

To verify that the HBAs have been identified, you can use the esxcfg-scsidevs -a CLI command.
HBAs and CNAs of Qlogic and Emulex have been tested and supported.

Note

For a virtual machine, the HBA information is not displayed in the virtual machine. In the virtual machine display, the SAN details are disabled for the virtual machine. The HBA information is displayed in the ESX. Device version support:
For Nexus 7000, LLDP is supported from 5.0. For Nexus 5000, LLDP is supported from4.2(1)N1(1). For Nexus 5000, FC is supported for all versions. For MDS, is supported from 3.3(2).

Table 20-1 summarizes the support by platform.

Table 20-1 Summary

Windows Server 2003 Supported NIC All Supported HBA Supported CNA Operating System Required service Authority Qlogic, Emulex Qlogic, Emulex R2 (All editions) 32 bit and 64 bit Telnet/ssh WinRM User level privileges

Windows Server 2008 All Qlogic, Emulex Qlogic, Emulex All editions 32 bit and 64 bit Telnet/ssh WinRM User level privileges

RHEL All Qlogic, Emulex Qlogic, Emulex RHEL 4.5 SSH/Telnet User level privileges

ESX All Qlogic, Emulex Qlogic, Emulex ESX 3.5 SSH/Telnet User level privileges

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Servers > Server Credentials. The discovered servers appear in the Servers area of the Contents pane. In the Servers pane, right-click to access the context menu. Choose New Server in the context menu. A new row for the server is displayed. In the IP Address field, enter the IP addresses of the range of servers. IP address are delimited with commas or hyphens. After the IP addresses are entered, the system validates the addresses. A red colored border indicates an error condition. A yellow colored border indicates a valid entry. Double-click the User Credentials field to access the Set User Credentials dialog box.

Step 2 Step 3 Step 4

Step 5

Cisco DCNM Fundamentals Guide, Release 6.x

20-8

OL-25174-02OL-25174-02

Chapter 20

Configuring Network Servers Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 6 Step 7 Step 8 Step 9 Step 10 Step 11

In the User Name field, enter the username. Valid usernames are between 1 and 32 characters. Valid characters are numbers, symbols, and case-sensitive letters. In the Password field and the Confirm Password field, enter the password. Valid passwords are numbers, symbols, and case-sensitive letters. Click OK. From the menu bar, choose File > Deploy to save the settings to the DCNM-LAN server. To start server correlation, right-click the row or a single server in the range to access the context menu. Choose Correlate in the context menu. The operation changes the status of each server to Discovering. When the operation completes, the adapters are bound to the servers. If the operation fails, the status of the server becomes Unreachable and is accompanied with a message.

Correlating a Server to Adapters Automatically

DCNM-LAN can log into servers that run a Linux operating system and use the network connectivity information that it retrieves to correlate HBA network adapters that it has detected to the Linux server.

BEFORE YOU BEGIN

You must configure valid server credentials for the server that you want DCNM-LAN to correlate with HBA adapters automatically. You can configure credentials unique to the server, or if the credentials are valid with other servers, too, you can configure default server credentials.

Note

If the server credentials are unavailable, you can bind the adapter to a server manually. For more information, see the Binding Adapters to a Server Manually section on page 20-10. DCNM-LAN must have discovered one or more HBA network adapters and one network server.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Servers > Servers. Discovered servers appear in the Servers area of the Summary pane. Under the Server column, click the server that you want to correlate with adapters automatically.

Step 2

Tip

If you want to correlate more than one server at a time, press and hold Ctrl and then click each server that you want to correlate with adapters.

Step 3

Right-click on the selected server(s) and choose Correlate Server(s). DCNM-LAN begins discovering network connectivity information from the selected server(s).

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

20-9

Chapter 20 Configuring Network Servers

Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
After discovery completes, the Connected Switches column shows any additional connections correlated to the server. The local topology shown to the right of the selected server is also updated to show any connections correlated with the server.

Binding Adapters to a Server Manually

DCNM-LAN allows you to associate HBA network adapters that it has detected to a discovered server. This process does not depend upon DCNM-LAN being able to log into the server and retrieve information from it. The connection between a managed device and the server can be displayed on the topology map after you have successfully bound the adapter to a server.

BEFORE YOU BEGIN

DCNM-LAN must have discovered one or more HBA network adapters. DCNM-LAN must be able to reach the server to which you want to bind the adapter, either by IP address or DNS name.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Servers > Static Server-Adapter Mapping. The Contents pane lists discovered HBA network adapters. Press and hold the Ctrl key and then click each adapter that you want to bind to a server. Right-click on any selected adapter and choose Bind to Server. The Enter Server Name dialog box appears In the Server Name field, enter the IP address or DNS name of the server, and then click OK. From the menu bar, choose File > Deploy to save your changes to the DCNM-LAN server. In the topology map, the connection between the adapter and the managed device is available for viewing when you choose to view the connections to end devices for the managed device.

Step 2 Step 3

Step 4 Step 5

Unbinding an Adapter from a Server

You can remove a server-adapter binding that you have created. This process does not depend upon DCNM-LAN being able to log into the server and retrieve information from it.

BEFORE YOU BEGIN

The server-adapter binding that you want to remove must exist in DCNM-LAN.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Servers > Static Server-Adapter Mapping.

Cisco DCNM Fundamentals Guide, Release 6.x

20-10

OL-25174-02OL-25174-02

Chapter 20

Configuring Network Servers Viewing Server Connectivity Information

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The Contents pane lists discovered HBA network adapters.
Step 2 Step 3

Under the Server Port column, click the adapter that you want to unbind. Right-click the adapter and choose Unbind from Server. The Server Name field for the selected adapter clears. From the menu bar, choose File > Deploy to save your changes to the DCNM-LAN server. In the topology map, the connection between the adapter and the managed device is no longer available for viewing.

Step 4

Viewing Server Connectivity Information

You can view connectivity information for the DCNM-LAN server.
Step 1

From the Feature Selector pane, choose Network Servers > Servers. The Summary pane lists discovered servers. In the Summary pane, click the server whose network connectivity information you want to view. The local topology for the server appears to the right of the Summary pane. (Optional) If you want to view Ethernet network or storage area network connectivity for the server, on the Server Details tab, expand the LAN Connectivity or SAN Connectivity section, as needed.

Step 2

Step 3

Viewing and Searching Network Servers

You can view and search the network servers that are connected to the Cisco NX-OS devices from the Cisco DCNM-LAN Client.

Note

The DCNM-LAN Client tracks only directly connected hosts to the discovered switches.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Server > End Hosts. The End Hosts summary appears in the Contents pane. The End Hosts summary displays the details of the network servers that are connected to the Cisco NX-OS devices. The information about the End Hosts is listed below.

Column Server Name VM Name MAC Address

Description Name of the server. VM name of the server.

Capability Read Read

MAC address of the server port. Read

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

20-11

Chapter 20 Viewing and Searching Network Servers

Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Column Server IP Address Switch Port VLAN ID Switch Name Last Seen Time Description IP address of the server. Port details. VLAN ID. Name of the switch. Capability Read Read Read Read

Displays the last seen time of Read the servers MAC address in the switch.

The Total Number Server Adapters label displays the number of servers available in network. Select the Enable End Hosts Discovery checkbox and click the deploy buttin to enable end hosts discovery. By default, the end host discovery is disabled. When you select enable end hosts discovery, end host discovery is executed every three hours for the following Cisco Nexus devices supported by Cisco DCNM:

Cisco Nexus 7000 Cisco Nexus 5000 Cisco Nexus 5500

The Current Page/Total Number of Pages label displays the current page and total count of pages.
Step 2 Step 3 Step 4 Step 5

From the Switch Port column, click on a port to navigate to the Ports panel and configure the port. (Optional) Click the first, previous, next, or the last button pages. (Optional) Enter the page number that you want to view in the Go to Page to navigate through the field.

(Optional) Click the Excel icon to export the data in a Microsoft Excel spreadsheet. You can chose to export either all server details or only the visible rows. When you see the prompt Do you want to export the all the servers?, click No to export only visible rows. (Optional) In the Filter By drop-down list, select the MAC address, Switch IP address, connected switch IP address, or VLAN ID and then click the magnifying glass to search the network server. (Optional) Select inactive hosts since from the drop-down list and provide the required date. All the inactive hosts from the date entered to the current date will be displayed.

Step 6 Step 7

Note

Once you filter the inactive servers, any of the inactive servers that becomes active in the switch will be removed from the filtered list. You can use the delete button to delete inactive servers. (Optional) You can change the polling interval by performing the following steps:
a.

Step 8

Under<USER_INSTALL_DIR>\dcm\ dcnm\data\hosttracking, locate the hosttracking.properties file. In the hosttracking.properties file, under the host_discovery_polling_interval_in_minutes field, enter the polling interval (in minutes).

Note

If Cisco DCNM is installed in VSB, by default, the hosttracking.properties file is located under /root/CSCOdcnm/data_archive/data/hosttracking. For example, HOST_DISCOVERY_POLLING_INTERVAL_IN_MINUTES=180

Cisco DCNM Fundamentals Guide, Release 6.x

20-12

OL-25174-02OL-25174-02

Chapter 20

Configuring Network Servers Field Descriptions for Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
b.

For the new polling interval to be in effect, in the End Hosts Discovery screen, disable end hosts discovery and enable end hosts discovery again with the new polling interval.

After you apply the filters in the End Hosts summary, any addition and deletion of network servers within the network are not displayed in the filtered list. To see those changes, you must either remove the filter and reapply or refresh the window. If the filtered result size exceeds the maximum number of sever rows per page, a dialog box appears warning you to change the filter criteria so that the number of rows is less than the maximum number of rows allowed per page.

Troubleshooting Host Tracking

By using the Cisco DCNM Web Client, you must discover the virtual servers that run VMware before discovering Cisco Nexus devices to which the virtual servers are connected. You can discover a server by using the Cisco DCNM Web Client.

DETAILED STEPS
Step 1

From the main menu bar, Admin > Data Sources > VMware.

You can discover a Cisco Nexus device by using the Cisco DCNM Web Client.

DETAILED STEPS
Step 1

From the main menu bar, Admin > Data Sources > LAN.

If a switch port that is connected to the server is down, the Cisco DCNM server removes that server entry from End Host page. If a switch port that is connected to the server is up, the DCNM server automatically detects the port and then triggers the server discovery and populates the MAC address table. The switch MAC address table does not have any host MAC addresses in the following scenarios:

There is no traffic flowing. The port connected to the server is down.

To track the hosts connected to the Switch, use the show mac address-table command.

Field Descriptions for Network Servers

This section includes the following field descriptions for the Network Servers feature:

Field Descriptions for Servers, page 20-14 Servers Summary Pane, page 20-14 Field Descriptions for Server Credentials, page 20-16

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

20-13

Chapter 20 Field Descriptions for Network Servers

Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Field Descriptions for Servers

This section includes the following field descriptions:

Servers Summary Pane, page 20-14 Server: Server Details: LAN Connectivity Section, page 20-14 Server: Server Details: LAN Connectivity Section, page 20-14

Servers Summary Pane

Table 20-2 Servers Summary Pane

Field Server Connected Switches Status

Description Display only. DNS name or IP address of the server. If DCNM-LAN could not determine the DNS name of the server, the IP address is shown instead. Display only. Name and IP address of each discovered device that is connected to the server. Display only. Whether the DCNM-LAN server can connect to and log into the server. Valid values are as follows:

ManagedDCNM-LAN has successfully logged into the server during automatic correlation of the server adapters. UnmanagedDCNM-LAN has not attempted to log into the server yet. By default, a discovered server is unmanaged until you attempt to correlate its adapters automatically. UnreachableDuring automatic correlation of the server adapters, DCNM-LAN could not reach the server or authentication failed. A message indicates the reason for the status.

Server: Server Details: LAN Connectivity Section

Table 20-3 Server: Server Details: LAN Connectivity Section

Field
Switch

Description Display only. Name and IP address of devices that the server is connected to with an Ethernet connection. Display only. Name of the Ethernet interface on the device, such as Ethernet1/2. Display only. MAC address of the Ethernet adapter on the server that is connected to the device. Display only. Name of the interface on the server.

Name Port Name

Server

MAC Address Port Name

Cisco DCNM Fundamentals Guide, Release 6.x

20-14

OL-25174-02OL-25174-02

Chapter 20

Configuring Network Servers Field Descriptions for Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Server: Server Details: SAN Connectivity Section

Table 20-4 Server: Server Details: SAN Connectivity Section

Field
Switch

Description Display only. Name and IP address of devices that the server is connected to with a Fibre Channel connection. Display only. World Wide Name (WWN) of the Fibre Channel interface on the device. Display only. Name of the Fibre Channel interface on the device, such as Fc1/4. Display only. World Wide Name of the HBA interface on the server.

Name FC Port WWN Port Name

Server

FC Port WWN

Field Descriptions for Static Server-Adapter Mapping

Table 20-5 Static Server-Adapter Mapping Contents Pane

Field Server Port

Description Display only. Identifies the server adapter, depending upon the adapter type, as follows:

For an HBA adapter, this field displays the WWN assigned to the adapter. For an Ethernet adapter, this field displays the MAC address of the adapter. Ethernet adapters appear on the Static Server-Adapter Mapping contents pane when the server does not advertise the IP address of the adapter in LLDP.

Server Name Vendor Switch Port Switch Name

DNS name or IP address of the network server that the adapter is bound to. Display only. Name of the manufacturer of the adapter. Display only. Name and WWN of the Fibre Channel interface on the connected device. Display only. Name and IP address of the connected device.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

20-15

Chapter 20 Additional References

Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Field Descriptions for Server Credentials

Table 20-6 Server Credentials Contents Pane

Field
Default Credentials

Description Name of the server user account that the DCNM-LAN server uses to access servers that it is discovering or that it is managing. On the server, the user account must have adequate permissions to retrieve information about the server network adapters.
Note

User Name

The information in the User Credentials field in the Servers area overrides the information in the Default Credentials section.

Password
Servers

Password for the server user account specified in the User Name field. By default, this field is blank. Display only. IPv4 address of the server. Display only. Name of the server. If DCNM-LAN cannot determine the name of the server, the IP address of the server is shown. Server user account that DCNM-LAN uses to connect to the server.
Note

IP Address Name User Credentials

If you configure this field, DCNM-LAN uses the user account that you configure when it connects to the server. If this field is blank, DCNM-LAN uses the user account specified in the Default Credentials area. By default, this field is blank.

Status

Display only. Whether the DCNM-LAN server can connect to and log into the server. Valid values are as follows:

ManagedDCNM-LAN has successfully logged into the server during automatic correlation of the server adapters. UnmanagedDCNM-LAN has not attempted to log into the server yet. By default, a discovered server is unmanaged until you attempt to correlate its adapters automatically. UnreachableDuring automatic correlation of the server adapters, DCNM-LAN could not reach the server or authentication failed. A message indicates the reason for the status.

Additional References
For additional information related to administering Network Servers, see the following sections:

Related Documents, page 20-17 Standards, page 20-17

Cisco DCNM Fundamentals Guide, Release 6.x

20-16

OL-25174-02OL-25174-02

Chapter 20

Configuring Network Servers Feature History for Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Related Documents
Related Topic Device discovery Topology map Document Title Chapter 16, Administering Device Discovery Chapter 19, Working with Topology

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Feature History for Network Servers

Table 20-7 lists the release history for this feature.
Table 20-7 Feature History for Network Servers

Feature Name Network Servers

Releases 5.0(2)

Feature Information Support was added.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

20-17

Chapter 20 Feature History for Network Servers

Configuring Network Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

20-18

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

21

Configuring Device Groups

This chapter describes how to configure the Device Groups feature in Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Device Groups, page 21-1 Licensing Requirements for Device Groups, page 21-2 Prerequisites for Device Groups, page 21-2 Guidelines and Limitations for Device Groups, page 21-2 Configuring Device Groups, page 21-2 Where to Go Next, page 21-6 Field Descriptions for Device Groups, page 21-6 Additional References, page 21-7 Feature History for Device Groups, page 21-8

Information About Device Groups

Device groups allow you to simplify the visualization of interconnections between groups of devices in the topology feature. You can categorize devices into device groups that you define, which allows you to focus on a limited number of devices when you view the topology. Device groups can help you manage a data center with DCNM-LAN more effectively. For example, you could groups of devices based on any of the following criteria:

LocationYou could group devices based on their physical location, such as city or as specific as the data center rack designation. AdministratorYou could group devices based on the DCNM-LAN users who administer them. Data center architectureYou could group devices based on the layers of network architecture in your data center, such as aggregation, access, and storage layers. Device typeYou could group devices based on their type, such as Cisco Nexus 7000 Series switches versus Cisco Nexus 5000 Series switches.

A device can be a member of one group only. The default device group contains any devices that you have not assigned to a custom device group. Any newly discovered device is placed in the default group.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

21-1

Chapter 21 Licensing Requirements for Device Groups

Configuring Device Groups

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Licensing Requirements for Device Groups

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement Device Groups requires no license. Any feature not included in a license package is bundled with the Cisco DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Device Groups

The Device Groups feature has the following prerequisite:

Devices must be discovered before you can assign them to device groups.

Guidelines and Limitations for Device Groups

The Device Groups feature has the following configuration guidelines and limitations:

By default, all discovered devices belong to the default device group. A device can be a member of one group only. For physical devices that support virtual device contexts (VDCs), you can assign VDCs that exist on the same physical device to different device groups. Choose a method of categorizing devices into device groups that provides the best simplification of your network topology.

Configuring Device Groups

This section includes the following topics:

Creating a Device Group, page 21-2 Adding Devices to a Group, page 21-4 Removing Devices from a Group, page 21-5 Deleting a Device Group, page 21-5

Creating a Device Group

You can create a device group and add one or more devices to it. There is only one default group. All other groups are custom device groups.

Cisco DCNM Fundamentals Guide, Release 6.x

21-2

OL-25174-02OL-25174-02

Chapter 21

Configuring Device Groups Configuring Device Groups

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Device Groups. The Summary pane lists custom device groups, if any. The default group does not appear. The Details pane shows the group name, description, and a list of devices in the group. From the menu bar, choose Actions > Create Device Group. A blank row appears in the Summary table. In the blank row, under Device Group Name, enter a name for the group. (Optional) Under Description, enter a useful description of the group. In the Details pane, expand the Membership Details section, if necessary. To add devices to the group, do the following:
a.

Step 2

Step 3 Step 4 Step 5 Step 6

Right-click below the column names in the Membership Details section and choose Add Device. The Device Selection dialog box appears. (Optional) Use the Select Search Criteria drop-down list to filter the devices shown in the Available Devices list. You can filter devices in one of the following ways:
All devicesShows every discovered device. Device typeShows only discovered devices of the type that you choose, such as Cisco Nexus

b.

7000 Series switches.

Unsupported devicesShows discovered devices that DCNM-LAN cannot manage and

monitor.
Connected devicesShows discovered devices connected within the number of hops that you

specify to the seed device that you specify by IP address.

Subnet devicesShows discovered devices whose IP addresses are within the subnet that you

specify by the IP address of the subnet and the subnet mask.

c.

Move one or more devices from the Available Devices List to the Selected Devices list. To move one device, click the device and then click Add. To move more than one device, press and hold Ctrl, click each device, and then click Add. Click OK.

d. Step 7

From the menu bar, choose File > Deploy to save the device group configuration. The new group is available in the topology map. Each device that you added to the new device group is removed from its previous group. If a preexisting, nondefault device group became empty because you moved all its devices to the new device group, DCNM-LAN automatically deletes the empty device group.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

21-3

Chapter 21 Configuring Device Groups

Configuring Device Groups

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Adding Devices to a Group

You can add devices to an existing device group. All devices belong to one and only one group. Devices that are not members of a custom device group automatically belong to the default device group. Adding a device to a group automatically removes the device from the group that previously contained the device.

BEFORE YOU BEGIN

Ensure that the device group that you want to add the devices to exists.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Device Groups. The Summary pane lists custom device groups. The default group does not appear. The Details pane shows the group name, description, and a list of devices in the group. Click the device group to which you want to add one or more devices. In the Details pane, expand the Membership Details section, if necessary. To add devices to the group, do the following:
a.

Step 2 Step 3 Step 4

Right-click below the column names in the Membership Details section and choose Add Device. The Device Selection dialog box appears. (Optional) Use the Select Search Criteria drop-down list to filter the devices shown in the Available Devices list. You can filter devices in one of the following ways:
All devicesShows every discovered device. Device typeShows only discovered devices of the type that you choose, such as Cisco Nexus

b.

7000 Series switches.

Unsupported devicesShows discovered devices that DCNM-LAN cannot manage and

monitor.
Connected devicesShows discovered devices connected within the number of hops that you

specify to the seed device that you specify by IP address.

Subnet devicesShows discovered devices whose IP addresses are within the subnet that you

specify by the IP address of the subnet and the subnet mask.

c.

Move one or more devices from the Available Devices List to the Selected Devices list. To move one device, click the device and then click Add. To move more than one device, press and hold Ctrl, click each device, and then click Add. Click OK.

d. Step 5

From the menu bar, choose File > Deploy to save the device group configuration. On the topology map, the device group will include the devices that you added to it.

Cisco DCNM Fundamentals Guide, Release 6.x

21-4

OL-25174-02OL-25174-02

Chapter 21

Configuring Device Groups Configuring Device Groups

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Each device that you added to the device group is removed from its previous group. If a preexisting, nondefault device group became empty because you moved all its devices to the new device group, DCNM-LAN automatically deletes the empty device group.

Removing Devices from a Group

You can remove devices from a custom device group. All devices that you remove from a custom group are added to the default device group.

Tip

If you want to move devices from one group to another, add them to the other group. DCNM-LAN automatically removes devices from one group when you add them to another group.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Device Groups. The Summary pane lists custom device groups. The default group does not appear. The Details pane shows the group name, description, and a list of devices in the group. Click the device group from which you want to remove one or more devices. In the Details pane, expand the Membership Details section, if necessary. In the Membership Details section, select the devices that you want to delete. To select a single device, click the device. To select more than one device, press and hold Ctrl, and then click each device. Right-click on one of the selected devices and choose Delete. DCNM-LAN removes the selected devices from the device group. From the menu bar, choose File > Deploy to save the device group configuration. On the topology map, the default device group will include the devices that you deleted from the custom device group. Each device that you deleted from the custom device group is added to the default device group. If the custom device group became empty because you removed all its devices, DCNM-LAN automatically deletes the empty device group.

Step 2 Step 3 Step 4

Step 5

Step 6

Deleting a Device Group

You can delete a custom device group. Devices that belong to a custom device group that you delete automatically become members of the default device group.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

21-5

Chapter 21 Where to Go Next

Configuring Device Groups

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Tip

If you add all the devices of a custom device group to another custom device group, DCNM-LAN automatically deletes the empty device group.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Device Groups. The Summary pane lists custom device groups. The default group does not appear. The Details pane shows the group name, description, and a list of devices in the group. Click the device group that you want to delete. From the menu bar, choose Actions > Delete Device Group. DCNM-LAN removes the device group from the Summary pane. The devices that were in the deleted device group are now members of the default device group.

Step 2 Step 3

Step 4

From the menu bar, choose File > Deploy to save the device group configuration. On the topology map, the default device group will include the devices that were in the deleted device group.

Where to Go Next
For more information about using device groups in the topology feature, see Chapter 19, Working with Topology.

Field Descriptions for Device Groups

This section includes the following field descriptions for the Device Groups feature:

Summary Pane, page 21-6 Device Group: Details: Global Settings Section, page 21-7 Device Group: Details: Membership Details Section, page 21-7

Summary Pane
Table 21-1 Device Groups Summary Pane

Field Device Group Name

Description Display only. Name that you assigned to the device group. After you create a device group, the name is not editable. Device group names must start with a letter and can be up to 30 alphanumeric characters. Text describing the device group. A description can be up to 80 characters.

Description

Cisco DCNM Fundamentals Guide, Release 6.x

21-6

OL-25174-02OL-25174-02

Chapter 21

Configuring Device Groups Additional References

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Device Group: Details: Global Settings Section

Table 21-2 Device Group: Details: Global Settings Section

Field Device Group Name Description

Description Display only. Name that you assigned to the device group. Text describing the device group. A description can be up to 80 characters.

Device Group: Details: Membership Details Section

Table 21-3 Device Group: Details: Membership Details Section

Field Switch Name Platform

Description Display only. Name of a device assigned to the device group. Display only. Name of the physical or virtual device type, such as Cisco Nexus 1000V Series or Cisco Nexus 7000 Series.

Additional References
For additional information related to administering Device Groups, see the following sections:

Related Documents, page 21-7 Standards, page 21-7

Related Documents
Related Topic Topology Device discovery Document Title Chapter 19, Working with Topology Chapter 16, Administering Device Discovery

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

21-7

Chapter 21 Feature History for Device Groups

Configuring Device Groups

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Feature History for Device Groups

Table 21-4 lists the release history for this feature.
Table 21-4 Feature History for Device Groups

Feature Name Device Groups

Releases 5.0(2)

Feature Information Support was added.

Cisco DCNM Fundamentals Guide, Release 6.x

21-8

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

22

Working with Cluster Administration

This chapter describes how to use the Cluster Administration feature in Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Cluster Administration, page 22-1 Licensing Requirements for Cluster Administration, page 22-4 Prerequisites for Cluster Administration, page 22-4 Guidelines and Limitations for Cluster Administration, page 22-4 Viewing Server Information, page 22-4 Field Descriptions for Cluster Administration, page 22-5 Additional References, page 22-6 Feature History for Cluster Administration, page 22-6

Information About Cluster Administration

This section includes the following topics:

Cluster Administration, page 22-1 Clustered-Server Environment, page 22-2 Master Server Role, page 22-2 Distributed Server Tasks, page 22-2 Effect of Cluster Changes on Server Task Distribution, page 22-3

Cluster Administration
Cluster Administration allows you to view information about the DCNM-LAN servers configured to operate in a server cluster. If the DCNM-LAN server is not configured to operate in a cluster, the Cluster Administration feature allows you to view information about the single server. For each server that appears in the Cluster Administration summary pane, you can view information such as the DCNM-LAN release number, Java version, operating system, system threads, memory utilization, IP address, and disk drive usage.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

22-1

Chapter 22 Information About Cluster Administration

Working with Cluster Administration

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Clustered-Server Environment
You can deploy DCNM-LAN in a server cluster, with up to five DCNM-LAN servers in a clustser. DCNM-LAN servers in a cluster communicate using multicast IP messages. The primary benefit of a clustered-server deployment is enhanced capacity for the device-management tasks that DCNM-LAN performs. A clustered-server deployment also helps to ensure availability of the DCNM-LAN server. DCNM-LAN distributes tasks among all servers in the cluster. Servers in the cluster are always active and never in a stand-by mode. For information about the server-system and network requirements for a clustered-server deployment, and for the detailed steps for installing a server cluster, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Master Server Role

One server in a DCNM-LAN server cluster is the master server. The master server is responsible for assigning tasks to all of the servers in the server cluster, including to itself. Tasks are stored in the DCNM-LAN database. If the master server fails, the server that assumes the master server role can access the tasks in the database. When users log into the DCNM-LAN client, they should specify the IP address or DNS name of the master server. When users submit requests to the master server, the master server distributes the tasks as needed. DCNM-LAN determines which server is the master server by the oldest server start time. The DCNM-LAN server that started first is always the master server in a server cluster. If the master server fails, the DCNM-LAN server with the next oldest start time assumes the role of the master server. You can control which server is the master server by controlling the order in which you start the servers in a cluster.

Distributed Server Tasks

The master server distributes tasks by assigning managed devices to servers in the server cluster. For example, in a cluster of four servers, if DCNM-LAN is managing 20 devices, the master server assigns five managed devices to each server, including itself. After the master server assigns a device to a server, that server performs the following tasks for that device:

Auto-synchronization with devicesThe server regularly retrieves the system message log file from the device. For more information about auto-synchronization, see Chapter 23, Administering Auto-Synchronization with Devices. Statistical data collectionThe server runs any statistical data collectors for the device, with the exception of virtual port channel (vPC) statistics. The master server always runs statistical data collectors for vPC statistics. For more information about statistical data collection, see Chapter 25, Administering Statistical Data Collection. Device discoveryThe server performs device configuration discovery for the device; however, the remainder of the device discovery phases are performed by the master server. For more information about the phases of device discovery, see the Discovery Process section on page 16-3.

Cisco DCNM Fundamentals Guide, Release 6.x

22-2

OL-25174-02OL-25174-02

Chapter 22

Working with Cluster Administration Information About Cluster Administration

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
For example, if a user initiates device discovery for a switch named DC-NEXUS-7010-3, the master server completes the initial phases of device discovery. It then assigns the device configuration discovery phase for DC-NEXUS-7010-3 to one of the servers in the cluster, ensuring that discovery tasks are evenly distributed. After discovery completes, the master server assigns DC-NEXUS-7010-3 to the server that is managing the least number of devices. The master server instructs the assigned server to perform auto-synchronization for DC-NEXUS-7010-3. Whenever a DCNM-LAN client user starts a statistical chart for any managed feature on DC-NEXUS-7010-3, the master server instructs the assigned server to run the statistical data collector for the chart.

Effect of Cluster Changes on Server Task Distribution

When servers join or leave the cluster, the master server always ensures that the assignment of managed devices to servers is redistributed evenly among the servers in the cluster. Table 22-1 describes the behavior of a DCNM-LAN server cluster for more specific events.
Table 22-1 Cluster Change Events and Behavior

Cluster Change Event Master server stops or fails

Cluster Behavior The server with the oldest start time becomes the master server and redistributes the assignment of managed devices evenly among the servers remaining in the cluster. Because the cluster size decreased, the number of devices assigned to each server increases. The master server redistributes the assignment of managed devices evenly among the servers remaining in the cluster. Because the cluster size decreased, the number of devices assigned to each server increases. If the user-initiated device-configuration deployment did not complete before the member server failed, the deployment fails and the server task to deploy the device configuration is lost. To recover from the loss of the deployment, the user must repeat the configuration steps and deploy the configuration again. In some cases, the failure may result in the device becoming unmanaged, and the user must rediscover the device before repeating the configuration steps. The master server redistributes the assignment of managed devices evenly among the servers remaining in the cluster. Because the cluster size decreased, the number of devices assigned to each server increases.

Server stops or fails

Server fails while performing a user-initiated device-configuration deployment

Server starts

The master server redistributes the assignment of managed devices evenly among the servers remaining in the cluster. Because the cluster size increased, the number of devices assigned to each server decreases.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

22-3

Chapter 22 Licensing Requirements for Cluster Administration

Working with Cluster Administration

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Licensing Requirements for Cluster Administration

The following table shows the licensing requirements for this feature: Product DCNM-LAN License Requirement Cluster Administration requires no license. Any feature not included in a license package is bundled with the DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Cluster Administration

The Cluster Administration feature has the following prerequisite:

Servers in a cluster must meet the clustered-server requirements. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Guidelines and Limitations for Cluster Administration

The Cluster Administration feature has the following limitation:

The Cluster Administration feature shows information about running servers only. When a server in a cluster stops or fails, it appears to have left the cluster, and its information is not shown by the Cluster Administration feature.

Viewing Server Information

You can view information about the DCNM-LAN servers that are configured to operate as a server cluster. If you have a single server, which is not configured to operate as a member of a server cluster, you can use the Cluster Administration feature to view information about it.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Cluster Administration. The Summary pane displays the cluster by the partition name assigned to the cluster during installation. A single server environment still has a partition name assigned to it during installation.

Step 2

Expand the cluster. The Summary pane lists each DCNM-LAN server in the cluster with information about the server.

Tip Step 3

To update the server information, from the toolbar, choose View > Refresh.

(Optional) If you want to view disk usage information, on the Details tab, expand the Logical Disk(s) section.

Cisco DCNM Fundamentals Guide, Release 6.x

22-4

OL-25174-02OL-25174-02

Chapter 22

Working with Cluster Administration Field Descriptions for Cluster Administration

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Field Descriptions for Cluster Administration

This section includes the following field descriptions for the Cluster Administration feature:

Summary Pane, page 22-5 Server: Details Tab, page 22-5

Summary Pane
Table 22-2 Cluster Administration Summary Pane

Field

Description

[Cluster partition name] Display only. Name assigned to the DCNM-LAN server partition during installation of the server software.
Note

The remaining fields on the summary pane pertain to specific servers in a cluster.

IP Address

Display only. IPv4 address of the DCNM-LAN server. If the server is currently the master server in the server cluster, the IP Address field also indicates that the server is the master server. Display only. DCNM-LAN release number that the server is running. Display only. Java version that the DCNM-LAN server is using. Display only. Number of processing threads used by the DCNM-LAN software on the server system. Display only. Percentage of system memory used by the DCNM-LAN software on the server system. Display only. Local date and time on the DCNM-LAN server when the client last received updated information.

DCNM-LAN Version Java Version Total Threads Memory Utilization (Percentage) Last Local Refresh Time

Server: Details Tab

Table 22-3 Server: Details Tab

Field
General

Description

The fields in this section show the same information as the fields of the same name on the Summary pane.
Logical Disk(s)

Name Size (MB) Free Space (MB)

Display only. Name of the drive. Display only. Total capacity of the drive, in megabytes. Display only. Number of megabytes available for use on the drive.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

22-5

Chapter 22 Additional References

Working with Cluster Administration

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Additional References
For additional information related to administering Cluster Administration, see the following sections:

Related Documents, page 22-6 Standards, page 22-6

Related Documents
Related Topic Events Device discovery Auto-synchronization with devices Statistical data collection Stopping servers Document Title System Management Configuration Guide, Cisco DCNM for LAN, Release 5.x Chapter 16, Administering Device Discovery Chapter 23, Administering Auto-Synchronization with Devices Chapter 25, Administering Statistical Data Collection Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Feature History for Cluster Administration

Table 22-4 lists the release history for this feature.
Table 22-4 Feature History for Cluster Administration

Feature Name Cluster Administration

Releases 5.0(2)

Feature Information Support was added.

Cisco DCNM Fundamentals Guide, Release 6.x

22-6

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

23

Administering Auto-Synchronization with Devices

This chapter describes how to administer the Auto-Synchronization with Devices feature in Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Auto-Synchronization with Devices, page 23-1 Licensing Requirements for Auto-Synchronization with Devices, page 23-2 Prerequisites for Auto-Synchronization with Devices, page 23-2 Guidelines and Limitations for Auto-Synchronization with Devices, page 23-3 Configuring Device Auto-Synchronization, page 23-3 Viewing the Status of Auto-Synchronization Pollers, page 23-8 Field Descriptions for Auto Synchronization with Devices, page 23-9 Additional References, page 23-10 Feature History for Auto-Synchronization with Devices, page 23-11

Information About Auto-Synchronization with Devices

The Auto Synchronizing with Devices feature ensures that the Cisco Data Center Network Manager for LAN (DCNM-LAN) server has current configuration and status information about managed devices. The DCNM-LAN server creates one poller process for each device to retrieve the system and accounting logs that this feature requires. When you choose Auto Synchronization with Devices on the Feature Selector pane, the Contents pane shows information about each poller process and allows you to control them. You can configure the length of time that DCNM-LAN waits before polling a device again. DCNM-LAN sets a default polling interval for each managed device. The default value varies by the type of device. The range of polling interval values is displayed when you begin editing the polling interval field for the device. For more information, see the Configuring the Polling Interval section on page 23-4. DCNM-LAN polls devices concurrently; however, to avoid polling all devices simultaneously, DCNM-LAN begins polling devices in alphabetical device-name order and delays each polling process by a short, random amount of time.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

23-1

Chapter 23 Licensing Requirements for Auto-Synchronization with Devices

Administering Auto-Synchronization with Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
This section includes the following topics:

Automatic and Manual Purging of Event Data, page 23-2 Virtualization Support, page 23-2

Automatic and Manual Purging of Event Data

You can use the Auto-Synchronization with Devices feature to delete unwanted event data. DCNM-LAN supports automatic purging of event data. You can configure the following aspects of automatic event data purging:

Days of the week and time of day that automatic purging occurs. Whether DCNM-LAN determines which event data to purge by the age of the data or by a maximum number of database entries. Severity level of events.

You can also manually purge event data.

Virtualization Support
DCNM-LAN treats each virtual device context (VDC) on a Cisco NX-OS device as a separate device. DCNM-LAN creates one poller process per device.

Licensing Requirements for Auto-Synchronization with Devices

The following table shows the licensing requirements for this feature: Product DCNM-LAN License Requirement Auto-Synchronization with Devices requires no license. Any feature not included in a license package is bundled with the DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Auto-Synchronization with Devices

The Auto-Synchronization with Devices feature has the following prerequisites:

The DCNM-LAN server must be able to connect to the devices. The Cisco NX-OS device must be running a supported version of Cisco NX-OS. The Cisco NX-OS device must have the minimal configuration that is required to enable device discovery to succeed. For more information, see the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8.

Cisco DCNM Fundamentals Guide, Release 6.x

23-2

OL-25174-02OL-25174-02

Chapter 23

Administering Auto-Synchronization with Devices Guidelines and Limitations for Auto-Synchronization with Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Guidelines and Limitations for Auto-Synchronization with Devices

The Auto-Synchronization with Devices feature has the following configuration guidelines and limitations:

We recommend that you use the default device polling interval unless you encounter issues with synchronization due to slow responses from devices or to managing many devices. For more information, see the Configuring the Polling Interval section on page 23-4. For the Auto-Synchronization with Devices feature, the DCNM-LAN client does not automatically update the information shown in the Summary pane. To ensure that you are viewing current information, from the menu bar, choose View > Refresh. We recommend that you configure automatic purging of event data to ensure that the DCNM-LAN database size does not grow too large.

Configuring Device Auto-Synchronization

This section includes the following topics:

Starting and Stopping a Poller, page 23-3 Configuring the Polling Interval, page 23-4 Synchronizing with a Device, page 23-4 Deleting Data from the Events Database, page 23-5 Enabling and Disabling Automatic Event Purging, page 23-6 Configuring Automatic Event Purge Settings, page 23-6 Purging Events Now, page 23-8

Starting and Stopping a Poller

You can start and stop a poller for a device. When a poller is stopped, auto-synchronization for the device does not occur.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Auto Synchronization with Devices. A table of pollers appears in the Contents pane. Each row corresponds to a poller for a particular device. Devices are listed alphabetically. The Poller Status field displays messages about whether the poller is running or is stopped.

Step 2

Click to select the poller that you want to start or stop.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

23-3

Chapter 23 Configuring Device Auto-Synchronization

Administering Auto-Synchronization with Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 3

Do one of the following:

To start a poller, from the menu bar, choose Actions > Start Poller. The Poller Status field changes to Running. To stop a poller, from the menu bar, choose Actions > Stop Poller. The Poller Status field changes to Stopped.

You do not need to save your changes.

Configuring the Polling Interval

You can configure how often the DCNM-LAN server synchronizes with managed devices. While synchronizing, the DCNM-LAN server fetches accounting and system logs from managed devices. This setting affects how frequently features in the DCNM-LAN client receive updated information about managed devices.

BEFORE YOU BEGIN

Determine how often you want DCNM-LAN to perform auto-synchronization with managed devices. Consider the following:

How often device configurations are changed by means other than DCNM-LAN, such as using the command-line interface of a device. If changes by means other than DCNM-LAN are common, consider using a short polling interval. How important it is to your organization that DCNM-LAN be up to date with managed device configurations. If up-to-date configuration information is important to your organization, consider using a short polling interval.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Auto Synchronization with Devices. The polling intervals for all devices appear below the table of pollers in the Poller Setting tab. Select the device in the Platform column that you want to work with. In the Polling Interval field, enter the number of seconds between auto-synchronizations for the selected device. The range of polling interval values is displayed when you begin editing the Polling Interval field for the device. From the menu bar, choose File > Deploy to save the polling interval.

Step 2 Step 3

Step 4

Synchronizing with a Device

You can make DCNM-LAN synchronize with a device manually when you do not want to wait for the next auto-synchronization to occur.

Cisco DCNM Fundamentals Guide, Release 6.x

23-4

OL-25174-02OL-25174-02

Chapter 23

Administering Auto-Synchronization with Devices Configuring Device Auto-Synchronization

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

If many configuration changes have occurred on the device since the last successful synchronization, consider performing device discovery instead of synchronization. For more information, see the Discovering a Device section on page 17-4.

BEFORE YOU BEGIN

Ensure that you have either configured the device entry with unique device credentials or that DCNM-LAN can use the default device credentials to connect to the device. For more information, see the Configuring Default Device Credentials section on page 17-6.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Auto Synchronization with Devices. A table of pollers appears in the Contents pane. Each row corresponds to a poller for a particular device. Devices are listed alphabetically.

Step 2 Step 3

Click to select the device that you want DCNM-LAN to synchronize with. From the menu bar, choose Actions > Synchronize with Device. Synchronization begins. To determine when the synchronization has finished, watch the Last Sync Status column. Typically, synchronization with a device occurs in less than 5 minutes. You do not need to save your changes.

Deleting Data from the Events Database

You can delete data from the events database based on the exact age of the events. Events that you delete can no longer appear in the Event Browser or on a feature-specific Events tab.

Tip

If you want to delete events based on the number of events in the database, see the Purging Events Now section on page 23-8.

BEFORE YOU BEGIN

Determine the date and time of the newest events data that you want to delete. When you follow the steps in this procedure, DCNM-LAN deletes all events that are older than the date and time that you select.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

23-5

Chapter 23 Configuring Device Auto-Synchronization

Administering Auto-Synchronization with Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Auto Synchronization with Devices. The Events Database Administration tab appears in the Details pane, below the table of pollers. From the Delete events older than drop-down list, choose the date and time of the newest event that you want to delete and click OK. Click Delete. DCNM-LAN deletes all events older than the date and time that you specified.

Step 2 Step 3

Enabling and Disabling Automatic Event Purging

You can enable or disable the automatic purging of events from the DCNM-LAN events database.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Auto Synchronization with Devices. The Events Database Administration tab appears in the Details pane, below the table of pollers. Under Auto Purge Settings, do one of the following:

Step 2

To enable automatic event purging, check Enable Auto Purge. To disable automatic event purging, uncheck Enable Auto Purge.

Step 3

From the menu bar, choose File > Deploy to save your changes to the DCNM-LAN server.

Configuring Automatic Event Purge Settings

You can configure when automatic event purging occurs and the criteria that DCNM-LAN uses to determine which events to purge.

BEFORE YOU BEGIN

Determine when you want automatic event purging to occur. We recommend that automatic event purging occur when DCNM-LAN usage is low. If you perform backups of your DCNM-LAN databases, consider scheduling automatic event purging after database backups have occurred, to ensure that you retain a record of all events.

Cisco DCNM Fundamentals Guide, Release 6.x

23-6

OL-25174-02OL-25174-02

Chapter 23

Administering Auto-Synchronization with Devices Configuring Device Auto-Synchronization

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Determine what criteria you want DCNM-LAN to use to determine which events to purge. The criteria available are as follows:

Age of eventDCNM-LAN can purge all events that are older than a specific number of days, weeks, or months. Number of events in the databaseWhen the number of events in the database exceeds the maximum number that you specify, DCNM-LAN can purge the oldest events first until the maximum number is not exceeded. Severity of eventDCNM-LAN can purge events based on the severity level of the event.

If you enable both criteria, DCNM-LAN applies them independently of each other.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Auto Synchronization with Devices. The Events Database Administration tab appears in the Details pane, below the table of pollers. Under Purge Threshold, configure the criteria that DCNM-LAN uses to determine which events to purge. You can configure any of the criteria in the following table: Purge Criteria Age of events How to Configure
1. 2. 3.

Step 2

Check Data older than. From the first drop-down list, choose the number of days, weeks, or months. From the second drop-down list, choose Days, Weeks, or Months, as needed. Check Total Entries Exceed(0-2147483647). In the box, enter the maximum number of entries that you want to allow in the events database. Check Severity. The list of eight severity levels becomes available. For each severity level that you want DCNM-LAN to use to determine whether to purge events, check the severity level.

Number of events in the database

1. 2.

Severity of event

1. 2.

Step 3

Under Auto Purge Settings, follow these steps to configure when you want automatic purging to occur:
a. b.

Check the days-of-the-week check boxes to specify which days of the week that you want automatic purging to occur. Use the Run at box to configure the exact time on the specified days that you want automatic event purging to occur.

Step 4 Step 5

(Optional) If you want to enable automatic event purging, check Enable Auto Purge. From the menu bar, choose File > Deploy to save your changes to the DCNM-LAN server.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

23-7

Chapter 23 Viewing the Status of Auto-Synchronization Pollers

Administering Auto-Synchronization with Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Purging Events Now

You can purge event data on demand, using the automatic event purge settings to determine which events are purged. Events that you delete can no longer appear in the Event Browser or on a feature-specific Events tab.

Tip

If you want to delete events on demand, based on the exact age of the events, see the Deleting Data from the Events Database section on page 23-5.

BEFORE YOU BEGIN

Ensure that the automatic event purge settings are configured as needed. For more information, see the Configuring Automatic Event Purge Settings section on page 23-6.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Auto Synchronization with Devices. The Events Database Administration tab appears in the Details pane, below the table of pollers. Under Purge, click Purge Now. DCNM-LAN deletes events, using the automatic event purge settings to determine which events to purge.

Step 2

Viewing the Status of Auto-Synchronization Pollers

To view the status of an auto-synchronization poller, from the Feature Selector pane, choose DCNM Server Administration > Auto Synchronization with Devices. Poller status and information about the synchronization time and status appear in the Pollers area in the Contents pane.
Table 23-1 Auto Synchronization Pollers Information

Field
Pollers

Description Display only. Date and time that the DCNM-LAN client updated information shown on the Contents pane. Display only. Name and IP address of the device for the corresponding poller. Display only. Whether the poller is running or stopped. A running poller attempts to synchronize with the configuration and status information from its device at the frequency specified by the Device Polling Interval field. Display only. Date and time that the poller last retrieved system and accounting log data from the device.

Last Refresh Time Device Poller Status

Last Sync Time

Cisco DCNM Fundamentals Guide, Release 6.x

23-8

OL-25174-02OL-25174-02

Chapter 23

Administering Auto-Synchronization with Devices Field Descriptions for Auto Synchronization with Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 23-1 Auto Synchronization Pollers Information (continued)

Field Last Sync Status

Description Display only. Whether the most recent synchronization attempt succeeded or failed. If synchronization failed, determine why DCNM-LAN failed to connect to the device. If necessary, rediscover the device.

Field Descriptions for Auto Synchronization with Devices

This section includes the following field descriptions for the Auto Synchronization with Devices feature:

Poller Setting Tab, page 23-9 Events Database Administration Tab, page 23-9

Poller Setting Tab

Table 23-2 Auto Synchronization with Devices Poller Setting Tab

Field
Pollers

Description Number of seconds that all pollers wait before the next attempt to synchronize with a device. The range of polling interval values is displayed when you begin editing the Polling Interval field for the device. Display only. Name and IP address of the device for the corresponding poller.

Polling Interval

Device

Events Database Administration Tab

Table 23-3 Events Database Administration Tab

Field

Description

Delete events older than Date and time of the newest event to be deleted from the events database. There is no default value for this field.
Purge Threshold

Data older than

Whether, during automatic event purging, DCNM-LAN deletes events that are older than the age specified in the drop-down lists located to the right of this check box. By default, this check box is unchecked. If you check the check box, the default age is 1 day. Whether, during automatic event purging, DCNM-LAN deletes the oldest events until the number of events equals the number in the box located to the right of this check box. By default, this check box is unchecked. If you check the check box, the default number of event is 25,000. Whether, during automatic event purging, DCNM-LAN deletes events with severity levels that are selected from the list of severity levels. By default, this check box is disabled.

Total Entries Exceed

Severity

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

23-9

Chapter 23 Additional References

Administering Auto-Synchronization with Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 23-3 Events Database Administration Tab (continued)

Field Severity Levels

Description Severity levels of events that DCNM-LAN deletes during automatic event purging. The severity levels are available only if the Severity check box is checked. By default, all severity levels are disabled. The severity levels are as follows:

Emergency Alert Critical Error Warning Notification Informational Debugging

Auto Purge Settings

Enable Auto Purge Run on

Whether automatic purging of event data is enabled. By default, this check box is disabled. Days of the week that the automatic purging of events data occurs. By default, none of the check boxes are checked. If you check the Daily check box, the check boxes for the individual days of the week become unavailable. Time of day that automatic purging of event data occurs, on the days of the week that automatic purging is enabled.

Run at

Additional References
For additional information related to administering Auto-Synchronization with Devices, see the following sections:

Related Documents, page 23-10 Standards, page 23-11

Related Documents
Related Topic Events Device discovery Document Title System Management Configuration Guide, Cisco DCNM for LAN, Release 5.x Chapter 16, Administering Device Discovery

Cisco DCNM Fundamentals Guide, Release 6.x

23-10

OL-25174-02OL-25174-02

Chapter 23

Administering Auto-Synchronization with Devices Feature History for Auto-Synchronization with Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Feature History for Auto-Synchronization with Devices

Table 23-4 lists the release history for this feature.
Table 23-4 Feature History for Auto-Synchronization with Devices

Feature Name Auto-Synchronization with Devices

Releases 5.0(2)

Feature Information No change from Release 4.2.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

23-11

Chapter 23 Feature History for Auto-Synchronization with Devices

Administering Auto-Synchronization with Devices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

23-12

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

24

Working With Threshold Rules

This chapter describes how to configure threshold rules using Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Threshold Rules, page 24-1 Licensing Requirements for Threshold Rules, page 24-5 Configuring Threshold Rules, page 24-5 Additional References, page 24-8 Feature History for Threshold Rules, page 24-9

Information About Threshold Rules

This section includes the following topics:

Threshold Rules Overview, page 24-1 Threshold Rule Examples, page 24-2

Threshold Rules Overview

DCNM-LAN provides a feature that you use to specify rising or falling threshold rules for sample variables in collected statistical data. Depending on the rule definition, a set of actions are performed by DCNM-LAN. You define the threshold rule on the Threshold Rules page, and you apply the threshold rule to the existing chart. This section includes the following topics:

Rising Threshold, page 24-2 Falling Threshold, page 24-2 Threshold Rule Properties, page 24-2 Threshold Rule Actions, page 24-2

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

24-1

Chapter 24 Information About Threshold Rules

Working With Threshold Rules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Rising Threshold
The rising threshold is the upper threshold for a sample variable. When the current sampled variable is greater than or equal to the specified threshold, a set of actions is performed.

Falling Threshold
The falling threshold is the lower threshold for a sample variable. When the current sampled variable is lower than or equal to the specified threshold a set of actions is performed.

Note

You can specify only one rising threshold and one falling threshold for a single sampled variable.

Threshold Rule Properties

Threshold rule properties are as follows:

NameSpecifies the threshold rule name. FrequencySpecifies the number of times the sampled variable must cross a threshold before triggering any actions. PeriodSpecifies the interval of time the frequency is monitored. RepeatPrevents the timer from resetting after triggering an action within the period. TrendSpecifies the rising or falling threshold.

Threshold Rule Actions

Threshold rule actions are as follows:

Send an email or SMS to a mail server or mail to SMS gateway. Run a script on the server. Send an event to the current DCNM JMS channel.

Threshold Rule Examples

Note

The granularity of a period is driven by the minimal interval of the collected data. Consequently, the period must be higher than that interval. This section includes the following topics:

Triggering an Action Each Time a Threshold is Crossed, page 24-2 Triggering an Action Only Once in a Period When a Threshold is Crossed, page 24-3 Triggering an Action Every Fourth Period When a Threshold is Crossed, page 24-4

Triggering an Action Each Time a Threshold is Crossed

To trigger an action each time a threshold is crossed, set properties as follows:

Cisco DCNM Fundamentals Guide, Release 6.x

24-2

OL-25174-02

Chapter 24

Working With Threshold Rules Information About Threshold Rules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Frequency1 RepeatYes

Figure 24-1 shows the trigger action when you set rule properties to the preceding values.
Figure 24-1 Trigger an Action Each Time a Threshold is Crossed

If the sampled variable crosses the threshold, an action is taken the first time it crosses the threshold. As a result, an action is performed each time the threshold is crossed.

Triggering an Action Only Once in a Period When a Threshold is Crossed

To trigger an action only once in a period when a threshold is crossed, set properties as follows:

Frequency1 Period300 RepeatNo

Figure 24-2 shows the trigger action when you set rule properties to the preceding values.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

24-3

Chapter 24 Information About Threshold Rules

Working With Threshold Rules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Figure 24-2 Trigger an Action Only Once When a Threshold is Crossed Within a Period

If the sampled variable crosses the threshold, an action is taken the first time it crosses the threshold. For the remaining 5 minutes, an action will not be taken. As a result, an action is performed only once during the specified period.

Triggering an Action Every Fourth Period When a Threshold is Crossed

To trigger an action every fourth period when a threshold is crossed, set properties as follows:

Frequency4 Period300 RepeatNo

Figure 24-3 shows the trigger action when you set rule properties to the preceding values.
Figure 24-3 Trigger an Action Every Fourth Period When a Threshold is Crossed

If the sampled variable crosses the threshold, an action is taken the fourth time it crosses the threshold. For the remaining 5 minutes, an action is not taken. As a result, an action is performed only once during the specified period.

Cisco DCNM Fundamentals Guide, Release 6.x

24-4

OL-25174-02

Chapter 24

Working With Threshold Rules Licensing Requirements for Threshold Rules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Licensing Requirements for Threshold Rules

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement Threshold rules require no license.

Configuring Threshold Rules

With this feature, you can create, delete, edit, view, and apply a rule to a chart. The following sections provide more details about the feature. This section includes the following topics:

Creating Threshold Rules, page 24-5 Deleting Threshold Rules, page 24-7 Editing Threshold Rules, page 24-7 Viewing Threshold Rules, page 24-8 Applying a Threshold Rule to a Chart, page 24-8

Creating Threshold Rules

You can create threshold rules using DCNM-LAN.

DETAILED STEPS
Step 1 Step 2

From the Feature Selector pane, choose DCNM Server Administration > Threshold Rules. From the toolbar, choose New, and then choose New Threshold Rule. The Details and Threshold Bindings tabs appear in the Details pane, with the Details tab open. Create a threshold rule as follows:
a. b.

Step 3

In the Name field, enter a name. In the Description field, enter a description of the threshold rule. After you have enter a description, the Rising Threshold check box is automatically checked and the Threshold field in the Settings area is outlined in red.

Note

A field outlined in red indicates that an entry is required. A field outlined in yellow indicates that the entry is satisfactory.

c.

In the Settings area, enter a value in the Threshold field. Once you have entered a value, the three options in the Action area are outlined in red. In the Action area, provide one of the following:

d.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

24-5

Chapter 24 Configuring Threshold Rules

Working With Threshold Rules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Enter email addresses (delimited with commas) Select Sent Event to forward events to the DCNM-LAN Event Browser Enter a script name

The script receives all data regarding the crossed threshold. The script can be written in any programming language and saved in one of the directories of the system PATH. Table 24-1 describes the available parameters.
Table 24-1 Parameters Passed to Script

Parameter $1 $2 $3 $4 $5

Description Device name Threshold name Timestamp Severity Monitored metric that is a counter or a non-counter.

When used as a counter, it represents a rate in metric units /second. When used as a non-counter, it represents an absolute in metric units.

$6

Threshold for the monitored metric that is a counter or a non-counter.

When used as a counter, it represents a rate in metric units /second. When used as a non-counter, it represents an absolute in metric units.

$7

Trend type The possible values are:

rate which is a counter.

absolute which is a non-counter

$8

Threshold type The possible values are:

rising falling

$9 $10 $11

Statistic class Statistic variable Source object

Cisco DCNM Fundamentals Guide, Release 6.x

24-6

OL-25174-02

Chapter 24

Working With Threshold Rules Configuring Threshold Rules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

Ensure that the DCNM-LAN server is configured for an SMTP server. For more information about configuring the DCNM-LAN server, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

e. f. g.

(Optional) In the corresponding Settings and Action areas, configure a Falling Threshold. (Optional) Click the Threshold Bindings tab to view bindings. Click Deploy.

The rule is deployed. When you exit DCNM-LAN and Save Pending Changes is checked in the Warning dialog box, click Yes to save the rule.

Deleting Threshold Rules

You can delete rules using DCNM-LAN.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Threshold Rules. The rules appear in the Summary pane. From the Summary pane, right-click the appropriate rule. From the drop-down list, choose Delete Threshold Rule. A warning dialog box appears and displays Are you sure you want to delete? Click Yes. The rule is deleted.

Step 2 Step 3

Step 4

Editing Threshold Rules

You can view threshold rules using DCNM-LAN.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Threshold Rules. The rules appear in the Summary pane. Edit any appropriate areas.

Step 2

Note

You cannot edit the Name field.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

24-7

Chapter 24 Additional References

Working With Threshold Rules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Viewing Threshold Rules

You can view threshold rules using DCNM-LAN.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Threshold Rules. The rules appear in the Summary pane. Click on a rule to view it.

Step 2

Applying a Threshold Rule to a Chart

You can apply threshold rules using DCNM-LAN.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose the appropriate feature. For example, if you wanted to see statistics for an Ethernet port, choose Interfaces > Physical > Ethernet. The available devices appear in the Summary pane. From the Summary pane, choose the appropriate device. Click the Statistics tab. In the toolbar, click New Chart and then from the drop-down list choose the chart that you want to view. For example, if you wanted to see statistics for traffic, choose Traffic Statistics Chart. In the chart toolbar, click Launch Threshold Setting.

Step 2 Step 3 Step 4 Step 5

Additional References
For additional information related to administering threshold rules, see the following sections:

Related Documents, page 24-8 Standards, page 24-9

Related Documents
Related Topic Events Statistical Data Collection Document Title System Management Configuration Guide, Cisco DCNM for LAN, Release 5.x Chapter 25, Administering Statistical Data Collection

Cisco DCNM Fundamentals Guide, Release 6.x

24-8

OL-25174-02

Chapter 24

Working With Threshold Rules Feature History for Threshold Rules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Feature History for Threshold Rules

Table 24-2 lists the release history for this feature.
Table 24-2 Feature History for Threshold Rules

Feature Name Threshold Rules

Releases 5.2(0)

Feature Information

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

24-9

Chapter 24 Feature History for Threshold Rules

Working With Threshold Rules

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

24-10

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

25

Administering Statistical Data Collection

This chapter describes how to administer Statistical Data Collection in the Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Statistical Data Collection, page 25-1 Licensing Requirements for Statistical Data Collection, page 25-2 Prerequisites for Statistical Data Collection, page 25-2 Guidelines and Limitations for Statistical Data Collection, page 25-3 Configuring Statistical Data Collection, page 25-3 Viewing the Status of Statistical Data Collectors, page 25-9 Field Descriptions for Statistical Data Collection, page 25-9 Additional References, page 25-11 Feature History for Statistical Data Collection, page 25-11

Information About Statistical Data Collection

You can use the Statistical Data Collection feature to control the statistics monitoring processes that you have created for one of the many device configuration features that support statistics. When you choose Statistical Data Collection on the Feature Selector pane, the Contents pane shows information about each statistical collection and allows you to control them. You can also use this feature to purge old data from the statistical database. You can configure the length of time that Cisco Data Center Network Manager for LAN (DCNM-LAN) waits before retrieving statistical data from devices that it is monitoring. By default, DCNM-LAN retrieves statistical data from monitored devices every 30 seconds. You can increase the length of time to a maximum of 4 minutes. For more information, see the Configuring Monitoring Preferences section on page 14-16. This section includes the following topics:

Automatic and Manual Purging of Statistical Data, page 25-2 Virtualization Support, page 25-2

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

25-1

Chapter 25 Licensing Requirements for Statistical Data Collection

Administering Statistical Data Collection

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Automatic and Manual Purging of Statistical Data

You can use the Statistical Data Collection feature to delete unwanted statistical data. DCNM-LAN supports automatic purging of statistical data. You can configure the following aspects of automatic statistical data purging:

Days of the week and time of day that automatic purging occurs. Whether DCNM-LAN determines which statistical data to purge by the age of the data or by a maximum number of database entries. Whether DCNM-LAN deletes the statistical data entries that it purges or consolidates them into one entry.

You can also manually purge statistical data.

Virtualization Support
DCNM-LAN treats each virtual device context (VDC) on a Cisco NX-OS device as a separate device. Statistical data collections contain statistics from objects within devices.

Licensing Requirements for Statistical Data Collection

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement Real-time monitoring requires no license. Cisco DCNM-LAN requires a LAN Enterprise license for the following features:

Maintaining a history of statistical data Using overview charts

For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Statistical Data Collection

Statistical data collection has the following prerequisites:

The DCNM-LAN server must be able to connect to the devices. The system clocks for the DCNM-LAN server and DCNM-LAN client must be synchronized. If the system clocks are not synchronized, scheduling tasks for data collection may start or end at incorrect times. The Cisco NX-OS device must be running a supported version of Cisco NX-OS. The Cisco NX-OS device must have the minimal configuration that is required to enable device discovery to succeed. For more information, see the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8.

Cisco DCNM Fundamentals Guide, Release 6.x

25-2

OL-25174-02OL-25174-02

Chapter 25

Administering Statistical Data Collection Guidelines and Limitations for Statistical Data Collection

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Guidelines and Limitations for Statistical Data Collection

The Statistical Data Collection feature has the following configuration guidelines and limitations:

Collections are created by starting monitoring for a new chart. For more information, see the Starting Statistical Monitoring for a Chart section on page 14-12. For the Statistical Data Collection feature, the DCNM-LAN client does not automatically update the information shown in the Summary pane. To ensure that you are viewing current information, from the menu bar, choose View > Refresh. When you start statistical monitoring for one or more charts and then close the DCNM-LAN client, a dialog box prompts you to decide whether to stop the collections or let them run. We recommend that you stop any unnecessary collections when you log out of the DCNM-LAN client. This practice conserves database space and decreases the server load. We recommend that you configure automatic purging of statistical data to ensure that the DCNM-LAN database size does not grow too large.

Configuring Statistical Data Collection

This section includes the following topics:

Starting and Stopping Statistical Data Collection, page 25-3 Using Modes in Statistics Charts, page 25-4 Deleting Statistical Data from a Collection, page 25-5 Deleting a Collection, page 25-5 Deleting Data from the Statistics Database, page 25-6 Enabling and Disabling Automatic Statistical Data Purging, page 25-6 Configuring Automatic Statistical Data Purge Settings, page 25-7 Purging Statistical Data Now, page 25-8

Starting and Stopping Statistical Data Collection

You can use the Statistical Data Collection feature to start and stop a statistical data collection process. Each collection process represents a statistical monitoring process that you created by starting monitoring for a device configuration feature.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Statistical Data Collection. A table of statistical data collectors appears in the Contents pane. Each row corresponds to a collector for a particular device. The Status field displays whether the collector is running or is stopped.

Step 2

Click the collector that you want to start or stop.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

25-3

Chapter 25 Configuring Statistical Data Collection

Administering Statistical Data Collection

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 3

Do one of the following:

To start a collector, from the menu bar, choose Actions > Start Collection. The Status field changes to Running. To stop a collector, from the menu bar, choose Actions > Stop Collection. The Status field changes to Stopped.

You do not need to save your changes.

Using Modes in Statistics Charts

You use statistics charts to toggle between the delta mode and the rate mode. Table 25-1 lists the features that contain statistics charts and delta mode/rate mode toggle button.
Table 25-1 Features Containing Statistics Charts and Delta Mode/Rate Mode Toggle Button

Path Interfaces > Physical Interfaces > Physical Interfaces > Logical Interfaces > Logical Interfaces > Logical Switching Switching > Spanning Tree Switching > Spanning Tree Switching > Fabricpath Switching > Layer 2 Security Switching > Layer 2 Security Switching > Layer 2 Security Switching > Layer 2 Security Switching > Layer 2 Security Security Security > Access Control Security > Access Control Security > Access Control Security > AAA Inventory

Feature Ethernet Interface Management Interface Loopback Interface Port Channel vPC VLAN Rapid PVST+ MST ISIS Process Port Security ARP Inspection DHCP Snooping Traffic Storm Control IGMP Snooping DOT1x IPv4 ACL IPv6 ACL MAC ACL Server Groups Virtual Switch

DETAILED STEPS
Step 1

From the Feature Selector pane, choose the appropriate feature. For example, if you wanted to see statistics for the Ethernet feature, choose Interfaces > Physical > Ethernet.

Cisco DCNM Fundamentals Guide, Release 6.x

25-4

OL-25174-02OL-25174-02

Chapter 25

Administering Statistical Data Collection Configuring Statistical Data Collection

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The available devices appear in the Summary pane.
Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

From the Summary pane, double-click the device. From the Summary pane, double-click Slots. Click the interface. From the Details pane, choose the Statistics tab. In the toolbar, click New Chart and then from the menu bar drop-down list, choose the chart that you want to view. For example, if you wanted to see statistics for traffic, choose Traffic Statistics Chart. (Optional) To toggle between the statistics mode and the rate mode, click the button to the right of the Select Frequency drop-down list.

Deleting Statistical Data from a Collection

You can delete statistical data from a collection. This feature allows you to delete all the data from a collection without affecting data from other collections and without deleting the collection itself. Each collection process represents a statistical monitoring process that you created by starting monitoring for a device configuration feature.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Statistical Data Collection. A table of statistical data collectors appears in the Contents pane. Each row corresponds to a collector for a particular device. Devices are listed alphabetically. The Status field displays whether the collector is running or is stopped.

Step 2 Step 3

Right-click the collection. From the menu bar, choose Actions > Delete Statistical Data. DCNM-LAN deletes all statistical data from the collection.

Deleting a Collection
You can delete a collection of statistical data from a specific device. Each collection process represents a statistical monitoring process that you created by starting monitoring for a device configuration feature.

Note

If you want to delete all data from a collections rather than deleting the collection itself, perform the steps in the Deleting Statistical Data from a Collection section on page 25-5.

BEFORE YOU BEGIN

Determine which collection of data you want to delete.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

25-5

Chapter 25 Configuring Statistical Data Collection

Administering Statistical Data Collection

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Statistical Data Collection. A table of statistical data collectors appears in the Contents pane. Devices are listed alphabetically. Each row corresponds to a collection of statistical data for a particular device.

Step 2 Step 3

Click the collection of data that you want to delete. From the menu bar, choose Actions > Delete Collection. The collection is deleted. You do not need to save your changes.

Deleting Data from the Statistics Database

You can delete statistical data from the statistics database.

Note

If you want to delete all data from a specific collection rather than deleting old data from all collections, perform the steps in the Deleting a Collection section on page 25-5.

BEFORE YOU BEGIN

Determine the date and time of the newest statistical data that you want to delete. When you follow the steps in this procedure, DCNM-LAN deletes all statistics that are older than the date and time that you select.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Statistical Data Collection. The Statistics Database area appears in the Contents pane, below the table of statistical data collectors. From the Delete statistical data older than drop-down list, select the date and time of the newest statistics that you want to delete and click OK. Click Delete. DCNM-LAN deletes all statistics older than the date and time that you specified.

Step 2 Step 3

Enabling and Disabling Automatic Statistical Data Purging

You can enable or disable the automatic purging of statistical data from the DCNM-LAN statistics database.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Statistical Data Collection.

Cisco DCNM Fundamentals Guide, Release 6.x

25-6

OL-25174-02OL-25174-02

Chapter 25

Administering Statistical Data Collection Configuring Statistical Data Collection

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The Statistical Database Administration tab appears in the Details pane, below the table of statistical data collectors.
Step 2

Under Auto Purge Settings, do one of the following:

To enable automatic statistical data purging, check Enable Auto Purge. To disable automatic statistical data purging, uncheck Enable Auto Purge.

Step 3

From the menu bar, choose File > Deploy to save your changes to the DCNM-LAN server.

Configuring Automatic Statistical Data Purge Settings

You can configure when automatic statistical data purging occurs and the criteria that DCNM-LAN uses to determine which statistical data to purge.

BEFORE YOU BEGIN

Determine when you want automatic statistical data purging to occur. A good recommendation is that you configure automatic statistical data purging to occur when DCNM-LAN usage is low. If you perform backups of your DCNM-LAN databases, consider scheduling automatic statistical data purging after database backups have occurred, to ensure that you retain a record of all statistical data. Determine what criteria you want DCNM-LAN to use to determine which statistical data to purge. The two criteria available are as follows:

Age of statistical dataDCNM-LAN can purge all statistical data entries that are older than a specific number of days, weeks, or months. Number of statistical data entries in the databaseWhen the number of statistical data entries in the database exceeds the maximum number that you specify, DCNM-LAN can purge the oldest statistical data entries first until the maximum number is not exceeded.

If you enable both criteria, DCNM-LAN applies them independently of each other.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Statistical Data Collection. The Statistical Database Administration tab appears in the Details pane, below the table of statistical data collectors.

Step 2

Under Purge Threshold, configure the criteria that DCNM-LAN uses to determine which statistical data to purge. You can configure either or both of the criteria usingthe information in Table 25-1.

Table 25-2

Purge Criteria

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

25-7

Chapter 25 Configuring Statistical Data Collection

Administering Statistical Data Collection

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Purge Criteria Age of statistical data

How to Configure
1. 2. 3.

Check Data older than. From the first drop-down list, choose the number of days, weeks, or months. From the second drop-down list, choose Days, Weeks, or Months, as needed. Check Stats. Entries Exceed(0-2147483647). In the box, enter the maximum number of entries that you want to allow in the statistical database.

Number of statistical data entries in the database

1. 2.

Step 3

Configure the action that you want DCNM-LAN to take on statistical database entries that meet the purge criteria. You can choose one of the following:

DeleteDCNM-LAN deletes the database entries that meet the purge criteria. ConsolidateDCNM-LAN merges all statistical data entries that meet the purge criteria into one entry Check the days-of-the-week check boxes to specify which days of the week that you want automatic purging to occur. Use the Run at box to configure the exact time on the specified days that you want automatic statistical data purging to occur.

Step 4

Under Auto Purge Settings, follow these steps to configure when you want automatic purging to occur:
a. b.

Step 5 Step 6

(Optional) If you want to enable automatic statistical data purging, check Enable Auto Purge. From the menu bar, choose File > Deploy to save your changes to the DCNM-LAN server.

Purging Statistical Data Now

You can purge statistical data on demand, using the automatic statistical data purge settings to determine which statistical data are purged.

Tip

If you want to delete statistical data on demand, based on the exact age of the statistical data entries, see the Deleting Data from the Statistics Database section on page 25-6.

BEFORE YOU BEGIN

Ensure that the automatic statistical data purge settings are configured as needed. For more information, see the Configuring Automatic Statistical Data Purge Settings section on page 25-7.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > Statistical Data Collection.

Cisco DCNM Fundamentals Guide, Release 6.x

25-8

OL-25174-02OL-25174-02

Chapter 25

Administering Statistical Data Collection Viewing the Status of Statistical Data Collectors

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The Statistical Database Administration tab appears in the Details pane, below the table of statistical data collectors.
Step 2

Under Purge, click Purge Now. DCNM-LAN deletes statistical data, using the automatic statistical data purge settings to determine which statistical data entries to purge.

Viewing the Status of Statistical Data Collectors

To view the status of statistical data collectors, from the Feature Selector pane, choose DCNM Server Administration > Statistical Data Collection. Collector status and other information appear in the Statistical Data Collectors area in the Contents pane. For information about the fields that appear, see the Field Descriptions for Statistical Data Collection section on page 25-9.

Field Descriptions for Statistical Data Collection

This section includes the following field descriptions for the Statistical Data Collection feature:

Summary Pane, page 25-9 Statistical Database Administration Tab, page 25-10

Summary Pane
Table 25-3 Summary Pane

Field
Statistical Data Collectors

Description Display only. Date and time that the DCNM-LAN client updated information shown on the Content pane. Display only. Name and IP address of the device for the corresponding poller. Display only. Username of the DCNM-LAN user who started monitoring for the chart that corresponds to the collection. Display only. Name and IP address of the device that is providing the statistical data in the collection. Display only. Description of the entity on the device that is providing the statistical data in the collection. For example, if the collection has statistical data for a rule that is assigned the sequence number 10 and is in an IPv4 ACL named acl-01, this field displays acl-01,seqNo=10. If the collection has data for the Ethernet 1/5 port, this field displays Ethernet1/5.

Last Refresh Time Collector ID Owner Device Objects

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

25-9

Chapter 25 Field Descriptions for Statistical Data Collection

Administering Statistical Data Collection

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 25-3 Summary Pane (continued)

Field Collected Statistics

Description Display only. Type of statistical data in the collection. For example, if the collection has statistical data for a rule in an IPv4 ACL, this field displays IpAclAceMatchStatistics. Display only. Whether the collector is started or stopped. Date and time of the newest statistical data to be deleted from the statistics database. There is no default value for this field.

Status
Statistics Database

Delete statistical data older than

Statistical Database Administration Tab

Table 25-4 Statistical Database Administration Tab

Field Delete statistical data older than

Purge

Description Date and time of the newest statistical data to be deleted from the statistics database. There is no default value for this field. Whether automatic statistical data purging deletes or consolidates statistical data entries that trigger the purge threshold. Consolidation merges all statistical data entries that trigger the purge threshold into one entry. Whether, during automatic statistical data purging, DCNM-LAN deletes statistics entries that are older than the age specified in the drop-down lists located to the right of this check box. By default, this check box is unchecked. If you check the check box, the default age is 1 day. Whether, during automatic statistical data purging, DCNM-LAN deletes the oldest statistics entries until the number of entries equals the number in the box located to the right of this check box. By default, this check box is unchecked. If you check the check box, the default number of event is 25,000. Whether automatic purging of statistical data is enabled. By default, this check box is disabled. Days of the week that automatic purging of statistical data occurs. By default, none of the check boxes are checked. If you check the Daily check box, the check boxes for the individual days of the week become unavailable. Time of day that automatic purging of statistical data occurs, on the days of the week that automatic purging is enabled.

Action

Purge Threshold

Data older than

Stat. Entries Exceed

Auto Purge Settings

Enable Auto Purge Run on

Run at

Cisco DCNM Fundamentals Guide, Release 6.x

25-10

OL-25174-02OL-25174-02

Chapter 25

Administering Statistical Data Collection Additional References

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Additional References
For additional information related to administering statistical data collection, see the following sections:

Related Documents, page 25-11 Standards, page 25-11

Related Documents
Related Topic Device discovery Document Title Chapter 16, Administering Device Discovery

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Feature History for Statistical Data Collection

Table 25-5 lists the release history for this feature.
Table 25-5 Feature History for Statistical Data Collection

Feature Name Statistical Data Collection

Releases 5.0(2)

Feature Information No change from Release 4.2.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

25-11

Chapter 25 Feature History for Statistical Data Collection

Administering Statistical Data Collection

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

25-12

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

26

Working with Network Analysis

This chapter describes how to use the Network Analysis (PONG) feature in Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Network Analysis, page 26-1 Licensing Requirements for Network Analysis, page 26-2 Prerequisites for Network Analysis, page 26-2 Guidelines and Limitations for Network Analysis, page 26-2 Using the Network Analysis Feature, page 26-2 Related Documents, page 26-8 Feature History for Network Analysis, page 26-8

Information About Network Analysis

The Network Analysis feature provides you with information to track and monitor the latency between two specified switches in a specified time interval. With Network Analysis, you can determine the health of the network by examining the delay between the two specified points in the network. The Network Analysis feature:

Supports real time and historical network analysis between two user specified devices or ports. The user specifies the required monitoring intervals. Supports an archive of historical Network Analysis measurements for the following:
End to end round trip time. Switching delay at each hop. Link delay between hops per path.

Provides reports that contain the resulting statistical information as a chart or summary table.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

26-1

Chapter 26 Licensing Requirements for Network Analysis

Working with Network Analysis

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Licensing Requirements for Network Analysis

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement The Network Analysis feature requires no license. Any feature not included in a license package is bundled with the Cisco DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Network Analysis

Network Analysis has the following prerequisite:

Network Analysis only pertains to the devices that DCNM-LAN has discovered.

Guidelines and Limitations for Network Analysis

The Network Analysis feature has the following configuration guidelines and limitations:

Specify the IP addresses for devices to monitor the network path between two end hosts or between a host and a server. This allows monitoring of the ingress port of the source connected switch to the egress port of the target switch connected to the end host or server. Specify the IP addresses for switches, VLAN, and optional interface information to monitor the path between them. Specify the threshold level for the round trip time to help evaluate the path latency results.

Using the Network Analysis Feature

This section includes the following topics:

Using Network Analysis, page 26-2 Using the New Path Latency Session Wizard, page 26-4 Viewing Session Statistics, page 26-7

Using Network Analysis

You can use Network Analysis to specify the scope of the analysis and to view the information about the analysis.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Analysis > Path Latency Monitoring (PONG).

Cisco DCNM Fundamentals Guide, Release 6.x

26-2

OL-25174-02OL-25174-02

Chapter 26

Working with Network Analysis Using the Network Analysis Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
The Summary pane appears in the Contents pane. Each row in the table is a path latency session. You are able to view the sessions that you have created as well as the sessions created by other users. See Table 26-1. Users with administrator privileges are allowed to modify other users sessions.
Table 26-1 Information in Summary Pane

Column Session ID Session Name Source Switch Destination Switch VLAN Class of Service (CoS) Round Trip Time (microseconds) Forward Delay (microseconds)

Description Unique ID of the session created by the user. The ID is updated after the user deploys the session. Unique name entered by user for the path latency session. IP address of the source switch from which path latency is monitored. IP address of the destination switch to which the path latency is monitored. VLAN ID through which the actual traffic flows (1 to 4094). Optional value used to filter the traffic monitoring based on class of service value (0 to 7). CoS values are shown in Table 26-2. Minimum, maximum, average and latest value of the round trip time (two way path: source <-> destination) of all the RTT latencies calculated up until current time. Minimum, maximum, average and latest value of the forward delay (forward path: source -> destination) of all the forward delay latencies calculated to the current time. Minimum, maximum, average and latest value of the reverse delay (reverse path: destination -> source) of all the reverse delay latencies calculated to the current time. Creator of the session. Success percentage of the packets traversed from source to destination during the specified time interval. Date and time when the monitoring was started. Column that specifies:

Reverse Delay (microseconds)

Owner Success Percentage Scheduled At Status

Session created Monitoring started Monitoring stopped

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

26-3

Chapter 26 Using the Network Analysis Feature

Working with Network Analysis

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Table 26-2

CoS Values and Corresponding Traffic Types

User Priority 0 1 2 3 4 5 6 7
Step 2

Traffic Type Background Best Effort Excellent Effort Critical Applications Video, < 100 ms latency Voice, < 10 ms latency Internetwork Control Network Control

Above the Summary pane, click the Configure New Rule link to set a threshold rule for one of the following parameters.

Round trip time Forward delay Reverse delay

Note

Clicking Configure New Rule links you to Theshold Rules of the DCNM-LAN Server Administration feature.

Step 3

Above the Summary pane, click the Set Global Threshold link to set a global threshold rule for the following parameters:

Round trip time Forward delay Reverse delay

The global threshold setting is applied to all the sessions in the Summary Table.
Step 4

Above the Summary pane, click the VLAN-CoS button to view the sessions grouped by VLAN-CoS.

Using the New Path Latency Session Wizard

You can use the New Path Latency Session wizard to create a new seesion.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Analysis > Path Latency Monitoring (PONG). The Summary pane appears in the Contents pane. In the Summary pane, right-click and choose New Path Latency Session in the context menu. The New Path Latency Session wizard appears.

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x

26-4

OL-25174-02OL-25174-02

Chapter 26

Working with Network Analysis Using the Network Analysis Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 3

In the Select Session Monitor Option of Interest screen, enter the following:

Session Name (Length: 1 to 256 characters) VLAN (Value: 1 to 4094) Class of Service (CoS)
CoS Values and Corresponding Traffic Types

Table 26-3

User Priority 0 1 2 3 4 5 6 7
Step 4

Traffic Type Background Best Effort Excellent Effort Critical Applications Video, < 100 ms latency Voice, < 10 ms latency Internetwork Control Network Control

In the Select Option section, choose one of the following options:

Monitor latency between source VDC and destination VDC. Monitor latency between source and destination VDC including source switching delay. Monitor latency between source and destination VDC including destination switching delay. Monitor latency between source and destination VDC including both switching delays.

Under the Monitor latency between source VDC and destination VDC option, you can additionally choose to measure the latency between switches that have Fabric Path mode connectivity. The latency measurements are measured between the source and destination switches but do not include the switching delay of both the end switches.

Note

For the switches that are in a classical ethernet cloud, the wizard allows you to choose their VDC MAC addresses/IP addresses/hostnames in the following wizard screen. Click Next to continue.

Step 5

In the Select Source and Destination Switch screen, do the following:

Choose the source switch by clicking on the ellipses next to the Select Source Switch field. Highlight the device in the screen that appears and click OK to enter your selection. Choose the destination switch by clicking on the ellipses next to the Select Destination Switch field. Highlight the device in the screen that appears and click OK to enter your selection.

Depending on the earlier selection that you made in the Select Option section of the wizard, Table 26-4 list the required and optional information that you must enter in the Select Source and Destination Switch screen.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

26-5

Chapter 26 Using the Network Analysis Feature

Working with Network Analysis

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Table 26-4

Required and Optional Information

Option Monitor latency between source VDC and destination VDC Monitor latency between source and destination VDC including source switching delay

Required

Optional

Source and destination

Egress/outbound interface through which the packet flows out from the source. N/A

Source and destination Inject/ingress interface through which the packet needs to be injected from the source switch. Also requires the source static MAC address associated with the interface. Source and destination Egress/outbound interface through which the packet terminates at the destination switch. Also requires the destination static MAC address associated with the interface. Source and destination Inject/ingress interface through which the packet needs to be injected from the source switch. Also requires source static MAC address associated with the interface. Egress/outbound interface through which the packet terminates at the destination switch. Also requires the destination static MAC address associated with the interface.

Monitor latency between source and destination VDC including destination switching delay

Egress/outbound interface through which the packet flows out from the source.

Monitor latency between source and destination VDC including both switching delays

N/A

Note

You can enter any arbitrary unique static MAC address that points to the selected interface. To configure a new static MAC address, use one of the following recommended addresses to avoid any conflict with globally administered MAC addresses (associated with any other host/devices):

X2XX.XXXX.XXXX X6XX.XXXX.XXXX XAXX.XXXX.XXXX XEXX.XXXX.XXXX

Cisco DCNM Fundamentals Guide, Release 6.x

26-6

OL-25174-02OL-25174-02

Chapter 26

Working with Network Analysis Using the Network Analysis Feature

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
where X is a hexadecimal value.

Click Next to continue.

Step 6

In the dialog box that appears, click OK to start input verification. The Input Verification screen appears and the results are displayed. Input verification verifies the following:

Path latency measurement between specified devices. Packet traversal between the specified devices.

If the verification fails, you must specify the information that you entered earlier in the wizard. Table 26-5 lists the additional settings that are available in the Input Verification window:
Table 26-5 Input Verification Settings

Setting Monitor Interval End Time Calculate Jitter No. of Packets to send

Description Interval of time between data collection points. Time of session termination Variance of inter packet RTT delay Packet count to send for the session to measure latency. To calculate jitter (inter packet delay variance), more than 1 packet has to be sent.

Value 0.5 - 5 minutes (Default: 5 minutes) N/A Default: unchecked 1 -5 packets (Default: 1 packet)

Click Finish after a successful verification and to enter the settings.

Viewing Session Statistics

You can view session statistics from the Summary pane.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose Network Analysis > Path Latency Monitoring (PONG). The Summary pane appears in the Contents pane. Right-click a session and choose Go To Statistics in the context menu. The statistics for the session appear as a chart and a table of detailed information in the Details pane. In the Details pane, click the Path Latency tab to display RTT information about each path. In the Details pane, right-click to display a context menu of additional statistical displays:

Step 2

Step 3 Step 4

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

26-7

Chapter 26 Related Documents

Working with Network Analysis

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 5

Path specific switching delaySwitching delay of all the switches traversed in each path. Path specific link delayLink delay at each hop traversed in each path. Switching delay of each switch across different paths traversed in the session. Link delay of each link across different paths traversed in the session.

In the Details pane, click the Session Report tab to display overall statistical information about the session. The information can be exported as an Excel .xls file by cllicking the export button near the top of the table.

Related Documents
For additional information related to the topology map, see the following sections: Related Topic Device discovery Network servers Document Title Chapter 16, Administering Device Discovery Chapter 20, Configuring Network Servers

Feature History for Network Analysis

Table 26-6 lists the release history for this feature.
Table 26-6 Feature History for Topology

Feature Name Network Analysis support

Releases 5.2(0)

Feature Information Support for Network Analysis was added.

Cisco DCNM Fundamentals Guide, Release 6.x

26-8

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

27

Administering DCNM-LAN Server Log Settings

This chapter describes how to administer the DCNM-LAN Server Log Settings feature in Cisco Data Center Network Manager for LAN (DCNM-LAN). This chapter includes the following sections:

Information About Administering DCNM-LAN Server Log Settings, page 27-1 Licensing Requirements for Administering DCNM-LAN Server Log Settings, page 27-2 Prerequisites for Administering DCNM-LAN Server Log Settings, page 27-2 Guidelines and Limitations for Administering DCNM-LAN Server Log Settings, page 27-3 Configuring DCNM-LAN Server Log Settings, page 27-3 Viewing DCNM-LAN Server Log Settings, page 27-4 Field Descriptions for DCNM-LAN Server Log Settings, page 27-5 Additional References, page 27-6 Feature History for DCNM-LAN Server Log Settings, page 27-7

Information About Administering DCNM-LAN Server Log Settings

The DCNM-LAN server maintains a log file of its operations. The log file contains information from DCNM-LAN features and server components.

Note

The DCNM-LAN Server Log Settings feature does not affect logging levels of Cisco NX-OS devices. DCNM-LAN does not support the configuration of device logging levels. This section includes the following topics:

Logging Levels, page 27-2 Log File and Location, page 27-2 Virtualization Support, page 27-2

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

27-1

Chapter 27 Licensing Requirements for Administering DCNM-LAN Server Log Settings

Administering DCNM-LAN Server Log Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Logging Levels
The DCNM-LAN server supports a hierarchy of logging levels, ordered by the severity of log messages. Each level includes messages for that level in addition to all log messages from levels of higher severity. The logging levels, in order from the highest to the lowest severity, are as follows:

Fatal Errors Errors Warnings Information Debugging Verbose

Log File and Location

The DCNM-LAN server writes server log messages to the sys.pipe file at the following location:
INSTALL_DIR\log

By default, when you install the DCNM-LAN server on Microsoft Windows Server, INSTALL_DIR is C:\Program Files\Cisco Systems\dcnm.

Virtualization Support
DCNM-LAN server logs do not contain log messages from Cisco NX-OS devices; therefore, this feature has no effect on virtualization support.

Licensing Requirements for Administering DCNM-LAN Server Log Settings

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement DCNM-LAN Server Log Settings requires no license. Any feature not included in a license package is bundled with the Cisco DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Administering DCNM-LAN Server Log Settings

Administering DCNM-LAN server log settings has the following prerequisites:

You should be familiar with a DCNM-LAN feature before you configure server log settings for it.

Cisco DCNM Fundamentals Guide, Release 6.x

27-2

OL-25174-02OL-25174-02

Chapter 27

Administering DCNM-LAN Server Log Settings Guidelines and Limitations for Administering DCNM-LAN Server Log Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Guidelines and Limitations for Administering DCNM-LAN Server Log Settings

The Administering DCNM-LAN server log settings feature has the following configuration guidelines and limitations:

Setting a logging level to a lower severity results in more messages in the log file. We recommend using the default logging settings unless you are troubleshooting an issue. When you are troubleshooting an issue, consider lowering the logging level severity of the affected feature or server component. After you resolve an issue, consider restoring the logging level of the affected feature or server component to a higher severity.

Configuring DCNM-LAN Server Log Settings

This section includes the following topics:

Configuring the Default Logging Level, page 27-3 Configuring a Unique Logging Level for a Feature or Server Component, page 27-3 Configuring a Feature or Server Component to Use the Default Logging Level, page 27-4

Configuring the Default Logging Level

You can configure the default logging level for all DCNM-LAN features and server components.

BEFORE YOU BEGIN

Determine what the default logging level should be. For more information, see the Logging Levels section on page 27-2.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > DCNM Server Log Settings. The log settings appear in the Contents pane. From the Default Logging Level drop-down list, choose the logging level. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 2 Step 3

Configuring a Unique Logging Level for a Feature or Server Component

You can configure a logging level of a feature or server component that is independent of the default logging level.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

27-3

Chapter 27 Viewing DCNM-LAN Server Log Settings

Administering DCNM-LAN Server Log Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
BEFORE YOU BEGIN
Determine what the logging level of the feature or service should be. For more information, see the Logging Levels section on page 27-2.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > DCNM Server Log Settings. The log settings appear in the Contents pane. Find the feature or server component that you want to configure with a unique logging level. Uncheck Default to the right of the feature or server component. The logging level drop-down list for the feature or server component becomes available. From the logging level drop-down list, choose the logging level. For more information, see the Logging Levels section on page 27-2. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 2 Step 3

Step 4 Step 5

Configuring a Feature or Server Component to Use the Default Logging Level

You can configure a feature or server component to use the default logging level.

BEFORE YOU BEGIN

Ensure that the default logging level is appropriate for the feature or service. For more information, see the Logging Levels section on page 27-2.

DETAILED STEPS
Step 1

From the Feature Selector pane, choose DCNM Server Administration > DCNM Server Log Settings. The log settings appear in the Contents pane. Find the feature or server component that you want to use the default logging level. Check Default to the right of the feature or service. The logging level drop-down list for the feature or server component becomes unavailable. From the menu bar, choose File > Deploy to apply your changes to the DCNM-LAN server.

Step 2 Step 3

Step 4

Viewing DCNM-LAN Server Log Settings

To view DCNM-LAN server user accounts, from the Feature Selector pane, choose DCNM Server Administration > DCNM Server Log Settings . The default logging level, feature logging settings, and server component logging settings appear in the Contents pane. For information about the fields that appear, see the Field Descriptions for DCNM-LAN Server Log Settings section on page 27-5.

Cisco DCNM Fundamentals Guide, Release 6.x

27-4

OL-25174-02OL-25174-02

Chapter 27

Administering DCNM-LAN Server Log Settings Field Descriptions for DCNM-LAN Server Log Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Field Descriptions for DCNM-LAN Server Log Settings

This section includes the following field descriptions for DCNM-LAN server log settings:

DCNM-LAN Server Log Settings Contents Pane, page 27-5

DCNM-LAN Server Log Settings Contents Pane

Table 27-1 DCNM-LAN Server Log Settings Contents Pane

Field Default Logging Level

Description Logging level for the features or server components whose Default check box is checked. The default value for this list is Informational. For more information about logging levels, see the Logging Levels section on page 27-2. Whether logging for the corresponding feature uses the default logging level or the logging level specified for the feature. When a Default check box is checked, the logging level list for the corresponding feature is unavailable. By default, these check boxes are unchecked. Logging level for the AAA feature. Logging level for the access control list feature. Logging level for the 802.1X feature. Logging level for the Gateway Load-Balancing Protocol feature. Logging level for the Interfaces feature. Logging level for the keychain management feature. Logging level for the layer 2 security feature, which are as follows:

DCNM-LAN Features

Default

AAA ACL Dot1X GLBP Interfaces Key Chain Layer 2 Security

Dynamic ARP inspection Port security DHCP snooping IP Source Guard Traffic storm control

Object Tracking Port Channel SPAN Spanning Tree Tunnel Virtual Devices VLAN FabricExtender VPC

Logging level for the object tracking feature. Logging level for the port security feature. Logging level for the SPAN feature. Logging level for the STP feature. Logging level for the tunnel interface management feature. Logging level for the virtual device context feature. Logging level for the VLAN feature. Logging level for the Fabric Extender feature. Logging level for the vPC feature.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

27-5

Chapter 27 Additional References

Administering DCNM-LAN Server Log Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 27-1 DCNM-LAN Server Log Settings Contents Pane (continued)

Field HSRP DEVICE GROUP Default

Description Logging level for the HSRP feature. Logging level for the Device Groups feature. Whether logging for the corresponding server component uses the default logging level or the logging level specified for the component. When a Default check box is checked, the logging level list for the corresponding component is unavailable. By default, these check boxes are unchecked. Logging level for the event component, which includes messages about how DCNM-LAN processes the system and accounting logs it retrieves from devices and also events generated by DCNM-LAN. Logging level for the statistical data collection component. Logging level for the configuration archive component, used by the Configuration Change Management feature. Logging level for the component that connects the DCNM-LAN server to devices. Logging level for the component that performs device discovery.

DCNM-LAN Server Components

Event

Statistics Collection Config Archive Device Connections Device Discovery

Additional References
For additional information related to administering DCNM-LAN server log settings, see the following sections:

Related Documents, page 27-6 Standards, page 27-6

Related Documents
Related Topic Troubleshooting DCNM-LAN Document Title Chapter 30, Troubleshooting DCNM-LAN

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Cisco DCNM Fundamentals Guide, Release 6.x

27-6

OL-25174-02OL-25174-02

Chapter 27

Administering DCNM-LAN Server Log Settings Feature History for DCNM-LAN Server Log Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Feature History for DCNM-LAN Server Log Settings

Table 27-2 lists the release history for this feature.
Table 27-2 Feature History for DCNM-LAN Server Log Settings

Feature Name Device Groups logging

Releases 5.0(2)

Feature Information Support was added for configuring the logging level for the Device Groups feature.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

27-7

Chapter 27 Feature History for DCNM-LAN Server Log Settings

Administering DCNM-LAN Server Log Settings

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

27-8

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

28

Starting and Stopping Cisco DCNM-LAN Servers

This chapter describes how to start or stop Cisco Data Center Network Manager for LAN (DCNM-LAN) servers. This chapter includes the following sections:

Information About Starting and Stopping DCNM-LAN Servers, page 28-1 Licensing Requirements for Starting and Stopping Cisco DCNM-LAN Servers, page 28-1 Starting DCNM-LAN Servers, page 28-2 Stopping DCNM-LAN Servers, page 28-5 Related Documents, page 28-8 Feature History for Starting and Stopping a DCNM-LAN Server, page 28-9

Information About Starting and Stopping DCNM-LAN Servers

Starting and stopping DCNM-LAN servers is a necessary part of server maintenance, such as during database backup, cleaning, or restoration. In a clustered server deployment, the order in which you start DCNM-LAN servers determines which server is the master server. This chapter provides detailed steps for starting and stopping DCNM-LAN servers for both single-server deployments and clustered-server deployments.

Licensing Requirements for Starting and Stopping Cisco DCNM-LAN Servers

The following table shows the licensing requirements for this feature: Product Cisco DCNM-LAN License Requirement Starting and stopping Cisco DCNM-LAN servers requires no license. Any feature not included in a license package is bundled with the Cisco DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

28-1

Chapter 28 Starting DCNM-LAN Servers

Starting and Stopping Cisco DCNM-LAN Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Starting DCNM-LAN Servers

This section includes the following topics:

Starting a Single DCNM-LAN Server, page 28-2 Starting a Cluster of DCNM-LAN Servers, page 28-3

Starting a Single DCNM-LAN Server

You can start a single DCNM-LAN server. The procedures for starting a single DCNM-LAN server differ for systems using the supported Microsoft Windows Server and Red Hat Enterprise Linux (RHEL) operating systems, as described in the following topics:

Starting a Single DCNM-LAN Server (Microsoft Windows Server), page 28-2 Starting a Single DCNM-LAN Server (RHEL), page 28-2

Starting a Single DCNM-LAN Server (Microsoft Windows Server)

On a server system running Microsoft Windows Server, you can start a DCNM-LAN server through the Windows services or by clicking the Start DCNM-LAN Server icon.

BEFORE YOU BEGIN

You must have installed the DCNM-LAN server. If you are starting a server cluster, ensure that you are starting the server in the correct order. For more information, see the Starting a Cluster of DCNM-LAN Servers section on page 28-3.

DETAILED STEPS
Step 1

Open the Control Panel window and choose Administrative Tools > Services. The Services window opens. Right-click Cisco DCNM Server and choose Start.

Step 2

Note

Alternatively, you can choose Start > All Programs > Cisco DCNM Server > Start DCNM Server; however, the location of shortcuts depends upon the choices you made when you installed the DCNM-LAN server.

A splash screen opens while the DCNM-LAN server starts. This screen closes once the DCNM-LAN server is running.

Starting a Single DCNM-LAN Server (RHEL)

On a server system that runs RHEL, you can start a DCNM-LAN server with the Start_DCNM_LAN_Server script. The script is located in your home folder or the folder that was specified when setting up the link folder during the installation of Cisco DCNM-LAN.

Cisco DCNM Fundamentals Guide, Release 6.x

28-2

OL-25174-02OL-25174-02

Chapter 28

Starting and Stopping Cisco DCNM-LAN Servers Starting DCNM-LAN Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

Start_DCNM_LAN_Server launches /usr/local/Cisco/dcm/dcnm/bin/startdcnm.sh.

BEFORE YOU BEGIN

The DCNM-LAN server must be installed. If you are starting a server cluster, ensure that you are starting the server in the correct order. For more information, see the Starting a Cluster of DCNM-LAN Servers section on page 28-3.

DETAILED STEPS
Step 1

Use the Start_DCNM_LAN_Server script to start the server on a RHEL operating system. The DCNM-LAN server opens a server console window and displays the processes it runs to start the server. The server is running when you see a Started in Xm:XXs:XXXms message.

Starting a Cluster of DCNM-LAN Servers

Depending on the operating system of the secondary server, the DCNM-LAN server can be started using the Windows GUI, the CLI, or the DCNM Install Manager tool. You can use the CLI or the DCNM Install Manager tool for a secondary server running RHEL. For a secondary server running Microsoft Windows, the DCNM-LAN server is started with the Windows GUI.

Starting with Windows GUI or RHEL CLI

Starting a cluster of DCNM-LAN servers requires starting each server individually; however, the order of server startup is important. The server with the oldest start time performs the master server role in the server cluster.

BEFORE YOU BEGIN

We recommend that you use the primary installation server as the master server. For information about deploying a clustered-server environment, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. If any server in the cluster is running, stop it prior to starting the cluster. The only way that you can control which server is the master server is by ensuring that the master server is started before the other servers start. For more information, see the Stopping DCNM-LAN Servers section on page 28-5.

DETAILED STEPS
Step 1

Start the server that you want to be the master server of the cluster. To do so, follow the steps for starting a single DCNM-LAN server for the applicable operating system:

Starting a Single DCNM-LAN Server (Microsoft Windows Server), page 28-2 Starting a Single DCNM-LAN Server (RHEL), page 28-2

Step 2

Wait for the master server to finish starting.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

28-3

Chapter 28 Starting DCNM-LAN Servers

Starting and Stopping Cisco DCNM-LAN Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 3

One at a time, start the other servers in the cluster. After starting a server, wait at least one minute before starting the next server. This delay helps ensure faster stabilization of the server cluster. For each server, follow the steps for starting a single DCNM-LAN server for the applicable operating system:

Starting a Single DCNM-LAN Server (Microsoft Windows Server), page 28-2 Starting a Single DCNM-LAN Server (RHEL), page 28-2

Starting with Install Manager

DCNM Install Manager is a GUI tool for servers that run Linux. It is designed to assist in performing silent mode operations on secondary servers (remote nodes).

Note

DCNM Install Manager does not support Windows servers.

DETAILED STEPS
Step 1

To access Install Manager, navigate to the dcnm-install-manager.sh file that is located in the bin folder where the DCNM-LAN server was installed. The default bin folder location for servers running Linux is /usr/local/Cisco/dcm/dcnm/bin. Double click the dcnm-install-manager.sh file to launch Install Manager. In the tool bar, click the New icon near the top of the Install Manager GUI for every secondary server. A new row in the list of Server Nodes is created every time the New icon is clicked.

Step 2 Step 3

Note

In the toolbar, click the Delete icon to delete a selected row in the list of Server Nodes. This step does not delete a secondary server from the clustered-server environment.

Step 4

For each secondary server represented by a row in the list of Server Nodes, enter the following:

Server name or IP address in the Server Name/IP Address field. Protocol used for connectivity in the Protocol field. The protocol is either Telnet or SSH. User credentials (user ID and password) used for connecting to the secondary server in the User Credentials field. The user credentials are used for SSH connectivity to the server. Telnet connectivity to the server does not require user credentials. Alternatively, default user credentials may be set by entering the credentials in the Default Credentials section of the GUI. The default credentials are used when the User Credential field is blank.

(Optional) Comments that may be useful to identify the secondary server in the Comments field.

The Last Action Status column in the list of Server Nodes includes the success or failure status of the last performed action. Clicking the + icon for the Last Action Status expands the display to show the entire log of actions performed on the server.

Cisco DCNM Fundamentals Guide, Release 6.x

28-4

OL-25174-02OL-25174-02

Chapter 28

Starting and Stopping Cisco DCNM-LAN Servers Stopping DCNM-LAN Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 5 Step 6

In the list of Server Nodes, select the secondary servers to start. In the toolbar, click the Verify icon to verify the connectivity to the selected secondary servers. Correct any connectivity issues before continuing. In the toolbar, click the Start icon to start the selected secondary servers.

Step 7

Note

The Install Manager is a standalone application. The settings specified are not saved and are not persistent. The settings are lost when the Install Manager GUI is closed.

Stopping DCNM-LAN Servers

This section includes the following topics:

Stopping Single DCNM-LAN Servers, page 28-5 Stopping a Cluster of DCNM-LAN Servers, page 28-6

Stopping Single DCNM-LAN Servers

You can stop a single DCNM-LAN server. The steps for stopping a single DCNM-LAN server differ for systems using the supported Microsoft Windows Server and RHEL operating systems, as described in the following topics:

Stopping a Single DCNM-LAN Server (Microsoft Windows Server), page 28-5 Stopping a Single DCNM-LAN Server (RHEL), page 28-6

Stopping a Single DCNM-LAN Server (Microsoft Windows Server)

On a server system that runs Microsoft Windows Server, you can stop a DCNM-LAN server through the Windows services or by clicking the Stop DCNM Server icon.

DETAILED STEPS
Step 1

Open the Control Panel window and choose Administrative Tools > Services. A window opens listing the Windows services. Right-click Cisco DCNM Server and choose Stop.

Step 2

Note

Alternatively, you can choose Start > All Programs > Cisco DCNM Server > Stop DCNM Server; however, the location of shortcuts depends upon the choices you made when you installed the DCNM-LAN server.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

28-5

Chapter 28 Stopping DCNM-LAN Servers

Starting and Stopping Cisco DCNM-LAN Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
A splash screen opens while the DCNM-LAN server begins to shut down. When the DCNM-LAN server has stopped, the splash screen closes.

Stopping a Single DCNM-LAN Server (RHEL)

On a server system that runs RHEL, you can stop a DCNM-LAN server with the Stop_DCNM_LAN_Server script. The script is located in your home folder or the folder that was specified when setting up the link folder during the installation of Cisco DCNM-LAN.

Note

Stop_DCNM_LAN_Server launches /usr/local/Cisco/dcm/dcnm/bin/stopdcnm.sh.

DETAILED STEPS
Step 1

Use the Stop_DCNM_LAN_Server script to stop the server on a RHEL operating system. The DCNM-LAN server opens a server console window and displays the processes that it runs to stop the server. The server is stopped when you see a Stopped at Xm:XXs:XXXms message.

Stopping a Cluster of DCNM-LAN Servers

Depending on the operating system of the secondary server, the DCNM-LAN server can be stopped using the CLI or the DCNM Install Manager tool. You can use the CLI or the DCNM Install Manager tool for a secondary server running RHEL. For a secondary server running Microsoft Windows, the DCNM-LAN server is stopped with the CLI.

Stopping with CLI

If you have a clustered-server DCNM-LAN deployment, you can use the stop-dcnm-cluster script to stop all the servers in the cluster.

BEFORE YOU BEGIN

Ensure that you know which server is currently the master server in the DCNM-LAN server cluster. You can use the Cluster Administration feature to do so. For more information, see the Viewing Server Information section on page 22-4.

DETAILED STEPS
Step 1 Step 2

On the master server, access a command prompt. Use the cd command to change the directory to the bin directory under the Cisco DCNM installation directory, as follows: cd path

Cisco DCNM Fundamentals Guide, Release 6.x

28-6

OL-25174-02OL-25174-02

Chapter 28

Starting and Stopping Cisco DCNM-LAN Servers Stopping DCNM-LAN Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
where path is the relative or absolute path to the bin directory. For Microsoft Windows, the default path to the Cisco DCNM bin directory is C:\Program Files\Cisco Systems\dcm\dcnm\bin. For RHEL, the default path to the bin directory is /usr/local/cisco/dcm/dcnm/bin.
Step 3

Run the stop-dcnm-cluster script. The script name depends upon the server operating system, as shown in the following table: Server Operating System Microsoft Windows Linux Stop DCNM Cluster Script stop-dcnm-cluster.bat stop-dcnm-cluster.sh

The script instructs each DCNM-LAN server in the cluster to stop.

Example
The following example from a Microsoft Windows server shows how to stop a cluster of DCNM-LAN servers, with DCNM-LAN installed in the default directory:
C:\Documents and Settings\Administrator>cd "C:\Program Files\Cisco Systems\dcm\dcnm\bin" C:\Program Files\Cisco Systems\dcm\dcnm\bin>stop-dcnm-cluster.bat C:\Program Files\Cisco Systems\dcm\dcnm\bin>set JAVA_HOME=C:\Program Files\Cisco Systems\ dcm\java\jre1.5 C:\Program Files\Cisco Systems\dcm\dcnm\bin>"C:\Program Files\Cisco Systems\dcm\ jboss-4.2.2.GA\bin\twiddle.bat" -s 172.28.254.254:1099 invoke "com.cisco.dcbu.dcm:service=ClusterServerInfo" stopServerInstancesInCluster 10 Shutdown Triggered for all Servers Successfully C:\Program Files\Cisco Systems\dcm\dcnm\bin>

Stopping with Install Manager

Cisco DCNM Install Manager is a GUI tool for servers that runs Linux. It is designed to assist in performing silent mode operations on secondary servers (remote nodes).

Note

Cisco DCNM Install Manager does not support Windows servers.

DETAILED STEPS
Step 1

To access Install Manager, navigate to the dcnm-install-manager.sh file that is located in the bin folder where the DCNM-LAN server was installed. The default bin folder location for servers running Linux is /usr/local/Cisco/dcm/dcnm/bin. Double click the dcnm-install-manager.sh file to launch Install Manager. In the toolbar, click the New icon near the top of the Install Manager GUI for every secondary server. A new row in the list of Server Nodes is created every time that the New icon is clicked.

Step 2 Step 3

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

28-7

Chapter 28 Related Documents

Starting and Stopping Cisco DCNM-LAN Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Note

In the toolbar, click the Delete icon to delete a selected row in the list of Server Nodes. This step does not delete a secondary server from the clustered-server environment.

Step 4

For each secondary server represented by a row in the list of Server Nodes, enter the following:

Server name or IP address in the Server Name/IP Address field. Protocol used for connectivity in the Protocol field. The protocol is either Telnet or SSH. User credentials (user ID and password) used for connecting to the secondary server in the User Credentials field. The user credentials are used for SSH connectivity to the server. Telnet connectivity to the server does not require user credentials. Alternatively, default user credentials can be set by entering the credentials in the Default Credentials section of the GUI. The default credentials are used when the User Credential field is blank.

(Optional) Comments that might be useful to identify the secondary server in the Comments field.

The Last Action Status column in the list of Server Nodes includes the success or failure status of the last performed action. Clicking the + icon for the Last Action Status expands the display to show the entire log of actions performed on the server.
Step 5 Step 6

In the list of Server Nodes, choose the secondary servers to stop. In the toolbar, click the Verify icon to verify the connectivity to the selected secondary servers. Correct any connectivity issues before continuing. In the toolbar, click the Stop icon to stop the selected secondary servers.

Step 7

Note

The Install Manager is a standalone application. The settings specified are not saved and are not persistent. The settings are lost when you exit the Install Manager GUI.

Related Documents
Related Topic Deploying single DCNM-LAN servers and deploying DCNM-LAN server clusters Viewing server cluster information Backing up, cleaning, and restoring DCNM-LAN databases Document Title Cisco DCNM Installation and Licensing Guide, Release 5.x Chapter 22, Working with Cluster Administration Chapter 29, Maintaining the Cisco DCNM-LAN Database

Cisco DCNM Fundamentals Guide, Release 6.x

28-8

OL-25174-02OL-25174-02

Chapter 28

Starting and Stopping Cisco DCNM-LAN Servers Feature History for Starting and Stopping a DCNM-LAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Feature History for Starting and Stopping a DCNM-LAN Server

Table 28-1 lists the release history for this feature.
Table 28-1 Feature History for Starting and Stopping a DCNM-LAN Server

Feature Name Starting and stopping a cluster of servers

Releases 5.0(2)

Feature Information Support for starting and stopping a cluster of servers was introduced.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

28-9

Chapter 28 Feature History for Starting and Stopping a DCNM-LAN Server

Starting and Stopping Cisco DCNM-LAN Servers

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

28-10

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

CH A P T E R

29

Maintaining the Cisco DCNM-LAN Database

This chapter describes how to maintain the Cisco Data Center Network Manager for LAN (DCNM-LAN) database. This chapter includes the following sections:

Information About Database Maintenance, page 29-1 Licensing Requirements for Database Maintenance, page 29-3 Prerequisites for Database Maintenance, page 29-3 Guidelines and Limitations for Database Maintenance, page 29-3 Performing Database Maintenance, page 29-4 Additional References, page 29-9 Feature History for DCNM-LAN Database Maintenance, page 29-9

Information About Database Maintenance

DCNM-LAN uses a PostgreSQL database or an Oracle database to store all data, including configuration information from managed devices, events and statistical data gathered from managed devices, and DCNM-LAN user information. In addition to scripts that you can run to perform database maintenance, DCNM-LAN provides features to help you delete events and statistical data that you no longer need. This section includes the following topics:

Automatic and Manual Purging of Data, page 29-1 Database Backup, page 29-2 Database Clean, page 29-2 Database Restore, page 29-2

Automatic and Manual Purging of Data

You can use the Auto-Synchronization with Devices feature to delete unwanted event data and the Statistical Data Collection feature to delete unwanted statistical data. DCNM-LAN supports automatic purging of both types of data. You can configure the following aspects of automatic data purging:

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

29-1

Chapter 29 Information About Database Maintenance

Maintaining the Cisco DCNM-LAN Database

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Days of the week and time of day that automatic purging occurs. Whether DCNM-LAN determines which data to purge by the age of the data or by a maximum number of database entries. For event-related data, whether DCNM-LAN determines which events to purge by event severity.

We recommend that you configure automatic purging of events and statistical data to ensure that the DCNM-LAN database size does not grow too large. You can also manually purge events and statistical data. For more information, see the following sections:

Automatic and Manual Purging of Event Data, page 23-2 Automatic and Manual Purging of Statistical Data, page 25-2

Database Backup
You can use the Cisco DCNM database backup script to create a backup file of the DCNM-LAN database. We strongly recommend that you regularly back up the DCNM-LAN database and that you archive backup files in a secure location that is not on the DCNM-LAN server system. You should retain the backup files as long as required by the standards of your organization.

Database Clean
You can use the Cisco DCNM database clean script to clean the DCNM-LAN database. Cleaning removes all DCNM-LAN data from the database and is a necessary step prior to restoring the DCNM-LAN database. Any database records that have not been backed up are lost when you clean the database. You can also clean the database if you want to delete all data and rebuild your DCNM-LAN implementation without restoring data from a backup.

Note

Database clean script is unavailable from the DCNM Everest release onwards.

Database Restore
You can use the Cisco DCNM database restore script to restore the DCNM-LAN database from a backup file. The backup file must have been created by the DCNM-LAN database backup script included in the same release of DCNM-LAN that you are restoring the data to. For example, if you are running Cisco DCNM Release 5.0(2), you should only perform database restoration from a backup of Cisco DCNM Release 5.0(2). Also, the backup file must have been created from the same database type and release that you are restoring the data to. For example, if you are restoring data to an Oracle 11g database, the backup file must have been created from an Oracle 11g database. Before you restore a DCNM-LAN database, you should clean the database. Restoring a database without cleaning the database can have unpredictable results.

Cisco DCNM Fundamentals Guide, Release 6.x

29-2

OL-25174-02OL-25174-02

Chapter 29

Maintaining the Cisco DCNM-LAN Database Licensing Requirements for Database Maintenance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Licensing Requirements for Database Maintenance

The following table shows the licensing requirements for this feature: Product DCNM-LAN License Requirement Database maintenance requires no license. Any feature not included in a license package is bundled with the DCNM-LAN and is provided at no charge to you. For information about obtaining and installing a Cisco DCNM LAN Enterprise license, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Prerequisites for Database Maintenance

Database maintenance has the following prerequisites:

You must have successfully installed the DCNM-LAN server. Cleaning the DCNM-LAN database requires that you stop the DCNM-LAN server. Restoring the DCNM-LAN database requires the following:
You must have a backup file created from exactly the same release of DCNM-LAN that you are

restoring with the backup file.

You must have a backup file created from exactly the same database type and release that you

are restoring data to.

You must have a backup file that was created from a DCNM-LAN database running in the same

operating system as the database that you want to restore. For example, backup files made from a database running in Microsoft Server 2003 can only be used to restore other DCNM-LAN databases running in Microsoft Server 2003.

Guidelines and Limitations for Database Maintenance

Database maintenance has the following configuration guidelines and limitations:

We recommend that you configure automatic purging of statistical data and event data to ensure that the DCNM-LAN database size does not grow too large. We recommend that you perform backups on a regular basis. Follow the standards of your organization to determine how frequently you should perform backups. You can only restore a DCNM-LAN database from a backup of the same release of DCNM-LAN. For example, if you are running Cisco DCNM Release 5.0(2), you should only perform database restoration from a backup of Cisco DCNM Release 5.0(2). You can only restore a DCNM-LAN database from a backup of the same database type and release as the current database. For example, if the current database is an Oracle 11g database, you can only restore it with a backup file made from an Oracle 11g database. You can only restore a DCNM-LAN database from a backup file that was made from a DCNM-LAN database running in the same operating system as the database that you want to restore. For example, backup files made from a database running in Microsoft Server 2003 can only be used to restore other DCNM-LAN databases running in Microsoft Server 2003.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

29-3

Chapter 29 Performing Database Maintenance

Maintaining the Cisco DCNM-LAN Database

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Performing Database Maintenance

This section includes the following topics:

Backing Up the DCNM-LAN Database, page 29-4 Cleaning a DCNM-LAN Database, page 29-5 Restoring a DCNM-LAN Database from a Backup File, page 29-7

Backing Up the DCNM-LAN Database

You can back up the DCNM-LAN database with the backup script. The DCNM-LAN server installer configures the backup script with the database username and database name that you specified during server installation.

DETAILED STEPS
Step 1 Step 2

On the DCNM-LAN server, access a command prompt. Use the cd command to change the directory to the bin directory under the Cisco DCNM installation directory, as follows: cd path where path is the relative or absolute path to the bin directory. For Microsoft Windows, the default path to the bin directory is C:\Program Files\dcm\dcnm\bin. For RHEL, the default path to the bin directory is /usr/local/cisco/dcm/dcnm/bin.

Step 3

Run the Cisco DCNM database backup script. The script name depends upon the server operating system and database type, as shown in the following table: Server Operating System Microsoft Windows Linux Database Type PostgreSQL Oracle PostgreSQL Oracle Backup Script Name backup-pgsql-dcnm-db.bat backup-oracle-dcnm-db.bat backup-pgsql-dcnm-db.sh backup-oracle-dcnm-db.sh

Step 4 Step 5 Step 6

Enter the filename for the backup that you are creating. At the confirmation prompt, enter y to continue with the backup. Verify that the backup file was created as you specified and has a file size greater than zero.

On Linux, use the ls -l command. On Microsoft Windows, use the dir command.

Step 7

Store the backup file in a safe location. We recommend that you copy the backup file to a secure location that is off the DCNM-LAN server system so that you can protect your data from the potential of a catastrophic hardware failure.

Cisco DCNM Fundamentals Guide, Release 6.x

29-4

OL-25174-02OL-25174-02

Chapter 29

Maintaining the Cisco DCNM-LAN Database Performing Database Maintenance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Example
The following example from a Windows server shows how to create a backup named masterbackup.bkp from a PostgreSQL DCNM-LAN database that was installed using default values:
C:\Documents and Settings\Administrator>cd "C:\Program Files\Cisco Systems\dcm\dcnm\bin" C:\Program Files\Cisco Systems\dcm\dcnm\bin>backup-pgsql-dcnm-db.bat ======================================================== Database Postgres Environment PostgreSQL Bin Path : ""C:\Program Files\Cisco Systems\dcm\db"\bin" DCNM Database Name : "dcmdb" DCNM Database User Name : "dcnmuser" ========================================================

Please enter the filename to be used for Database Backup:masterbackup.bkp "" "Database Schema "dcnmuser" will be backed up in filename : masterbackup.bkp" "" Continue y/n [n] : y . . . Database backup File: woobie1 Operation Completed C:\Program Files\Cisco Systems\dcm\dcnm\bin>dir masterbackup.bkp Volume in drive C has no label. Volume Serial Number is D415-F632 Directory of C:\Program Files\PostgreSQL\8.2\bin 06/15/2009 01:53 PM 900,129 masterbackup.bkp 1 File(s) 900,129 bytes 0 Dir(s) 23,960,858,624 bytes free C:\Program Files\Cisco Systems\dcm\dcnm\bin>

Cleaning a DCNM-LAN Database

You can use the DCNM-LAN database clean script to clean the database, which deletes all data from the DCNM-LAN database. You might want to clean the database for the following reasons:

You want to restore the DCNM-LAN database from a backup. You want to delete all data and rebuild your DCNM-LAN implementation without restoring data from a backup.

The DCNM-LAN server installer configures the clean script with the database username and database name that you specified during the server installation.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

29-5

Chapter 29 Performing Database Maintenance

Maintaining the Cisco DCNM-LAN Database

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
BEFORE YOU BEGIN
Back up the DCNM-LAN database. Any data not preserved in a backup is lost when you clean the database. Stop the DCNM-LAN server. The DCNM-LAN server must be down before you can finish the database cleaning procedure. For more information, see the Stopping DCNM-LAN Servers section on page 28-5.

DETAILED STEPS
Step 1 Step 2 Step 3

On the DCNM-LAN server, access a command prompt. If you have not already done so, stop the DCNM-LAN server. For more information, see the Stopping DCNM-LAN Servers section on page 28-5. Use the cd command to change the directory to the bin directory under the Cisco DCNM installation directory, as follows: cd path where path is the relative or absolute path to the bin directory. For Microsoft Windows, the default path to the bin directory is C:\Program Files\dcm\dcnm\bin. For RHEL, the default path to the bin directory is /usr/local/cisco/dcm/dcnm/bin.

Step 4

Run the Cisco DCNM database clean script. The script name depends upon the server operating system and database type, as shown in the following table: Server Operating System Microsoft Windows Linux Database Type PostgreSQL Oracle PostgreSQL Oracle Clean Script clean-pgsql-dcnm-db.bat clean-oracle-dcnm-db.bat clean-pgsql-dcnm-db.sh clean-oracle-dcnm-db.sh

Step 5 Step 6

At the confirmation prompt, enter y to continue with cleaning the database. If you want to restore the DCNM-LAN database from a backup, proceed to the Restoring a DCNM-LAN Database from a Backup File section on page 29-7. Do not start the DCNM-LAN server. If you do not want to restore the DCNM-LAN database from a backup and want to rebuild your DCNM-LAN implementation manually, start the DCNM-LAN server. See the Starting a Single DCNM-LAN Server section on page 28-2.

Example
The following example from a Windows server shows how to clean a PostgreSQL DCNM-LAN database that was installed using default values:
C:\Documents and Settings\Administrator>cd "C:\Program Files\Cisco Systems\dcm\dcnm\bin" C:\Program Files\Cisco Systems\dcm\dcnm\bin>clean-pgsql-dcnm-db.bat ========================================================

Cisco DCNM Fundamentals Guide, Release 6.x

29-6

OL-25174-02OL-25174-02

Chapter 29

Maintaining the Cisco DCNM-LAN Database Performing Database Maintenance

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Database Postgres Environment PostgreSQL Bin Path : ""C:\Program Files\Cisco Systems\dcm\db"\bin" DCNM Database Name : "dcmdb" DCNM Database User Name : "dcnmuser" DCNM Database SuperUser Name : "cisco" =========================================================

*************************************************************************** PLEASE MAKE SURE THE DCNM SERVICE IS SHUTDOWN BEFORE RUNNING THIS SCRIPT!! ***************************************************************************

DCNM database schema

"dcnmuser" will be deleted permanently...

Please Confirm y/n [n] : y . . . Operation Completed C:\Program Files\Cisco Systems\dcm\dcnm\bin>

Restoring a DCNM-LAN Database from a Backup File

You can use the Cisco DCNM database restore script to restore the DCNM-LAN database from a backup file. The restore script cleans the database prior to restoring it.

BEFORE YOU BEGIN

Locate the backup file that you want to use to restore the DCNM-LAN database. Ensure that the backup file that you want to use to restore the database was made from the same release of DCNM-LAN. For example, you can only restore a Cisco DCNM Release 5.0(2) database from a backup file created from a Cisco DCNM Release 5.0(2) database. Ensure that the backup file was made from the same database type and release as the current database. For example, you can only restore an Oracle 11g database from a backup file made from an Oracle 11g database. Ensure that the backup file was made from a DCNM-LAN database running in the same operating system as the DCNM-LAN server that you want to restore the database to. For example, backup files made from a database running in Microsoft Server 2003 can only be used to restore other DCNM-LAN databases running in Microsoft Server 2003. The DCNM-LAN server must be stopped while you are restoring the database.

DETAILED STEPS
Step 1 Step 2

On the DCNM-LAN server, access a command prompt. If you have not already done so, stop the DCNM-LAN server. For more information, see the Stopping DCNM-LAN Servers section on page 28-5.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

29-7

Chapter 29 Performing Database Maintenance

Maintaining the Cisco DCNM-LAN Database

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 3

Use the cd command to change the directory to the bin directory under the Cisco DCNM installation directory, as follows: cd path where path is the relative or absolute path to the bin directory. For Microsoft Windows, the default path to the bin directory is C:\Program Files\dcm\dcnm\bin. For RHEL, the default path to the bin directory is /usr/local/cisco/dcm/dcnm/bin.

Step 4

Run the Cisco DCNM database restore script. The script name depends upon the server operating system and database type, as shown in the following table: Server Operating System Microsoft Windows Linux Database Type PostgreSQL Oracle PostgreSQL Oracle Restore Script restore-pgsql-dcnm-db.bat restore-oracle-dcnm-db.bat restore-pgsql-dcnm-db.sh restore-oracle-dcnm-db.sh

Step 5 Step 6 Step 7

Enter the name of the backup file that you want to use to restore the DCNM-LAN database. At the confirmation prompt, enter y to continue with the database restore. To resume using DCNM-LAN, start the DCNM-LAN server. See the Starting a Single DCNM-LAN Server section on page 28-2.

Example
The following example from a Microsoft Windows server shows how to restore a DCNM-LAN PostgreSQL database that was installed using default values and using a backup file named masterbackup.bkp that exists in the bin directory Cisco DCNM installation directory:
C:\Documents and Settings\Administrator>cd "C:\Program Files\Cisco Systems\dcm\dcnm\bin"

C:\Program Files\Cisco Systems\dcm\dcnm\bin>restore-pgsql-dcnm-db.bat ======================================================== Database Postgres Environment PostgreSQL Bin Path : ""C:\Program Files\Cisco Systems\dcm\db"\bin" DCNM Database Name : "dcmdb" DCNM Database User Name : "dcnmuser" ========================================================

*************************************************************************** PLEASE MAKE SURE THE DCNM SERVICE IS SHUTDOWN BEFORE RUNNING THIS SCRIPT!! ***************************************************************************

Please enter the filename to be used for Database Restore:masterbackup.bkp ""

Cisco DCNM Fundamentals Guide, Release 6.x

29-8

OL-25174-02OL-25174-02

Chapter 29

Maintaining the Cisco DCNM-LAN Database Additional References

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
"Database Schema "dcnmuser" will be Restore from filename : masterbackup.bkp" "" Continue y/n [n] : y "Cleaning the database... . . . "Done" pg_restore: connecting to database for restore . . . Restored Database from : masterbackup.bkp Operation Completed C:\Program Files\Cisco Systems\dcm\dcnm\bin>

Additional References
For additional information related to maintaining the DCNM-LAN database, see the following sections:

Related Documents, page 29-9 Standards, page 29-9

Related Documents
Related Topic Automatic purge of event data Automatic purge of statistical data Document Title Chapter 23, Administering Auto-Synchronization with Devices Chapter 25, Administering Statistical Data Collection

Standards
Standards Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

Feature History for DCNM-LAN Database Maintenance

Table 29-1 lists the release history for this feature.
Table 29-1 Feature History for DCNM-LAN Database Maintenance

Feature Name Database maintenance scripts

Releases 5.0(2)

Feature Information No change from Release 4.2(3).

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

29-9

Chapter 29 Feature History for DCNM-LAN Database Maintenance

Maintaining the Cisco DCNM-LAN Database

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

29-10

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

C H A P T E R

30

Troubleshooting DCNM-LAN
This chapter describes how to troubleshoot common issues you might experience while using Cisco Data Center Network Manager for LAN (DCNM-LAN).

Note

For troubleshooting DCNM-LAN server installation issues, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. This chapter includes the following sections:

Tips for Using DCNM-LAN, page 30-1 Trouble with Starting the DCNM-LAN Server, page 30-2 Trouble with the DCNM-LAN Database, page 30-3 Trouble with the DCNM-LAN Client, page 30-5 Trouble with Device Discovery or Device Status, page 30-11 Trouble with Device Management, page 30-12 Trouble with Topology, page 30-12 Trouble with Device OS Management, page 30-13 Trouble with Event Browsing, page 30-13

Tips for Using DCNM-LAN

This section includes the following topics:

Events Tabs Show Fewer Events than the Event Browser, page 30-1 Event Browser Pie Chart May Be Inaccurate for Small Numbers, page 30-2

Events Tabs Show Fewer Events than the Event Browser

The Event Browser feature shows all messages received by DCNM-LAN, even if the message pertains to a feature that is not supported by DCNM-LAN. An Events tab shows only those messages that reflect the status of the currently selected feature. For some features, this is a subset of the possible messages about the feature.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

30-1

Chapter 30

Troubleshooting DCNM-LAN Trouble with Starting the DCNM-LAN Server

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Event Browser Pie Chart May Be Inaccurate for Small Numbers

The Event Browser pie chart may sometimes show incorrect sizes for wedges that are less than 5 percent of the pie; however, the numbers shown are correct.

Trouble with Starting the DCNM-LAN Server

This section includes the following topics:

DCNM-LAN Server Fails to Start, page 30-2

DCNM-LAN Server Fails to Start

Check Table 30-1 for symptoms related to downloading the DCNM-LAN client. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-1 DCNM-LAN Server Fails to Start

Symptom DCNM-LAN server fails to start.

Possible Cause The Postgres database did not install.

Solution For troubleshooting DCNM-LAN server installation issues, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. Start the Postgres service:

The Postgres service is not running.

In Microsoft Windows Server, choose Start > All Programs > Postgres 8.2 > Start Service. In RHEL, use the following command: /DCNM/db/bin/DB start Correct the Postgres user credentials. For more information, see the Updating DCNM-LAN Database Name and Username in pgAdmin III section on page 30-3. Start the DCNM-LAN server. For more information, see the Starting DCNM-LAN Servers section on page 28-2. Check the server log for messages such as Port port-number already in use. The server log is the following file: Installation_directory\jboss-4.2.2.GA\server\dcnm\ log\server.log

The Postgres user credentials are incorrect.

1.

2.

The ports used by the server are already in use.

1.

2. 3.

Determine which application is using the port and stop or reconfigure the application. Restart the DCNM-LAN server.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

30-2

Chapter 30

Troubleshooting DCNM-LAN Trouble with the DCNM-LAN Database

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Trouble with the DCNM-LAN Database

This section includes the following topics:

Trouble with a PostgreSQL Database, page 30-3 Trouble with an Oracle Database, page 30-4

Note

If the DCNM-LAN database fails or communication to the DCNM-LAN database fails, you must stop the DCNM-LAN server or shut down the cluster of DCNM-LAN servers before addressing the problem. Always verify that the DCNM-LAN database and the communication to the DCNM-LAN database are functioning properly before restarting the DCNM-LAN server or cluster of DCNM-LAN servers.

Trouble with a PostgreSQL Database

Check Table 30-2 for symptoms related to the pgAdmin III application for administering a postgreSQL database used with DCNM-LAN. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-2 pgAdmin III Errors

Symptom Error message states that the DCNM-LAN database does not exist. Error message states that password authentication failed for the DCNM-LAN database username.

Possible Cause The DCNM-LAN database name might have changed during an upgrade or reinstallation of the DCNM-LAN server software. The DCNM-LAN database username may have changed during an upgrade or reinstallation of the DCNM-LAN server software.

Solution In the pgAdmin III application, perform the steps in the Updating DCNM-LAN Database Name and Username in pgAdmin III section on page 30-3.

Updating DCNM-LAN Database Name and Username in pgAdmin III

You can update the DCNM-LAN database and username in pgAdmin III.
Step 1 Step 2

Open the pgAdmin III application. In the Object Browser pane, under Servers, click PostgreSQL Database Server 8.2. In the right-hand pane, the Properties tab appears with several other tabs. On the Properties tab, double-click Maintenance database. A dialog box displays a Properties tab for the server. If you need to change the database name, click the Maintenance DB field and type the correct DCNM-LAN database name.

Step 3

Step 4

Note

The database name should be the name that you specified when you most recently upgraded or reinstalled the DCNM-LAN server software.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

30-3

Chapter 30 Trouble with the DCNM-LAN Database

Troubleshooting DCNM-LAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Step 5

If you need to change the database username, click the Username field and type the correct DCNM-LAN database username.

Note

The database username should be the database username that you specified when you most recently upgraded or reinstalled the DCNM-LAN server software.

Step 6 Step 7

Click OK. In the Object Browser pane, double-click PostgreSQL Database Server 8.2. If you changed the username in Step 5, the Connect to Server dialog box appears. If necessary, enter the password for the username that you specified in Step 5 and click OK. The pgAdmin III application connects to the DCNM-LAN database and displays the databases and login roles. If you need additional assistance, see the Help menu in the pgAdmin III application or see the pgAdmin web site at the following URL: http://pgadmin.org/docs/1.6/index.html

Step 8

Trouble with an Oracle Database

If the DCNM-LAN server has trouble using an Oracle database, it logs the error messages in the following file: Installation_directory\jboss-4.2.2.GA\server\dcnm\log\server.log Check Table 30-3 for symptoms related to using an Oracle database with DCNM-LAN. For each error message, see the possible cause and follow the corresponding solution.

Cisco DCNM Fundamentals Guide, Release 6.x

30-4

OL-25174-02OL-25174-02

Chapter 30

Troubleshooting DCNM-LAN Trouble with the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 30-3 DCNM-LAN server.log File Errors with an Oracle Database

Symptom The following error appears in the server.log file:

java.sql.SQLException: ORA-01653: unable to extend table Cisco DCNMUSER.DCMRAWEVENTTABLE by 1024 in tablespace SYSTEM

Possible Cause The tablespace SYSTEM is too small.

Solution
1.

Stop the DCNM-LAN server. See Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers. Increase the SYSTEM table space. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. Start the DCNM-LAN server. See Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers. Stop the DCNM-LAN server. See Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers. Increase the number of sessions and processes to 150 each. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. Start the DCNM-LAN server. See Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers. Stop the DCNM-LAN server. See Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers. Increase the number of open cursors to 1000. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. Start the DCNM-LAN server. See Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers.

2.

3.

The following error appears in the server.log file:

The number of available [org.hibernate.util.JDBCExceptionReporter] Could sessions and processes is inadequate. not create connection; - nested throwable:
(java.sql.SQLException: Listener refused the connection with the following error: ORA-12519, TNS:no appropriate service handler found

1.

2.

3.

The following error appears in the server.log file:

2009-04-08 15:53:47,125 ERROR [org.hibernate.util.JDBCExceptionReporter] ORA-00604: error occurred at recursive SQL level 1 ORA-01000: maximum open cursors exceeded

The number of open cursors is inadequate.

1.

2.

3.

Trouble with the DCNM-LAN Client

This section includes the following topics:

Cannot Download the DCNM-LAN Client from the Server, page 30-6 Cannot Install the DCNM-LAN Client, page 30-6 Cannot Start the DCNM-LAN Client, page 30-7 Cannot Log into the DCNM-LAN Client, page 30-8 Client Loses Connection to the DCNM-LAN Server, page 30-10

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

30-5

Chapter 30 Trouble with the DCNM-LAN Client

Troubleshooting DCNM-LAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cannot Download the DCNM-LAN Client from the Server

Check Table 30-4 for symptoms related to downloading the DCNM-LAN client. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-4 Cannot Download the DCNM-LAN Client from the Server

Symptom Cannot download the DCNM-LAN client from the server.

Possible Cause You are using the wrong URL or web server port. The TCP port is blocked by a gateway device. You are using an unsupported web browser.

Solution Verify that you are using the correct URL, including the port number. Open the TCP port in your firewall. For information about ports used by DCNM-LAN, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. Use a supported web browser. For more information about supported web browsers, see the Cisco DCNM Release Notes, Release 5.x.

Cannot Install the DCNM-LAN Client

Check Table 30-4 for symptoms related to installing the DCNM-LAN client. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-5 Cannot Install the DCNM-LAN Client

Symptom Installer attempts to install Java version 1.6.0_21 but fails.

Possible Cause The system does not have Internet access.

Solution The DCNM-LAN client installer requires Internet access to download the Java version 1.6.0_21 JRE. If the system cannot access the Internet, use another system to download the Java installer, copy it to the system that you want to install the DCNM-LAN client on, install Java, and restart the DCNM-LAN client installation. You can download Java version 1.6.0_21 JRE from the Oracle Technology Network website.

Your network environment requires the If your network environment requires a proxy connection use of a proxy connection to access the to permit the download of the Java installer, ensure that the Internet. proxy settings are configured in Internet Options, available from the Control Panel.

Cisco DCNM Fundamentals Guide, Release 6.x

30-6

OL-25174-02OL-25174-02

Chapter 30

Troubleshooting DCNM-LAN Trouble with the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cannot Start the DCNM-LAN Client

Check Table 30-6 for symptoms related to starting the DCNM-LAN client. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-6 Cannot Start the DCNM-LAN Client

Symptom Cannot start the DCNM-LAN client.

Possible Cause The client installation may be corrupted. The wrong version of Java may be installed.

Solution
1.

Uninstall the DCNM-LAN client. For more information, see the Uninstalling the DCNM-LAN Client section on page 13-8. Download and install the DCNM-LAN client from the DCNM-LAN server. During the client installation, allow DCNM-LAN to install the supported version of Java on the computer. When you download the client from the DCNM-LAN server, if the supported version of Java is not detected on the computer, DCNM-LAN asks you for permission to install the supported version of Java. Your browser may notify you that the Java installer was digitally signed by an expired certificate. To continue, confirm the installation. For more information, see the Downloading and Launching the DCNM-LAN Client section on page 13-3.

2.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

30-7

Chapter 30 Trouble with the DCNM-LAN Client

Troubleshooting DCNM-LAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cannot Log into the DCNM-LAN Client

Check Table 30-7 for symptoms related to logging into the DCNM-LAN client. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.

Cisco DCNM Fundamentals Guide, Release 6.x

30-8

OL-25174-02OL-25174-02

Chapter 30

Troubleshooting DCNM-LAN Trouble with the DCNM-LAN Client

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 30-7 Cannot Log into the DCNM-LAN Client

Symptom

Possible Cause

Solution Ask a DCNM-LAN administrator to reset your password using one of the following scripts:

Cannot log into You forgot your password. the DCNM-LAN client.

For Microsoft Windows, use dcnm_root_directory/dcm/dcnm/bin/pwreset.bat (by default, dcnm_root_directory is c:\Program Files\Cisco Systems\dcm\dcnm\bin). For Linux, use dcnm_root_directory/dcm/dcnm/bin/pwreset.sh (by default, the dcnm_root_directory is /usr/local/cisco).

To reset a password, run the appropriate script for the operating system that you are using, and then enter the user ID to be reset and the password to be used for it. If no one has administrative access to DCNM-LAN, you can reset the local administrator account or change DCNM-LAN server authentication settings by reinstalling the DCNM-LAN server software. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. Authentication servers are not configured to authenticate DCNM-LAN users. If DCNM-LAN is configured to use authentication servers, ensure that every authentication server that you have configured DCNM-LAN to use is configured to accept authentication requests from the DCNM-LAN server. If you have deployed DCNM-LAN in a clustered-server environment, ensure that every authentication server is configured to accept requests from each DCNM-LAN server in the cluster. Restart the DCNM-LAN server. See the Starting a Single DCNM-LAN Server section on page 28-2. Ensure that the computer that runs the DCNM-LAN client meets the network requirements for using the DCNM-LAN client remotely. Any gateway network devices between the DCNM-LAN client and server must allow connections to the DCNM-LAN web server and to the DCNM-LAN server. By default, the DCNM-LAN web server listens to port 8080 and the DCNM-LAN server listens to port 1099; however, you can configure these ports during DCNM-LAN server installation. If you need to change either port, reinstall the server and choose the Full Reinstall option. For information about ports used by DCNM-LAN, see the Cisco DCNM Installation and Licensing Guide, Release 5.x. Do the following:
1. 2.

The DCNM-LAN server is down. The DCNM-LAN server is unreachable.

The DCNM-LAN server IP address changed after you installed the server.

Ensure that the IP address of the DCNM-LAN server is statically assigned. Reinstall the DCNM-LAN server and choose the Full Reinstall option, which allows you to specify the server IP address. See the Cisco DCNM Installation and Licensing Guide, Release 5.x. Log into the DCNM-LAN client and specify the new IP address of the DCNM-LAN server in the DCNM-LAN Server field of the login dialog box.

3.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

30-9

Chapter 30 Trouble with the DCNM-LAN Client

Troubleshooting DCNM-LAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 30-7 Cannot Log into the DCNM-LAN Client (continued)

Symptom

Possible Cause

Solution In the DCNM-LAN client login window, click More and, in the Port field, change the port number that your DCNM-LAN server uses. See the Restarting the DCNM-LAN Client section on page 13-7. If you want to change the port that the DCNM-LAN server listens to, reinstall the DCNM-LAN server and choose the Full Reinstall option, which allows you to specify the DCNM-LAN server port. See the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Cannot log into The wrong DCNM-LAN server the port number was used in the DCNM-LAN login attempt. client (continued).

When you try to log into the DCNM-LAN client, you receive the error message Can not resolve DCNM-LAN server hostname via DNS. Make sure that DCNM-LAN server has a valid DNS entry.

You used a hostname to specify Ensure that DNS on your network has an entry for the DCNM-LAN the DCNM-LAN server during server hostname. the login and DNS does not have an entry for the DCNM-LAN server.

Client Loses Connection to the DCNM-LAN Server

Check Table 30-8 for symptoms related to the DCNM-LAN client losing its connection with the server. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-8 Client Loses Connection to the DCNM-LAN Server

Symptoms

Possible Cause

Solution Restart the DCNM-LAN client. Restart the DCNM-LAN server. See Chapter 28, Starting and Stopping Cisco DCNM-LAN Servers. Investigate your network to determine if it meets the network requirements for using the DCNM-LAN client remotely. For information about ports used by DCNM-LAN, see the Cisco DCNM Installation and Licensing Guide, Release 5.x.

Client loses The client had a failure. connection to the The DCNM-LAN server is down. server. The DCNM-LAN The DCNM-LAN server is client window is unreachable. pink.

Cisco DCNM Fundamentals Guide, Release 6.x

30-10

OL-25174-02OL-25174-02

Chapter 30

Troubleshooting DCNM-LAN Trouble with Device Discovery or Device Status

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Trouble with Device Discovery or Device Status

Check Table 30-9 for symptoms related to issues with device discovery or the device status. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-9 Trouble with Device Discovery or Management

Symptoms

Possible Cause Incorrect device credentials were provided.

Solution Reenter the username and password, and try discovering the device again. If you are attempting to discover CDP neighbors of the seed device, ensure that the credentials that you provide are valid on all devices that you want to discover.

A device discovery task fails. A device status changes to Unmanaged or Unreachable.

The SSH server is disabled on the device.

Reenable the SSH server on the device and try discovering the device again.

The maximum number of SSH sessions Check the number of user sessions on the device. Free at that the device can support has been least one connection and try discovering the device again. reached. CDP is disabled on the device or on the Ensure that CDP is enabled on the device globally and that device interface that the DCNM-LAN it is enabled on the specific interface that the DCNM-LAN server connects to. server connects to. The device interface that the Ensure that the device interface that the DCNM-LAN DCNM-LAN server connects to is shut server connects to is up. down. The device restarted or shut down before discovery could complete. The DCNM-LAN server cannot reach the device. Ensure that the device is running and try discovering the device again. Ensure that the network requirements for device management are met. See the Verifying the Discovery Readiness of a Cisco NX-OS Device section on page 16-8. Use the clear logging logfile command to clear the system log in the device and try to manually discover the device. Use the clear accounting log command to clear the accounting log messages in the device and try to manually discover the device.
Note

Discrepancy in system log messages. Discrepancy in accounting log messages.

When working with a custom VDC, clear the accounting log messages only from the default VDC.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

30-11

Chapter 30 Trouble with Device Management

Troubleshooting DCNM-LAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Trouble with Device Management

Check Table 30-6 for symptoms related to device management. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-10 Trouble with Device Management

Symptom Clearing the log file or the accounting log on a Cisco NX-OS device does not cause DCNM-LAN to rediscover the device automatically.

Possible Cause

Solution

The device did not generate a system Rediscover the device. For more information, see the message about the accounting log or Discovering a Device section on page 17-4. the log file being cleared. This problem is particularly likely if the device is a Cisco MDS 9000 Family Multilayer Switch running Cisco SAN-OS Release 3.1 or earlier releases. You can do either of the following:

The DCNM-LAN The DCNM-LAN server was down. client shows device configuration information that is out of date.

Rediscover the device. For more information, see the Discovering a Device section on page 17-4. Restart the DCNM-LAN server with a clean database. If the server was down for a long time, this action is the recommended solution.
1. 2. 3.

Stopping DCNM-LAN Servers, page 28-5 Cleaning a DCNM-LAN Database, page 29-5 Starting DCNM-LAN Servers, page 28-2

Trouble with Topology

Check Table 30-11 for symptoms related to using the topology feature. For each symptom that describes your problem, determine which possible cause applies and follow the corresponding solution.
Table 30-11 Trouble with Topology

Symptom

Possible Cause

Solution

Links between Cisco MDS 9000 Family Multilayer Switches continue appear after the link has gone down.

Devices are connected by Rediscover the devices that topology incorrectly shows as Gigabit Ethernet or Fast Ethernet linked. ports, and are running Cisco SAN-OS Release 3.1 or earlier releases.

Cisco DCNM Fundamentals Guide, Release 6.x

30-12

OL-25174-02OL-25174-02

Chapter 30

Troubleshooting DCNM-LAN Trouble with Device OS Management

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Trouble with Device OS Management

Check Table 30-12 for symptoms related to the Device OS Management feature. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-12 Trouble with Device OS Management

Symptom

Possible Cause

Solution Use a file server that is on the same LAN as the devices included in the software installation job. If all of the available file servers transfer software image files too slowly, before you create the software installation job, manually copy the files to the devices that you will include the job and configure the job to use the manually copied files rather than a file server. For information about configuring a software installation job, see the System Management Configuration Guide, Cisco DCNM for LAN, Release 5.x.

During a software The connection between the file installation job, the server and the device is slow. software image file transfer between a file server and a device takes too much time.

Trouble with Event Browsing

Check Table 30-13 for symptoms related to event browsing issues. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Table 30-13 Trouble with Event Browsing

Symptom

Possible Cause

Solution

Events available on the device command line do not appear in the DCNM-LAN client. Too few events are shown in Event Browser or an Events tab.

Logging levels on managed devices are Check the logging level configuration on managed devices. set incorrectly. See the Cisco NX-OS System-Message Logging Requirements section on page 16-4. The DCNM-LAN client fetches events Check the events-related setting in the DCNM-LAN client that are not old enough. preferences. For more information, see the Configuring the Maximum Age of Events Fetched from the Server section on page 14-16.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

30-13

Chapter 30 Trouble with Event Browsing

Troubleshooting DCNM-LAN

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table 30-13 Trouble with Event Browsing

Symptom Too many events are shown in Event Browser or on an Events tab.

Possible Cause

Solution

A managed device has an issue that is Temporarily unmanage the device until you resolve the generating many system log messages. issues on the device. For more information, see the Unmanaging a Device section on page 17-5. Logging levels on managed devices are Check the logging level configuration on managed devices. set incorrectly. See the Cisco NX-OS System-Message Logging Requirements section on page 16-4. By design, an Events tab shows only messages that apply to the currently selected feature and may show only a subset of the possible messages for the feature. For more information, see the Events Tabs Show Fewer Events than the Event Browser section on page 30-1. Use the Event Browser to see status-related system messages received by DCNM-LAN. For more information, see the System Management Configuration Guide, Cisco DCNM for LAN, Release 5.x.

A feature Events tab does not show events that appear in the Event Browser.

Cisco DCNM Fundamentals Guide, Release 6.x

30-14

OL-25174-02OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

P A R T

Appendices

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

A P P E N D I X

Launching Fabric Manager in Cisco SAN-OS Releases Prior to 3.2(1)

This appendix provides instructions for launching Fabric Manager Client in Cisco SAN-OS releases prior to 3.2(1). This Appendix contains the following sections:

Setting the Seed Switch in Cisco SAN-OS Releases 3.1(1) to 3.2(1), page A-1 Setting the Seed Switch in Releases Prior to Cisco SAN-OS Release 3.1(1), page A-2

Setting the Seed Switch in Cisco SAN-OS Releases 3.1(1) to 3.2(1)

Note

As of Cisco SAN-OS Release 3.1(1), the Fabric Manager login procedure changed. If you are running a version of Cisco SAN-OS that is earlier than Cisco SAN-OS 3.1(1), follow the login instructions in the Setting the Seed Switch in Releases Prior to Cisco SAN-OS Release 3.1(1) section on page A-2. From Cisco SAN-OS Release 3.1(1) to Release 3.2(1), you must log in to Fabric Manager Server before you discover or open fabrics, and these fabrics can have different user credentials. You can specify different SNMP communities per switch on the Web Server.

Note

The default user name is admin and the default password is password for your initial login. This information is stored in the database. Both the Fabric Manager Server and the Web Server share the same user credential database. To log in to Fabric Manager Server and to open a fabric, follow these steps:

Step 1

Double-click the Fabric Manager Client icon on your workstation. You see the Fabric Manager Server Login dialog box. Set FM Server to the IP address where you installed Fabric Manager Server, or set it to localhost if you installed Fabric Manager Server on your local workstation. If you forget your password, you can run one of the following scripts:

Step 2

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

A-1

Appendix A Setting the Seed Switch in Releases Prior to Cisco SAN-OS Release 3.1(1)

Launching Fabric Manager in Cisco SAN-OS Releases Prior to 3.2(1)

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
bin\webUserAdd.bat admin password adds a user name and password to the Fabric Manager

Server database.
bin\DBReset.bat resets the database back to the initial state and removes any discovered

fabrics. Both of these scripts are available as UNIX .sh files.

Step 3 Step 4 Step 5

Enter the Fabric Manager Server user name and password. Check the Use SNMP Proxy check box if you want Fabric Manager Client to communicate with Fabric Manager Server through a TCP-based proxy server. Click Login. After you successfully log in to Fabric Manager Server, you can set the seed switch and open the fabrics that you are entitled to access. You see the Discover New Fabric dialog box. Set the fabric seed switch to the Cisco MDS 9000 Family switch that you want Fabric Manager to use. Enter the user name and password for the switch. Choose the Auth-Privacy option MD5-DES (default) when you log in.

Step 6 Step 7 Step 8

Note

The Accelerate Discovery check box should remain checked for normal operation. Uncheck this only if you have changed switch IP addresses. You may experience problems with SAN IDs in Fabric Manager if you uncheck this check box.

Step 9

Click Discover. You see the Open Fabric dialog box. Check the check box(es) next to the fabric(s) you want to open in the Select column, or click the Discover button to add a new fabric.

Step 10

Note

As of Cisco SAN-OS Release 3.1(1) and later, opening multiple fabrics is a licensed feature. You will get a message if any of the fabrics discovered does not have a license.

Note

As of Cisco SAN-OS Release 3.1(2b), a license can be a permanent license, an evaluation license, or there are no licenses (all evaluation licenses have expired).

Step 11

Click Open to open the fabric.

Setting the Seed Switch in Releases Prior to Cisco SAN-OS Release 3.1(1)
Note

As of Cisco SAN-OS Release 3.1(1), the Fabric Manager login procedure changed. If you are running Cisco SAN-OS Releases 3.1(1) to 3.2(1), then follow the login instructions in the Setting the Seed Switch in Cisco SAN-OS Releases 3.1(1) to 3.2(1) section on page A-1.

Cisco DCNM Fundamentals Guide, Release 6.x

A-2

OL-25174-02

Appendix A

Launching Fabric Manager in Cisco SAN-OS Releases Prior to 3.2(1) Setting the Seed Switch in Releases Prior to Cisco SAN-OS Release 3.1(1)

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
When you run Fabric Manager, you must select a switch for Fabric Manager to use to discover the fabric. For releases earlier than Cisco SAN-OS Release 3.1(1), use the same user name and password on each of the multiple fabrics that you open, then log in directly to the MDS 9000 Family switch that you want Fabric Manager to use. To set the seed switch if you are running a version of Cisco SAN-OS that is earlier than Cisco SAN-OS Release 3.1(1), follow these steps:
Step 1

Double-click the Fabric Manager Client icon on your workstation. You see the Fabric Manager Login dialog box. Click the Options button if necessary to expand the optional settings in this dialog box. Set FM Server to the IP address where you installed Fabric Manager Server, or set it to localhost if you installed Fabric Manager Server on your local workstation. Set the fabric seed switch to the MDS 9000 Family switch that you want Fabric Manager to use. Enter the user name and password for the switch. Check the Use SNMP Proxy check box if you want Fabric Manager Client to communicate with Fabric Manager Server through a TCP-based proxy server.

Step 2 Step 3 Step 4 Step 5 Step 6

Note

The Accelerate Discovery check box should remain checked for normal operation. Uncheck this only if you have changed switch IP addresses. You may experience problems with out of sync SAN IDs in Fabric Manager if you uncheck this check box.

Step 7

Click Open to open the fabric.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

A-3

Appendix A Setting the Seed Switch in Releases Prior to Cisco SAN-OS Release 3.1(1)

Launching Fabric Manager in Cisco SAN-OS Releases Prior to 3.2(1)

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

A-4

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

A P P E N D I X

Cisco DCNM Unsupported Feature List

This appendix contains a list of features and functions not supported by Cisco DCNM or Device Manager. This list is organized according to the chapter in which the feature would be described if it were supported. (See Table B-1.)
Table B-1 Features Not Supported by Cisco DCNM or Device Manager

Part 2 Cisco MDS NX-OS Installation and Switch Management

Chapter/Category

Procedure Moving Licences Between Switches

Obtaining and Installing Licenses Backing Up License Files Initial Configuration Starting a Switch (Initial Setup) Configuring Console Settings Configuring COM1 and Modem Settings Adjusting for Daylight Savings Time Configuring the Initialization String Basic Switch Configuration Terminal Settings File System Commands Displaying File Contents Software Images Manual Upgrade on a Dual Supervisor Switch Corrupted Bootflash Recovery

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

B-1

Appendix B

Cisco DCNM Unsupported Feature List

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table B-1 Features Not Supported by Cisco DCNM or Device Manager (continued)

Part

Chapter/Category

Procedure Compressing and Uncompressing Files Displaying the Last Lines in a File Executing Commands Specified in a Script Setting the Delay Time Displaying Configuration Files Unlocking the Startup Configuration File Accessing Remote File Systems

Working with Configuration Files Formatting External CompactFlash

Configuring High Availability Managing System Hardware Managing Modules

Copying Images to the Standby Supervisor Clock Modules Connecting to a Module Preserving Module Configuration Purging Module Configuration EPLD Configuration Configuring SSI Boot Image Managing SSMs

3 Switch Configuration

Configuring Interfaces Scheduling Tasks

Displaying the ALPA Cache Contents Clearing the ALPA Cache Schedule Configuration Inter-VSAN Routing (IVR) FICON Support IVR Service Groups Displaying and Clearing ARP Caches Tuning Configuration IPS Module Core Dumps Remote SPAN

4 Fabric Configuration 6 IP Services

Inter-VSAN Routing Configuration Configuring FCIP Configuring the SAN Extension Tuner Configuring IP Storage

8 Network and Switch Monitoring

Monitoring Network Traffic Using SPAN

Cisco DCNM Fundamentals Guide, Release 6.x

B-2

OL-25174-02

Appendix B

Cisco DCNM Unsupported Feature List

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table B-1 Features Not Supported by Cisco DCNM or Device Manager (continued)

Part 10 Troubleshooting

Chapter/Category Troubleshooting Your Fabric

Procedure Loop Monitoring Configuring CIM CFS for FC Timers Local Text Based Capture Capturing FC Analyzer Frames Locally Sending Captured FC Analyzer Frames to a Remote IP Address Clearing Configured FC Analyzer Information Displaying a List of Hosts Configured for Remote Capture Using Fabric Analyzer Display Filters

Monitoring System Processes and Saving the Last Core to Flash Logs Kernel Core Dumps System Health Initiation Loopback Test Configuration Frequency Hardware Failure Action Tests for a Specified Module Clearing Previous Error Reports Online Health Management System

Enabling and Disabling the OHMS Enabling and Disabling Hardware Failure Action Configuring Onboard Failure Logging Clearing Previous Error Reports Performing Tests for a Specified Module Configuring Automatic Loopback Tests Performing SERDES Loopback Tests

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

B-3

Appendix B

Cisco DCNM Unsupported Feature List

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

B-4

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

A P P E N D I X

Interface Nonoperational Reason Codes

If the administrative state for an interface is up and the operational state is down, the reason code differs based on the nonoperational reason code as described in Table C-1.
Table C-1 Reason Codes for Nonoperational States

Reason Code Link failure or not connected SFP not present Initializing

Description Physical layer link is not operational. The small form-factor pluggable (SFP) hardware is not plugged in. The physical layer link is operational and the protocol initialization is in progress. Cisco MDS SAN-OS waits for the specified R_A_TOV time before retrying initialization. The interface VSAN is deleted or is in a suspended state. To make the interface operational, assign that port to a configured and active VSAN.

Applicable Modes All

Reconfigure fabric in progress The fabric is currently being reconfigured. Offline Inactive

Hardware failure Error disabled

A hardware failure is detected. Error conditions require administrative attention. Interfaces may be error-disabled for various reasons. For example:

Configuration failure. Incompatible buffer-to-buffer credit configuration.

To make the interface operational, you must first fix the error conditions causing this state; and next, administratively shut down or enable the interface.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

C-1

Appendix C

Interface Nonoperational Reason Codes

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Table C-1 Reason Codes for Nonoperational States (continued)

Reason Code Isolation due to ELP failure Isolation due to ESC failure Isolation due to domain overlap Isolation due to domain ID assignment failure Isolation due to other side E port isolated Isolation due to invalid fabric reconfiguration Isolation due to domain manager disabled Isolation due to zone merge failure Isolation due to VSAN mismatch Nonparticipating

Description Port negotiation failed. Port negotiation failed. The Fibre Channel domains (fcdomain) overlap. The assigned domain ID is not valid. The E port at the other end of the link is isolated. The port is isolated due to fabric reconfiguration. The fcdomain feature is disabled. The zone merge operation failed. The VSANs at both ends of an ISL are different. FL ports cannot participate in loop operations. It may happen if more than one FL port exists in the same loop, in which case all but one FL port in that loop automatically enters nonparticipating mode.

Applicable Modes Only E ports and TE ports

Only FL ports and TL ports

PortChannel administratively down

The interfaces belonging to the PortChannel are down. Only PortChannel interfaces Suspended due to incompatible The interfaces belonging to the PortChannel have speed incompatible speeds. Suspended due to incompatible The interfaces belonging to the PortChannel have mode incompatible modes. Suspended due to incompatible An improper connection is detected. All interfaces in a remote switch WWN PortChannel must be connected to the same pair of switches.

Cisco DCNM Fundamentals Guide, Release 6.x

C-2

OL-25174-02

S e n d

c o m m e n t s

t o

d c n m -d o c f e e d b a c k @c is c o . c o m

A P P E N D I X

Managing Cisco FabricWare

The Cisco FabricWare software running on the MDS 9020 Switch offers Fibre Channel switching services that realize maximum performance. Cisco FabricWare provides networking features such as zoning, advanced security, nondisruptive software upgrades, diagnostics, a CLI with syntax resembling Cisco IOS, and standard interfaces for management applications. This appendix contains the following sections:

Fibre Channel Support, page D-1 Zone Configuration, page D-1 Security, page D-2 Events, page D-2 Managing Cisco FabricWare with DCNM, page D-3

Fibre Channel Support

Cisco FabricWare supports autoconfigured Fibre Channel ports capable of up to 4-Gbps bandwidth. Cisco FabricWare supports the following port types:

E F FL Fx Auto

Cisco FabricWare supports Fabric Shortest Path First (FSPF) as the standard path selection protocol used by Fibre Channel fabrics. The FSPF feature is enabled by default on all Fibre Channel switches. Except in configurations that require special consideration, you do not need to configure any FSPF services. FSPF automatically calculates the best path between any two switches in a fabric.

Zone Configuration
Zoning enables you to set up access control between storage devices or user groups. If you have administrator privileges in your fabric, you can create zones to increase network security and to prevent data loss or corruption. Zoning is enforced by examining the source-destination ID field. Cisco FabricWare does not support QoS, broadcast, LUN, or read-only zones.

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

D-1

Appendix D Security

Managing Cisco FabricWare

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
You can use the DCNM zone configuration tool to manage zone sets, zones, and zone membership for switches running Cisco FabricWare. Cisco FabricWare supports zone membership by pWWN. Refer Cisco MDS 9000 Family Fabric Manager Fabric Configuration Guide.

Security
Cisco FabricWare supports the following security features:

RADIUS SSH User-based roles IP access control lists

Cisco FabricWare can use the RADIUS protocol to communicate with remote AAA servers. RADIUS is a distributed client/server protocol that secures networks against unauthorized access. In the Cisco implementation, RADIUS clients run on Cisco MDS 9000 Family switches and send authentication requests to a central RADIUS server that contains all user authentication and network service access information. You can access the CLI using the console (serial connection), Telnet, or Secure Shell (SSH). For each management path (console or Telnet and SSH), you can configure one or more of the following security control options: local, remote (RADIUS), or none. Using these access methods, you can configure the roles that each authenticated user receives when they access the switch. Cisco FabricWare supports two fixed roles: network administrator and network operator. IP access lists (IP-ACLs) control management traffic over IP by regulating the traffic types that are allowed or denied to the switch. IP-ACLs can only be configured for the mgmt0 port. DCNM Server uses SNMPv1 and SNMPv2 to communicate with Cisco FabricWare.

Events
You can monitor fabric and switch status for Cisco FabricWare switches through either a syslog server or an SNMP trap receiver. The syslog, or system message logging software, saves messages in a log file or directs the messages to other devices. This feature provides you with the following capabilities:

Provides logging information for monitoring and troubleshooting Allows you to select the types of captured logging information Allows you to select the destination server to forward the captured logging information

By default, the switch logs normal but significant system messages to a log file and sends these messages to the system console. You can specify which system messages should be saved based on the type of facility and the severity level. You can access logged system messages using the CLI or by saving them to a properly configured system message logging server. You can configure the Cisco MDS 9020 Switch using the CLI to send notifications to SNMP managers when particular events occur. You can send these notifications as traps.

Cisco DCNM Fundamentals Guide, Release 6.x

D-2

OL-25174-02

Appendix D

Managing Cisco FabricWare Managing Cisco FabricWare with DCNM

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Managing Cisco FabricWare with DCNM

DCNM supports switches running Cisco FabricWare. Table D-1 shows the supported features and where to find more information on that feature.
Table D-1 FabricWare Features in DCNM

Feature Zones

FabricWare Capabilities Zone configuration Zone membership by pWWN No Cisco FabricWare support for QoS, broadcast, LUN, or read-only zones

Guide Refer to the Cisco MDS 9000 Family Fabric Manager Fabric Configuration Guide

Interfaces

1/2/4 Fibre Channel autonegotiating ports Refer to the Cisco MDS 9000 Family DCNM Interfaces Configuration Guide SNMPv1 and SNMPv2c Refer to the Cisco MDS 9000 Family DCNM System Management Configuration Guide Refer to the Cisco MDS 9000 Family DCNM System Management Configuration Guide Refer to the Cisco MDS 9020 Switch Configuration Guide and Command Reference.

SNMP

Software images

Automated upgrades Manual upgrades

FLOGI, name server, FDMI, and RSCN

Displaying FLOGI details Registering name server proxies Displaying FDMI RSCN statistics

Security

Configuring RADIUS Configuring server groups Configuring role-based authorization Configuring user accounts Configuring SSH services

Refer to the Cisco MDS 9000 Family DCNM Security Configuration Guide.

Fibre Channel routing FSPF global configuration FSPF interface configuration IP services IP access control lists on mgmt0

Refer to the Cisco MDS 9020 Switch Configuration Guide and Command Reference. Refer to the Cisco MDS 9000 Family DCNM Security Configuration Guide. Refer to the Cisco MDS 9000 Family DCNM Fundamentals Configuration Guide. Refer to the Cisco MDS 9000 Family Fabric Manager Fabric Configuration Guide

System messages

System message logging configuration

Advanced configuration

FC timer

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

D-3

Appendix D Managing Cisco FabricWare with DCNM

Managing Cisco FabricWare

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

Cisco DCNM Fundamentals Guide, Release 6.x

D-4

OL-25174-02

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m

INDEX

A
AAA server Admin tab description aliases switching between global device aliases and fcaliases 3-10 using with FDCNM-SAN ALPA caches clearing ARP caches clearing displaying
B-2 B-2 B-2 B-2 3-10 2-36 2-56 11-14

recovering from corruption space requirements

10-6

B-1

buffer-to-buffer credits. See BB_credits bundleMisCfg tooltip

11-14

adminDown tooltip

C
CAs DCNM-SAN Web Services channelAdminDown tooltip
2-11 11-14 11-14

channelConfigurationInProgress tooltip channelOperSuspended tooltip CIM configuring

B-3 11-14

displaying contents

Cisco DCNM Enterprise LAN License adding a device to a license Cisco DCNM-LAN client
21-5, 23-5 18-3 18-3

Auto-Synchronization with Devices DCNM-LAN deleting events data description

23-1 14-16, 23-4 23-6

removing a device from a license downloading Java

13-2 13-2 13-2 13-3 13-8 13-8 13-3 13-2

poller interval

installation prerequisites licensed features operating systems

23-3 23-4

purging data automatically purging data now

23-8

starting and stopping a poller synchronizing with a device

password, default

reinstalling the client uninstalling the client Cisco DCNM-LAN server

B
BB_credits reason codes bootflash: file system
10-4 C-1 11-14

adding a device to a license starting stopping

28-2 28-5

18-3 18-3

removing a device from a license

bitErrRTThresExceeded tooltip

Cisco DCNM license See Cisco DCNM Enterprise LAN License

Cisco DCNM Fundamentals Guide, Release 6.x

OL-25174-02

IN-1

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
Cisco MDS SAN-OS software images Cisco NX-OS DCNM-LAN logging requirements Cisco Traffic Analyzer configuring with Performance Manager CLI accessing firewall clock modules managing
B-2 D-2 4-2 9-9 16-4 10-1

D
D_S_TOV errors when setting database DCNM-LAN backing up cleaning guidelines maintenance restoring database files resolving lock errors daylight saving time
22-1 22-4 2-36 29-7 29-4 29-5 29-3 29-1 11-7

Cluster Administration DCNM-LAN description viewing data COM1 ports configuring configuring command scripts executing CompactFlash slot0:
10-4 B-2 B-1

adjusting for DCNM-SAN authentication

B-1

4-1 to ?? 11-22

corrupted jar file errors detachable tables downgrading error recovery FAQs FCIP
11-1 11-19 11-4 11-7 5-19

command schedulers
B-2

installation failures ISL statistics

9-5

11-6, 11-7

configuration files displaying connectivity troubleshooting tool console settings configuring core dumps IPS modules core files saving to CompactFlash custom reports creating a template Custom tab description
2-30 2-31 B-3 B-2 B-1 5-33 B-2

launching troubleshooting login failure recovery

11-6

11-3

missing Information pane network discovery

5-30

11-9 11-22

mixed software environments problems with map changes running with multiple NICs setting preferences upgrade failures description
4-1 4-3 5-28 11-6

11-8 11-20

shows as disabled service

11-4

DCNM-SAN authentication discovery best practices Web Server support

4-4

Cisco DCNM Fundamentals Guide, Release 6.x

IN-2

OL-25174-02

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DCNM-SAN Clients advanced mode description filtering
5-1 5-15 5-2

exporting performance data launching navigating printing TCP ports

5-18 2-7 2-10

2-11

displaying physical attributes

5-15

2-11 2-11 2-11 11-14

Information pane main menu status bar

5-8

using with SSL Device Discovery DCNM-LAN description

deniedDueToPortBinding tooltip
5-28

setting preferences
5-24

toolbar icons (table) troubleshooting tools wizards

5-32

5-12 5-33

16-1 16-10 16-11

discovering a device rediscovering a device discovering a device

2-38

DCNM-SAN Server authentication

4-2 3-6

rediscovering a device Device Groups DCNM-LAN

11-10

2-40

continuously monitoring fabrics database failed to start description

3-1 3-1

adding devices to a group creating a device group description

3-2 21-1 4-3

21-4 21-2

disk space requirements fabric discovery features installing

3-1

removing a device from a group in topology Device Manager

11-20 19-18

21-5

installation overview
3-3

local host error messages modifying settings passwords

3-9 3-8

color definitions context menus description

2-36 2-36 6-1

6-6 6-8

performing administrative tasks performing configuration tasks properties files Solaris support user names viewing logs
3-9 2-51 3-1 3-6 3-1

disk images not visible downgrading FAQs icons

11-1 6-5 11-4

11-7

Red Hat Linux support

3-1

installation failures label definitions managing ports PortChannels preferences

2-50 6-10 6-6

11-6, 11-7

login failure recovery

6-8 6-8

11-6

Windows support authentication

4-4

DCNM-SAN Web Server DCNM-SAN Web Services configuring communities configuring users description
2-5 2-55

setting preferences tabs

6-6 6-8

6-10

trunking

upgrade failures

11-4

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

IN-3

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
using interface (figure) viewing port status
6-6 6-8 6-3

elpFailureClassFParamErr tooltip elpFailureClassNParamErr tooltip

11-14 11-14 11-15

viewing supervisor modules viewing switch modules devices discovery

8-2 6-8

elpFailureInvalidFlowCTLParam tooltip elpFailureInvalidPayloadSize tooltip elpFailureInvalidPortName tooltip elpFailureInvalidTxBBCredit tooltip

5-31 11-15

11-15

11-15

modifying groupings (procedure) Devices and Credentials DCNM-LAN adding a device deleting a device description
17-1 17-4 17-5 17-3

elpFailureIsolation tooltip

11-15 11-15 11-15

elpFailureLoopbackDetected tooltip elpFailureRevMismatch tooltip

17-6 11-15

elpFailureRatovEdtovMismatch tooltip ELP failures reason codes EPLD images configuring E ports isolation
i-lxiv 11-14 C-2 11-15 11-15 B-2 11-15 C-2

configuring default credentials

17-5

elpFailureUnknownFlowCTLCode tooltip

11-15

discovering a device unmanaging a device DirectX installing documentation additional publications domain IDs duplicates causing errors failures
C-2 11-6

ePortProhibited tooltip

eppFailure tooltip error messages

domainAddrAssignFailureIsolation tooltip
11-13

errorDisabled tooltip gen error messages error reports

11-7

domainInvalidRCFReceived tooltip domainManagerDisabled tooltip domainMaxReTxFailure tooltip domainOverlapIsolation tooltip domains overlap isolations DPVM wizard
5-33 C-2

11-14

clearing previous ESC failures

B-3 11-15

11-14 11-14 11-14

escFailureIsolation tooltip reason codes Ethernet interfaces

C-2

domainOtherSideEportIsolation tooltip
11-14

viewing performance information events displaying using DCNM-SAN

8-2

2-23

displaying using DCNM-SAN Web Services displaying using Device Manager

2-6 8-2

8-2

drill down reports description

events and syslogs Events Browser DCNM-LAN

2-52

E
E_D_TOV errors when setting
11-7

configuring maximum event age Events tab DCNM-LAN

14-16

Cisco DCNM Fundamentals Guide, Release 6.x

IN-4

OL-25174-02

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
configuring maximum event age exporting Performance Manager reports as CSV external CompactFlash formatting
B-2 9-11 14-16

device grouping support FCIP restrictions

11-19

5-31

exchange link parameter failures. See ELP failures

fcipPortAdminCfgChange tooltip fcipPortMaxReTx tooltip

11-15

11-15 11-15

fcipPortKeepAliveTimerExpire tooltip fcipPortPersistTimerExpire tooltip

11-16

F
fabric editing monitoring Fabric Analyzer using display filters
B-3 11-15 11-15 11-15 11-15 2-38

fcipPortSrcAdminDown tooltip fcipPortSrcLinkDown tooltip fcipSrcPortRemoved tooltip FCoE wizard

5-32 11-16 11-16

11-16 11-16 11-16

fcipSrcModuleNotOnline tooltip

11-16

fabricBindingDBMismatch tooltip fabricBindingDomainInvalid tooltip

fcotChksumErr tooltip fcotNotPresent tooltip

fabricBindingNoRspFromPeer tooltip fabricBindingSWWNNotFound tooltip Fabric Manager Clients Fabric pane FabricPath fabrics discovery monitoring FabricWare DCNM-SAN support (table) events roles
D-2 D-1 D-3 5-30 3-6 19-9 5-19 5-7

fcotVendorNotSupported tooltip fcspAuthenfailure tooltip fctimers configuring CFS

B-3 11-16

11-16

using interface (figure)

Fibre Channel analyzers capturing frames locally

B-3 B-3 B-3

clearing configured information FICON DCNM-SAN Client support ficonBeingEnabled tooltip ficonNoPortnumber tooltip ficonNotEnabled tooltip ficonVsanDown tooltip
D-2 D-2 D-2 D-1 11-16 11-16 5-2

sending frames to remote IP addresses

Fibre Channel support

D-2

11-16 11-16

security

FICP wizard files compressing

B-2 B-1 B-2 5-33

SNMP traps syslog traps FAQs DCNM-SAN fcaliases

zoning support

displaying contents
11-1 11-1

displaying last lines uncompressing filtering

3-10 B-2

Device Manager

using with DCNM-SAN FC-GS-3 requests

end port groups switch groups

5-23 5-23

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

IN-5

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
firstPortNotUp tooltip flows performance statistics FL ports nonparticipating codes FSPF flow statistics
7-3 to ?? D-1 C-2 7-1 2-22 11-16 11-16

HTTP proxy servers configuring hwFailure tooltip

11-21 11-16

firstPortUpAsEport tooltip

viewing performance information

I
icons Device Manager images See kickstart images; software images; system images images. See kickstart images; software images; system images incomAdminRxBBCreditPerBuf tooltip
11-16 6-5

frequently asked questions. See FAQs

path selection protocol

G
Generation 2 switching modules installing in Generation 1 chassis Gigabit Ethernet interfaces viewing performance information Global preferences DCNM-LAN events preference overview
14-15 14-17 14-16 14-16 2-23 10-14

incompatibleAdminMode tooltip

11-16 11-16 11-16

incompatibleAdminRxBBCredit tooltip incompatibleAdminRxBufferSize tooltip incompatibleadminSpeed tooltip initialization string configuring initializing tooltip install all command failure cases installation DCNM-LAN prerequisites
13-2 11-16 10-4 B-1 11-16 11-16

monitoring preference

preprovisioning preference

interfaceRemoved tooltip

H
hardware failures configuring actions Health tab description high availability software upgrades historical data preserving hosts performance statistics Host Tracking
2-76 7-1 11-19 10-2 2-14 B-3

interfaces nonoperational reason codes reason codes

C-1 11-16 C-1

invalidAttachment tooltip invalidConfig tooltip inventories managing Inventory tab description IP-ACLs wizard
Cisco DCNM Fundamentals Guide, Release 6.x

11-16 11-16

invalidFabricBindExh tooltip
8-4

viewing ISL information

2-24

2-27

5-33

IN-6

OL-25174-02

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
See also IPv4-ACLs; IPv6-ACLs IPFC errors caused by configuration IPS modules core dumps IPv4-ACLs FabricWare support iSCSI DCNM-SAN Client support wizard ISLs performance statistics statistics
9-5 2-27 7-1 5-33 5-2 D-2 B-2 11-8

configuring kickstart images description

B-3

10-4 10-1 10-5

KICKSTART variable Konqueror

selecting for supervisor modules configuring for Java Web Start

11-5

L
LDAP license See Cisco DCNM Enterprise LAN License licenses backing up files
B-1 B-1 11-9 2-21 2-56

viewing detailed inventory information viewing performance information IVR DCNM-SAN Client support FICON support service groups wizard
5-32 B-2 B-2 5-2

moving between switches unsupported features wizard

5-33 B-1

One-Click License Install failed

linkFailCreditLossB2B tooltip linkFailCreditLoss tooltip

11-17

11-16 11-17 11-17

J
Java execution failures
11-6 11-7

linkFailDebounceTimeout tooltip linkFailLinkReset tooltip linkFailLIPF8Rcvd tooltip linkFailLIPRcvdB2B tooltip linkFailLossOfSignal tooltip linkFailLossOfSync tooltip
11-3 11-4 11-17 11-17 11-17 11-17 11-17 11-17

linkFailLineCardPortShutdown tooltip

java.lang.ArrayIndexOutOfBoundsException errorArrayIndexOutOfBoundsException error Java Web Start checking installation not detected
11-4 11-5

linkFailLRRcvdB2B tooltip linkFailNOSRcvd tooltip linkFailOLSRcvd tooltip

hangs on the download dialog running from command line setting up on *.jnlp files JNLP verifying settings
11-3 11-5

11-17 11-17 11-17 11-17

linkFailOPNyRETB2B tooltip linkFailOPNyTMOB2B tooltip linkFailPortInitFail tooltip linkFailPortUnusable tooltip linkFailRxQOverFlow tooltip linkFailTooManyINTR tooltip link failures reason codes
C-1

11-17 11-17 11-17 11-17

K
kernel core dumps

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

IN-7

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
linkFailure tooltip logins failure recovery logs increasing log window size viewing information
2-51 8-4 11-10 11-6 11-17

default preferences

5-29 11-13 11-13

freezing the layout look green squares with mode highlighting

5-21 5-19 11-14 11-13

icon descriptions light gray squares module warnings no squares

11-14

viewing using Device Manager loopbackDiagFailure tooltip loopbackIsolation tooltip loopback tests configuring frequency loops monitoring
B-3 B-3 11-17 11-17

orange crosses

11-14 11-14

orange squares with mode purging down elements red crosses red squares
11-14

5-22

red line through switches

11-14 5-22

11-13

M
management role-based map preferences Automatically Save Layout default Detach Overview Window default Display End Device Labels default Display End Devices default Expand Loops default
5-29 5-29 5-29 5-29 5-29 5-29 5-29 5-29 5-29 5-32

refreshing saving

5-22 11-13

shows two switches when only one tab descriptions viewing large Visio diagrams fan failuresmaps power supply failures
11-13 5-21

upgrade software without losing map settings

5-21 5-22

11-19

maps module failuresmaps

Display Unselected VSAN Members default Expand Multiple Links default

McAfee Internet Suite 6.0 Professional DCNM-SAN installation failures messages selecting severity level modems configuring settings module configurations preserving purging modules
B-2 B-2 B-1 2-54 11-7 11-7

Layout New Devices Automatically default Override Preferences for Non-default Layout default 5-29 Select Switch or Link from Table default

Device Manager installation failures

Open New Device Manager Each Time default

5-29

Use Quick Layout when Switch has >=30 End Devices default 5-29 maps black squares brown squares
11-14 11-14 11-24

clearing license orange X clearing topologies color definitions

11-22 11-13

connecting to replacing module tests configuring

B-2

10-14

B-3

Cisco DCNM Fundamentals Guide, Release 6.x

IN-8

OL-25174-02

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
monitoring stopping and starting DCNM-LAN Mozilla configuring for Java Web Start multiple fabrics managing
8-4 11-24 11-5 14-12 14-12

conditions for sending removing forwards NPV wizard

5-33

2-63

2-54

O
offline tooltip
11-17

N
network administrator roles FabricWare Network Analysis DCNM-LAN PONG
26-2 D-2

OHMS configuring
B-3 11-17

ohmsExtLBTest tooltip Opera

Online Health Management System. See OHMS configuring for Java Web Start other tooltip
8-2 8-3 11-17 11-5

network monitoring device discovery network operator roles FabricWare Network Servers DCNM-LAN binding adapters to a server clearing default credentials clearing unique credentials
20-10 20-4 20-6 20-4 20-5 D-2

mapping topologies

P
parentDown tooltip passwords assigning using DCNM-SAN pcAnyWhere replacing with DirectX stopping
11-6 11-18 11-18 11-6 5-32 11-17

peerFCIPPortClosedConnection tooltip peerFCIPPortResetConnection tooltip performance configuring collections

20-9 2-59

configuring default credentials configuring unique credentials correlating servers description NICs
20-1 20-6

correlating servers and adapters

customizing reports data

7-4 7-2

2-30

unbinding an adapter from a server

20-10

event triggers graphs

11-21 11-21 9-7

manually specifying for DCNM-SAN Client manually specifying for DCNM-SAN Server manually specifying for Device Manager nondisruptive upgrades methods notifications
10-2 11-17

historical monitoring

9-2 9-7 9-5

host-optimized port groups ISL statistics (procedure) real-time monitoring summary reports tables
9-7 9-7 9-1

11-21

nonParticipating tooltip

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

IN-9

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
using thresholds Performance Manager authentication
4-4 7-4 7-2

incompatible speeds wizard

5-33

C-2

portFabricBindFailure tooltip portGracefulShutdown tooltip port groups

9-9 7-4

11-18 11-18

configuring data collection configuring flows creating a flow data collection

9-2 9-2

configuring with Traffic Analyzer creating collections

7-2 7-2 9-11

host-optimized performance Port Mapper Port Mapping ports

2-29 2-29

9-7

data interpolation exporting as CSV reports

9-6

disabling using Device Manager enabling using Device Manager Port Security
11-6

6-8 6-8

shows as disabled service using thresholds viewing reports

7-2 3-5

wizard preferences

5-33 11-18

portVsanMismatchIsolation tooltip Confirm Deletion default

9-6 5-28

verifying collections
9-6

wizard for configuring exporting as XML generating top 10 viewing events viewing graphs
9-7 9-7 9-11 9-8

DCNM-SAN Clients default

5-28 6-10

5-28

Performance Manager reports

Device Manager

Export Tables with Format default Show CFS Warnings default Show Device Name by default
9-7 5-29 5-28

5-28

viewing host-optimized port group performance viewing summary reports viewing tables Performance tab description polling periods changing
3-9 2-16 9-7 9-7

Show End Device Using default

5-28 5-28 5-28 5-28

Show Shortened iSCSI Names default Show Timestamps as Date/Time default Telnet Path default
5-28

Show WorldWideName (WWN) Vendor default Use Secure Shell instead of Telnet default
5-28

PONG, See Network Analysis portBindFailure tooltip portBlocked tooltip PortChannels configuring using Device Manager creation dialog box too small down states
C-2 C-2 C-2 11-8 6-8 11-18 11-18 11-18

Q
QoS wizard
5-33

portChannelMembersDown tooltip

R
RADIUS FabricWare support
D-2

incompatible modes

incompatible remote switch

Cisco DCNM Fundamentals Guide, Release 6.x

IN-10

OL-25174-02

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
rcfInProgres tooltip reason codes description (table) Red Hat Linux DCNM-SAN Server related documents remote AAA server delayed authentication remote file systems accessing remote SPAN configuring
B-2 B-2 4-2 i-lxiv 2-56 3-1 C-1 11-18

Enable Audible Alert when Event Received default 5-29 Retry request 1 time(s) after 5 sec timeout default 5-29 Trace SNMP packets in Log default SNMPv1 FabricWare support SNMPv2 FabricWare support software images default settings
10-8 10-5 D-2 D-2 5-29

Remote AAA Server

selecting for supervisor modules space requirements upgrade prerequisites

5-32 10-7 10-6 to ?? 10-1

role-based management controlling access roles privileges RRD configuring database RSPAN configuring
B-2 2-61 5-32 2-56

upgrading SAN-OS images variables disruptive mechanisms Solaris DCNM-SAN SSH FabricWare support
D-2 3-1 11-18 10-1

software upgrades
10-2 10-2

removing web services roles

srcPortNotBound tooltip

S
SAN extension tuner configuring
B-2

SSI boot images configuring SSL certificates using with DCNM-SAN Web Services SSMs managing boot alert
27-3 27-1 B-2 2-11 B-2

SAN operating system. See Cisco MDS SAN-OS schedulers. See command schedulers Server Log Settings DCNM-LAN configuring the default logging level description services modules replacing SFPs not present reason codes SNMP preferences
C-1 10-14

standby supervisor modules

10-14 10-13

boot variable version copying image to

B-2

managing bootflash: startup configuration files unlocking

B-2

10-13

Statistical Data Collection DCNM-LAN

Cisco DCNM Fundamentals Guide, Release 6.x OL-25174-02

IN-11

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
deleting a collection
25-5 25-5 25-6

replacing syslog

10-14 6-8

deleting data from a collection description

25-1 25-6

viewing using Device Manager viewing information

2-15 2-14

deleting data from the statistics database purging data automatically purging data now Statistics tab Statistics tab DCNM-LAN stopping and starting monitoring storage devices performance statistics summary reports description
2-6 7-1 14-12 14-12 25-3 25-8

viewing with Events tab syslogs

2-52

system health initiating system images description

10-4 10-5 B-3

stopping and starting data collection

selecting for supervisor modules SYSTEM variable system messages viewing using Device Manager viewing with Events tab
10-13 2-14 10-1

8-4

Supervisor-1 modules migrating from Supervisor-2 modules (note) selecting software images Supervisor-2 modules Generation 1 chassis select software images supervisor modules managing standby bootflash: replacing
10-12, 10-14 10-14 10-13 10-13 10-13 to ?? 10-14 10-13 to ?? 10-5

T
tables filtering navigating templates creating for custom reports terminals configuring settings thresholds baselines for performance time delays setting topologies clearing maps mapping Topology
8-3 11-22 B-2 11-18 7-3 B-1 2-31 2-10 2-10 2-11

migrating from Supervisor-1 modules

10-5

searching for information

migrating to Supervisor-2 modules standby boot alert

standby supervisor boot variable version upgrading a dual supervisor switch viewing using Device Manager suspendedByMode tooltip suspendedBySpeed tooltip suspendedByWWN tooltip swFailure tooltip switches starting up Switch Groups
B-1 B-1 11-18 11-18 11-18 11-18 6-8 B-1

tooManyInvalidFLOGIs tooltip

accessing DCNM-SAN accessing Fabric Path accessing other features collapsing a device group

19-24 19-25 19-23 19-18

upgrading with dual supervisors

2-64

switching modules
Cisco DCNM Fundamentals Guide, Release 6.x

IN-12

OL-25174-02

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
copy running-config to startup-config creating a device group deleting a device group description
19-1 19-18 19-22 19-19 19-22 19-21

launching DCNM-SAN Web Services UNIX issues parent menus disappear too many open files error upgradeInProgress tooltip
11-12 11-12

2-7

expanding a device group exporting as JPG image hiding device groups hiding network servers layouts legend
19-5 19-10 19-15, 19-16 19-28 19-18

web browser cannot find web server

11-18

11-12

19-17

upgrades. See disruptive upgrades; nondisruptive upgrades; software upgrades upgrading switches
B-1

loading layouts managing a vPC moving devices opening the map

User-based roles FabricWare support

19-19 D-2

moving a device between device groups

19-14 19-9

users DCNM-LAN adding a local user

15-6 15-7

removing a device from a device group showing device groups showing network servers using viewing tools views
19-2 19-29 19-12 19-18 19-17 19-10

19-20

changing a local user password deleting a local user description roles

15-2 15-1 15-8

understanding icons and links

V
virtual server
8-4 2-76

vPC configuration inconsistency topology map mapping multiple fabrics topology maps custom
8-3 8-3 8-3 11-18 2-44

Visio diagrams saving maps as VMware

2-76 2-43 2-43 5-22

description enclosures

vPC Inconsistencies vPC inconsistency vPC Utilization vsanInactive tooltip VSANs flow statistics
6-8 2-44

tovMismatch tooltip Traffic Distribution troubleshooting

11-18 11-18

vsanMismatchIsolation tooltip
5-33 7-3 C-2

DCNM-SAN tools trunking

configuring using Device Manager trunkNotFullyActive tooltip

11-18

mismatches wizard
5-32

U
UNIX

W
Windows
Cisco DCNM Fundamentals Guide, Release 6.x

OL-25174-02

IN-13

Index

Se n d c o m m e n t s t o d c n m - d o c f e e d b a ck @ c i s c o . c o m
DCNM-SANServer Windows issues blue screen
11-11 11-11 11-11 3-1

DCNM-SAN window content disappears icons disappear from desktop SCP/SFTP failures Windows XP hangs wizards DPVM Wizard FCIP Wizard FCoE Wizard IP ACL Wizard iSCSI Wizard IVR Zone Wizard NPV Wizard
5-33 5-33 5-33 5-33 5-33 5-32 5-33 5-33 5-32 5-33 11-11 11-10 11-11 11-11

Device Manager window content disappears printing causes an application crash text fields are too small

11-11

License Install Wizard PortChannel Wizard Port Security Wizard QoS Wizard VSAN Wizard WWNs suspended connection
5-33

Software Install Wizard

5-32

5-33

Zone Edit Tool Wizard

5-32

C-2

Z
zoneMergeFailureIsolation tooltip zoneRemoteNoRespIsolation tooltip zones displayed as bold wizard zoning FabricWare support
D-1 5-32 11-9 5-33 11-18 11-18

troubleshooting tools

Cisco DCNM Fundamentals Guide, Release 6.x

IN-14

OL-25174-02