Migrating from Brocade ECFM to Brocade DCFM
Contents
1. Cancel Help Figure 11 Configure Names dialog box NOTE If you have nicknames that are greater than 128 characters in length they are truncated at 128 characters during data migration PosT DEPLOYMENT CONFIGURATION Discovery of Environment First display the Discovery dialog box by choosing Discovery gt Setup You can also use the Setup icon on the main toolbar The RBAC Discovery permission controls access to displaying this dialog box and all its functions If you want to know if a switch has been discovered or not use the switch s Properties dialog box Missing Switches If a fabric has been discovered and some of its switches segment out into single or multiple new fabrics you can now easily rediscover those new fabrics in the Discover Setup window without entering their credentials Migrating from Brocade ECFM to Brocade DCFM 19 of 22 FROM THE SOLUTIONS CENTER Solution Guide a Discover Setup Add an IP Acdress to Discover Discovered Addresses Name Ip Address Discovery Status Communty String User ID H amp test H ze MixedF E5100_142004 10 09 00 05 1E 41 69 8 EDU 14208 10 03 00 60 69 90 10 62 10 32 142 10 E4100_142010 10 03 00 05 1E 34 02 4F 10 372 142 12 Figure 12 Discover Setup window Validation Testing The main way to ensure that data has been migrated from Brocade EFCM to DCFM correctly is to look at the data in DCFM For example check the following types of data e Zones2. The DCFM remote client application will run on Microsoft Windows 2000 or on Microsoft Windows 2003 or on Microsoft Windows XP Professional Service Pack 2 or later If the patches have been applied click the following button to begin the installation process You will receive a Java Security warning requesting permission to download and start the installer program and to read and write files on your system You must grant these permissions to allow installation of the DCFM client application Migrating from Brocade ECFM to Brocade DCFM 18 of 22 FROM THE SOLUTIONS CENTER Solution Guide Importing Names To import names previously nicknames in EFCM choose Configure gt Names to display the Configure Names dialog box shown in Figure 11 Click Import to display the Import Files dialog box browse to the location of the CSV file and follow onscreen instructions Configure Names Display All Names v Scope Name v v Name WAN Operational Status Type Description hba_node_nickname 20000000C969C833 Discovered FCHBA 200e _A00000051 E022FD6 Discovered FCSwitch Dee H OK_D6 _100008008849E200 Discovered FCSwitch Principal Switch wheat_the_heck 2001 080088E38D93 Discovered FCPort EFCM_DCFM_Migration _100008008849E200 Discovered Fabric FC Fabric j10k_port_7_nickname 200708008849E200 Discovered FCPort hba_port_nickname _A0000000C969C839 _ Discovered FCPort ER RE Detached WWAN Name
3. FROM THE SOLUTIONS CENTER Solution Guide Migrating from Brocade Enterprise Fabric Connectivity Manager to Brocade Data Center Fabric Manager Brocade Data Center Fabric Manager DCFM simplifies infrastructure management with the performance and scalability required in the Brocade Data Center Fabric which connects applications to infrastructure in the majority of the world s data centers BROCADE FROM THE SOLUTIONS CENTER Solution Guide CONTENTS ites ii ee ee eee ee 3 Supported Firmware ANNER 3 Vlugt e gil gis 6 kone mentee arene eee nen er career E ee eee 4 VIS elle RE 4 nl 5 WTS Lee dee E ha OMG sesiciss c45cncitstceseseiaccecescscsusetesncscesusenectscsusetesntsec E 5 TAE DISCOVOIV SWIC E 5 Deployment Best Practices for Public Private Networks AANEREN 6 open REENEN 6 Bee Ee e 8 Hyprd Management Eege 9 PEM a Ne NEW E ee E E be ssusaoauntenstanesesseace 10 EOE a cad aeeisteteied ocece ee etesttet cad eaas eendeteee cetetece ete ees tater es atereeeesssencaanausnecaaccanenaccesventeseenieee 10 PIG IVES TEA AAN AN AA AAA AAN A A EE A A A AT 11 Tnird Pary Management i OGUClS EE 11 Integration ES BE E 12 Northbound notification SNMP Syslog forwarding ENEE 13 TODOIO OV IW e 14 CMTE WOT ACS tee 14 WOONONA OU E 14 E o E O EE E E A E E E AE eebe 15 slauon and Dep oyme sss ete ceentseer Nr iiter tre te et oeren art eer errr ter ec ee rrr eek eer ee cee eee ener eae 16 HVS ea TANS US ue EI E 16 POV WIN COIE E 18 APOTE N E
4. e Topology displays that you ve customized see also Topology Maps section earlier in this document e Role Based Access Control RBAC data e User list e Names see also Names section earlier in this document e ROV TOV setting TROUBLESHOOTING 1 Click the Technical Support Information tab 2 Inthe text field specify the path to save the DCFM server technical support information to 3 Click Capture to gather all the information and then click Close Migrating from Brocade ECFM to Brocade DCFM 20 of 22 FROM THE SOLUTIONS CENTER Solution Guide APPENDIX A BROCADE FABRIC MANAGEMENT PRODUCT FAMILY This information is available in several other documents but as a convenience it is added here too Brocade DCFM manages both FOS fabrics and mixed FOS M EOS fabrics with product specific element managers and enhanced group management functions The DCFM architecture integrates the best management features of EFCM and Fabric Manager it is based on the EFCM Graphical User Interface GUI and Fabric Manager messaging and data management design for improved performance and scalability Brocade DCFM Professional Brocade DCFM Enterprise Enhanced Group Manager Brocade DCFM is available as two different products DCFM Professional and DCFM Enterprise Brocade DCFM Professional is targeted at customers seeking a less extensive management solution for smaller SANs This software is included with Brocade switches and al
5. reporting workflow etc Brocade DCFM Professional Brocade DCFM Enterprise Enhanced Group Manager FOS Element Managers HBA Element Managers M EOS Element Managers 2009 Brocade Communications Systems Inc All Rights Reserved 01 09 GA SG 118 01 Brocade Fabric OS File Lifecycle Manager MyView and StoragexX are registered trademarks and the Brocade B wing symbol DCFM DCX and SAN Health are trademarks of Brocade Communications Systems Inc in the United States and or in other countries All other brands products or service names are or may be trademarks or service marks of and are used to identify products or services of their respective owners Notice This document is for informational purposes only and does not set forth any warranty expressed or implied concerning any equipment equipment feature or service offered or to be offered by Brocade Brocade reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use This informational document describes features that may not be currently available Contact a Brocade sales office for information on feature and product availability Export of technical data contained in this document may require an export license from the United States government Migrating from Brocade ECFM to Brocade DCFM 22 of 22
6. a a E 19 Post Deployment Configuration se eennnn1nnennnnnnnennnnnnnonnnnnneennnnnnneonnnnnnnennnnnnnennnnnnnnennnnnnnennnnnnennnnnnnnnnnennnnnnnnennnnnnnennnnnnnnennnn nenene nnnennnnnnnnenennnnnennnn nnne nnn nnnen ennn neene 19 Discovery e E KT e ien EE 19 Ve 19 NV UNC eA NO EAR 20 tee 20 Appendix A Brocade Fabric Management Product Family sssssssssssssnssssssssesnssesnssnsonenssnssnsoesnssnecesenesesnesneonenssnssneoeeneonensoneonensonsoneoesnsensonensones 21 Appendix B Integration with Partner Management Framewoth csssssssssssssssssssesnsssssssnesessesnesnsaeesesneanesseaeesesnsaneateneaneateneaneassneaneneeneaneneenesnenses 22 Migrating from Brocade ECFM to Brocade DCFM 2 of 22 FROM THE SOLUTIONS CENTER Solution Guide INTRODUCTION Brocade DCFM is a management application that provides easy centralized management of the Storage Area Network SAN as well as quick access to all product configuration applications Using this application you can configure manage and monitor your networks with ease In order to introduce higher scalability and performance Brocade DCFM was designed to perform discovery through a single Fabric OS FOS director or switch whereas Brocade Enterprise Fabric Connectivity Manager EFCM discovered all directors directly over an Ethernet connection In an existing Storage Area Network SAN comprised of legacy McDATA directors a Brocade discovery switch must be introduced
7. and then a client will be allowed to establish a telnet session through the DCFM server to a given managed FC device e The HTTP proxy provides a mechanism to use Brocade Web Tools from stations on the company intranet other than the DCFM server No proxy agents exist on the DCFM server for SSH SCP SNMP FTP or Syslog Migrating from Brocade ECFM to Brocade DCFM 8 of 22 FROM THE SOLUTIONS CENTER Solution Guide While it may still be possible to use some level of scripts Perl Expect and so on to make changes on the managed devices it can be much more complex in the private management network configuration mostly due to the inability to have clients outside the private network communicate directly with the managed devices It is likely that the only way to do it securely would be to run the scripts on the DCFM server or add another connection to the private network from a server that runs the scripts to make changes on the managed devices Hybrid Management Network In rare cases hybrid management networks that is private management network topology and open network management topology are both implemented with the same server as shown in Figure 3 In most cases these configurations started as private management networks and later managed devices not close enough to be included in the private management network were added and were therefore brought under management in an open management network configuration Some data centers may decide
8. any backbone director or switch attached to the network Protecting the FC devices with strong passwords is especially important in this configuration In addition access restrictions can be set at either the managed SAN device backbone director switch or in the managed Ethernet switch to which the SAN device s management port s are connected Restrictions can be set by IP address IP ports or both Doing so reduces the security concerns of running an open management network Attaching SAN devices to a company intranet could expose them to other security threats including attempts to gain access denial of service attacks and others As previously explained the risks of running in an open management network can be greatly reduced by creating access restrictions Migrating from Brocade ECFM to Brocade DCFM T of 22 FROM THE SOLUTIONS CENTER Solution Guide Private Management Network In a private management network Brocade DCFM is attached to both the company intranet with one Ethernet connection and a private network to which managed devices are also be attached DCFM client connections are accepted on the Ethernet connection attached to the company intranet and all management traffic between DCFM and the devices are on the private network as shown in Figure 2 Intranet DCFM client DCFM connections server H Sen Ki b Ba 3 oO Figure 2 Private management network configuration The private managem
9. behaves like any autonomous per fabric Zone Library vr Zoning Zoning Scope 10 00 00 05 1E 46 50 00 e Zone DB Global Zone Library Zone DB Operation Zone DB Edit Zone DB Active Zone Config abric Zone DB Switch MA lobal Zone Library Offline Repository Wed Aug 06 17 09 35 PDT 2008 Potential Members Type WAN oneLibrary Offline Repository Wed Aug 06 17 09 35 PDT 2006 Figure 5 Zoning window showing the Zone database menu Nicknames Called Nicknames in Brocade EFCM you can use Names in DCFM as a way of providing simple user friendly names for products and ports During migration nicknames are converted to names and are exported to a CSV file Once you have logged into DCFM you can import this file Note that the user configurable setting for whether or not to use unique or non unique names is also migrated NOTE If you have nicknames that are greater than 128 characters in length they are truncated at 128 characters during data migration Although it is unlikely that truncating names will cause problems if you know you have very long nicknames you might want to make them 128 characters or less in EFCM before the migration Third Party Management Products Many customers use a combination of Brocade EFCM and third party Storage Resource Management SRM products to manage their storage and fabric infrastructure The most commonly used SRM products include e EMC ControlCenter ECC e IBM TotalStorage
10. fabric is during a Zone Set Activation operation In Brocade DCFM the Zone DB menu shown in Figure 5 is equivalent to the Zone Library menu in EFCM and can display up to three items immediately following a migration e Fabric Zone DB This function is implemented to access the defined and effective offline zone configurations stored in the fabric when a FOS switch is present NOTE Because switches in an M EOS fabric cannot contain more than one zone configuration EFCM has no equivalent capability Legacy EFCM users can disregard the Fabric Zone DB data e Zone Library This library reflects zoning information contained in the autonomous EFCM per fabric zoning libraries If you were not using per fabric libraries prior to migration that is using the global library instead then this selection will not contain any data Migrating from Brocade ECFM to Brocade DCFM 10 of 22 FROM THE SOLUTIONS CENTER Solution Guide e Global Zone Library This library reflects zoning information contained in the common EFCM global zoning library If you were not using the global zoning library prior to migration that is using per fabric libraries instead then this selection will not contain any data DCFM Operational Difference The DCFM Global Zone Library is NOT as common a library as it was in EFCM During migration the EFCM Global Zone Library is simply replicated into a per fabric Zone Library for each fabric Therefore a DCFM Global Zone Library
11. later e Version M EOSn 9 6 x or later NOTE Although you do not have to install or know the Java version used because it is bundled with both versions of Brocade DCFM development was conducted using Java JDK 1 6 Migrating from Brocade ECFM to Brocade DCFM 3 of 22 FROM THE SOLUTIONS CENTER Solution Guide Migration Facts There is no charge for Brocade EFCM license conversion to Brocade DCFM Enterprise EFCM customers with valid software licenses are entitled to upgrade to a DFCM Enterprise license at no additional charge Customers upgrading to DCFM Enterprise are required to purchase a service agreement with a minimum one year term You can upgrade to Brocade DCFM if you currently have the EFCM Enterprise Base EFCM Enterprise Advanced Module EFCM Standard 9 6 or 9 7 to DCFM Enterprise Data from your Brocade EFCM will be migrated to DCFM Enterprise Brocade DCFM Enterprise supports a mixed M EOS and FOS fabric On pure M EOS fabrics consult your sales representative to help you decide the right solution for your environment MIGRATION OVERVIEW The migration is described in detail in the Brocade DCFM Migration and Transition Guide For your convenience this section lists high level steps required for the migration in a Windows environment including Review the pre flight checklist making sure that o You have the DCFM license key on the Key Certificate and serial number from the DVD jewel case o Aversion of
12. prior to upgrading from EFCM to DCFM see the Planning section In addition to reading this document for further details about how to install configure and deploy Brocade DCFM ensure that you have access to current product documentation e Brocade Data Center Fabric Manager Enterprise User Manual e Brocade Data Center Fabric Manager Migration and Transition Guide provides installation instructions migration instructions from both Brocade EFCM and Brocade Fabric Manager and information about the differences between EFCM and Fabric Manager interfaces and the Brocade DCFM interface e Brocade Data Center Fabric Manager Enterprise Release Notes And other Brocade papers e Brocade DCFM Features Brief e Brocade DCFM Data Sheet NOTE Although there are two editions of Brocade DCFM unless otherwise noted this document refers to Brocade DCFM Enterprise Brocade DCFM Professional is another version of the application with a subset of capabilities This document is for Brocade customers who are currently using Brocade Enterprise Fabric Connectivity Manager EFCM and want to find out more about migrating to Brocade DCFM It is not intended as a definitive technical reference on Brocade DCFM but it provides guidelines for field engineers or IT personnel at customer sites Supported Firmware FOS e Version 5 0 0 or later for FOS only fabrics e Version 6 0 0 for Native Interoperability NI fabrics M EOS e Version M EOSc 9 6 x or
13. CFM interface as the two are almost identical The key difference between the two interfaces is that the Event Management and Security tabs are in different places e You can access Event Policies available through Monitor gt Event Policies e Security Center is available only through the M Series Element Managers One change on the toolbar is that the Export function is no longer available as that functionality has been moved to individual dialog boxes bS View All DCFM 10 0 1 SAN Edit view Discover Configure Monitor Tools Help 2S Ei BWA O Demir nme v Nme v v Search o View Ai Name 7500_a All Levels 2 E 750a E amp switch Group sw7500_92 sw7500_93 A BZ Corporate 4 eg Clariion E g Host Group 20 00 00 1B 32 01 5 gt oc b i EI Ki Routed Products Group S amp virtual Group EI KZ Switch Group G ocx3_a1 D partition0 E AZ Corporate B EI KZ Switch Group P 1E 03 08 00 88 37 39 i pcx3_a3 Devic 4 sw7500_92 sw7500_93 Corporate A Clariion loc_hps_1 DCK3_A1 partitiond Corporate B DCKS_AS _ Swit a j aw F d M S l D I Ba Dall Ba D asterLog Filter _ Only events for current view Page of1 gt Hp Legend a F Minimap a Level Source Name Source Address Type Description LL Edge6064 10 66 23 140 Security Event Switch IP Access Control List Violation on 10 66 23 14 S gt 80to100 G Edge6064 10 656 23 140 Secur
14. EFCM is installed on your server that meets migration requirements o The fabric is using the required version of M EOS o The EFCM data is fully backed up on your current management servers NOTE Ensure that all instances of the EFCM client are closed on the management server and on remote workstations Insert the Brocade DCFM installation DVD into the drive on a Windows management server and follow onscreen directions Migrate data from your Brocade EFCM application This could take up to 30 minutes Specify the following settings and apply them could take up to 30 minutes o Configure the IP server o Configure server Syslog Web server SNMP and starting ports o Configure the fabric size small medium or large o Select the FTP server Start the DCFM server and client Once all the DCFM services are started you can log in You can use your user ID and password from EFCM Migrating from Brocade ECFM to Brocade DCFM A of 22 FROM THE SOLUTIONS CENTER Solution Guide PLANNING As with all technology upgrades in the data center planning is a critical part of the process When you are migrating from one software application to another you need to find out as much as you can about the new application and how it differs from the application you are currently using that is Brocade EFCM Then decide when is the right time to upgrade and start putting a task list task owners and a timeline in place Migration Considerations
15. ENTER Solution Guide INSTALLATION AND DEPLOYMENT Installing the Remote Client With EFCM there were two methods to install the client application 1 Install the client using the application CD 2 Download and install the client from the EFCM server s Web site The DCFM client is now a Web start application launched from the DCFM server type the IP address of the DCFM server in the browser window NOTE If SSL was selected during the installation you will need to use HTTPS to access the DCFM Web site shown in Figure 9 O O A BD E Ah i adress L https 166 70 134 252 M Eco Ae Google G 166 70 134 252 sw Goal Pr amp E 166 70 134 252 1500167410 5 Downloading application Download SNMP MIB Name DCFM 10 These MIB files are provi d Publisher Data Center Fabric Manager Enterprise data base of a ny SNM Pvi From https 166 70 134 252 ENTITY RFC2737 mib Estimated time remaining 4 seconds COO FICON v5 0 mib connected to a Brocade switch Figure 9 The DCFM Web site Migrating from Brocade ECFM to Brocade DCFM 16 of 22 FROM THE SOLUTIONS CENTER Solution Guide You can change the SSL and port settings after the installation by going to SAN gt Options gt Server Port as shown in Figure 10 In EFCM these settings were under Server Connections ey Options Category This option allows you to configure server port settings Backup Enable SSL EN Display End Node Dis
16. PPENDIX B INTEGRATION WITH PARTNER MANAGEMENT FRAMEWORKS This information is available in several other documents but as a convenience it is added here too Brocade DCFM is designed with open standards interfaces to simplify integration with management frameworks supplied by server storage and infrastructure management partners The DCFM open standards architecture has the following characteristics e Simplifies partner integration using open standard interfaces SNMP SMI S Improves customer management of virtualized resources server fabric storage Reduces management complexity of virtualized data centers Improves administrator productivity so that human resources scale efficiently with the growth of storage and virtual server workloads DCFM provides integrated data path management for server networks multi protocol data center fabrics and heterogeneous storage environments Its open interfaces simplify partner management integration anticipating the evolution of infrastructure management from physical switch management to policy based service management essential for cost effective scalable management of virtual data centers To ensure that all of this works together seamlessly we have architected the appropriate integration hooks into the code right from the beginning Integration with Brocade products via servel storage frameworks SMI SNMP Web Services etc OS installation updates LUN management chargebacks
17. Productivity Center TPC e HP Storage Essentials SE e Hitachi Storage Services Manager e NetApp Onaro SANscreen e Symantec CommandCentral Storage CCS Customers leverage these SRM products primarily for LUN level activities for example LUN provisioning LUN masking mapping reporting chargebacks and performance characterization They are also used in conjunction with EFCM to manage storage provisioning for applications via the connected network fabric configuring the fabric ports for appropriate protocol speed zoning configuring QoS parameters collecting performance statistics monitoring for error conditions and so on EFCM is used to support both proprietary API interfaces ECC API for EMC ECC SWAPI for other SRM products and standards based SMI S interfaces to enable these SRM products to discover and manage SAN elements With DCFM the proprietary APIs are not being carried forward since they reached End of Life EOL a while ago in favor of the standards based SMI S approach Therefore customers migrating from EFCM to DCFM will have to ensure that they use SMI S for any fabric and switch related activities that they Migrating from Brocade ECFM to Brocade DCFM 11 of 22 FROM THE SOLUTIONS CENTER Solution Guide want managed through these SRM products All of Brocade s key partners have already migrated their SRM products to SMI S and therefore this shouldn t pose any issues NOTE For more details on best practices r
18. S access control mechanisms Provider logging of exceptions operations and performance metrics for diagnostic purposes Secure SAN fabrics Secure RPC communication CIM queries using WBEM Query Language WQL Northbound notification SNMP Syslog forwarding SNMP Trap Forwarding You can configure the application to send SNMP traps to other computers To correctly configure trap forwarding you must configure the target computer s IP address and SNMP ports Syslog Forwarding Syslog messages are available only on B Series platforms Syslog forwarding is the process by which you can configure the management application to send Syslog messages to other computers Switches send the Syslog information only through port 514 therefore if port 514 is being used by another application you must configure the management application to listen on a different port Then you must configure another Syslog server to listen for Syslog messages and forward the messages to the management application Syslog listening port Syslog messages are persisted in the database You can view the Syslog messages from the management application However the management application does not convert the Syslog messages into event objects except for the audit Syslog messages Migrating from Brocade ECFM to Brocade DCFM 13 of 22 FROM THE SOLUTIONS CENTER Solution Guide Topology Maps Client Interface Users of EFCM will be very familiar and comfortable with the D
19. There are several things to consider when you are making the decision to migrate to Brocade DCFM Note the following e Export to database MySQL and DB2 not supported the EFCM flat file structure is replaced by a Sybase database in DCFM Third party integration API support SMI S is the third party integration management interface for DCFM e Event Management Rules DCFM has different Event Management capabilities see the product documentation for details e Manager of Managers MoM Master subordinate instances are not supported e Group by function in Views All views are migrated but any views customized by a Group by revert to their default grouping The Performance Data and Master log is not migrated from EFCM to DCFM The Discovery Switch A switch which is called a discovery switch when it is used in this context must be a B Series device running Fabric OS FOS The discovery switch is a switch in the fabric that uses in band communication to get fabric wide information about the Name Server Zoning and fabric membership There must be at least one discovery switch configured in pure Fabric OS fabrics and present and configured in mixed fabrics The presence of a discovery switch provides significant help in improving the scalability of the application NOTE In the Brocade DCFM interface the discovery switch may be called the seed switch The following devices can be configured as a discovery swi
20. can use a Brocade 5000 Switch but Brocade DCX Backbone or 48000 Director is recommended e Large fabrics You can use a Brocade 5000 Switch but Brocade DCX Backbone or 48000 Director is recommended Using FOS 6 2 or later you can take advantage of the Virtual Fabrics feature in Fabric OS to partition a switch and use the resulting Logical Switches as discovery switches for multiple M EOS fabrics Doing so allows you to manage them using a single FOS discovery switch for all of them something that was not available prior to version 6 2 Deployment Best Practices for Public Private Networks They are many different ways that a DCFM server can be deployed Some configurations are restrictive and provide greater levels of security Other configurations are more flexible and may make it easier to deal with change Planning the LAN connectivity for DCFM will help to ensure that your deployment matches the needs of your environment Open Management Network For the purpose of this document an Open Management Network is one where the DCFM server is attached to the company intranet with a single Ethernet attachment as shown in Figure 1 The devices to be managed by DCFM are also attached directly to the company intranet via Ethernet Typically the server and the devices are in the same location and likely on the same subnet but devices could be remote as well Migrating from Brocade ECFM to Brocade DCFM 6 of 22 FROM THE SOLUTIONS CENTER Solution Gu
21. egarding deployment of SMI S providers for various Scenarios public private networks FOS and M EOS intermixed fabrics in IM2 and IM3 modes and so on refer to either the OEM best practices Table 1 Compatibility between SRM products and SMI S for FOS and M EOS SRM Product SRM Product Version SMI for FOS Version SMI for M EOS Version EMC ControlCenter ECC 120 7 2 25 IBM TotalStorage Productivity Center TPC 6 0 9 NetApp Onaro SANscreen TO COME TO COME TO COME Symantec Command Central 5 0 120 7 2 2 2 2 Storage e fal IMPORTANT Information provided in the table above is current as of the writing of this document Integration APIs SMI SWAPI Storage Management Initiative SMI is a broad based initiative sponsored by the Storage Networking Industry Association SNIA that is standardizing all aspects of storage management for multivendor storage networking products SMI encompasses the storage aspects of the Common Information Model CIM from the Distributed Management Task Force DMTF CIM provides a common definition of management information for systems networks applications and services and allows for vendor extensions CIM s common definitions enable vendors to exchange semantically rich management information between systems throughout the network The Brocade SMI Agent SMI A is a proxy agent to multiple fabrics it resides on a separate host When it is deployed the SMI A does not require any modifica
22. ent network was a common configuration with Brocade EFCM in the past Many customers used an Ethernet hub which was included as part of a rack system into which the FC switches or directors were installed in While it is still possible to run DCFM with a private management network on a hub you can achieve better performance between the DCFM server and the managed devices using a minimum of one dedicated fast Ethernet switch 100 MB full duplex device A private Virtual LAN VLAN on a larger network switch would provide the most robust solution A private management network provides the benefit of having the DCFM server act as a firewall between the company intranet and the managed FC switches Denial of service attacks and attempts to log in could largely be performed only against the DCFM server itself and not against the managed devices Access to the DCFM server should be protected in the same way that other critical servers in the data center are to prevent unauthorized access While the private management network provides a configuration that can prevent access other than the DCFM server to managed devices note that there are proxy agents on the DCFM server that will allow limited access to the managed devices through other protocols A telnet and HTTP proxy both exist in the DCFM server e M EOS only The telnet proxy requires that you log in to the proxy first with the login password combination you would use to log in to the DCFM server
23. hat do not display as expected For example views in EFCM can be grouped by many different fields labels such as location enclosure vendor and so on However in DCFM views can be grouped only by fabric ka Create view Mame Corporate View Description Corporate Fabrics Only Members Include Assets via C All m Selection Available Fabrics Selected Fabrics Total Products 2 Total Products H Cancel Help Figure 7 Create Views dialog box Instructions to create customized views can be found in the View Management section of the Brocade DCFM Enterprise User s Manual One of the most common uses of views was to group all of the HBAs together for a single server A better way to achieve this grouping is to use the Server Port Mapping feature which performs the same function Right click an HBA to initiate the HBA Server Mapping dialog box shown in Figure 8 Ka HBA Server Mapping Create servers and assign HBAS HB 4 Servers E Be Serveri 10 00 00 00 COD EZE 2 10 00 00 00 CO GBEZEG 2 SS 30 00 0016 32 01 59 168 Corporate A 20 00 00 1632 01 59 oc br i Corporaie A 20 01 00 1 B 32 21 59 Cancel Help Figure 8 HBA Server Mapping dialog box NOTE In EFCM ports from multiple fabrics could participate in a group whereas in DCFM only ports from a single fabric can participate in a group Migrating from Brocade ECFM to Brocade DCFM 15 of 22 FROM THE SOLUTIONS C
24. ide Server DCFM client P d Ee e 7 DCFM Intranet vs WF a Ki Figure 1 Open management network configuration There are several advantages to an open management network Configuring DCFM and the devices is straightforward as there is little concern for IP routes or the DCFM server having multiple Network Interface Cards NICs Furthermore a SAN administrator who wishes to use Web Tools Telnet SSH or other management protocols outside Brocade DCFM can easily do so from any client station with access to the intranet that the SAN devices are attached to Another benefit of an open management network is that the devices can be configured to send asynchronous messages to a server other than the DCFM server For example SNMP or SYSLOG could be configured on each of the managed devices to send messages to a server other than the DCFM server which would receive and process those messages accordingly One of the most important benefits of an open management network is the ability to have a server that runs scripts that utilize SSH Perl Expect or other scripting protocols to communicate with and make changes on the Fibre Channel FC devices under management There are some caveats however to using an open management network Probably the most critical is the other viewpoint of one of the strengths of this configuration that is that any device on the customer intranet can use any of the available protocols to access
25. ity Event BAS Wrong User Name Password Combination on 1 E 40to80 LL Administrator 10 66 22 62 User Action Corporate B successfully set to Fabric 14to 40 G Edge6064 10 668 23 140 Security Event Switch IP Access Control List Violation on 10 66 23 1 Oto 4 G Edgeb064 10 66 23 140 Security Event BAS Wrong User Name Password Combination on 1 Collection Disabled on LL Edqeb064 10 66 23 140 Security Event Switch IP Access Control List Violation on 10 66 23 1 Pending j j gas r Y Edge6064 10 656 23 140 Security Event BAS Wrong User Name Password Combination on 1 Si Legend Utilization LE Edge6064 10 668 23 140 Security Event Switch IP Access Control List Violation on 10 66 23 14 w change Figure 6 Example DCFM topology screen Topology Layout After upgrading to DCFM the topology layout options may be set back to defaults If that is the case you will still be able to customize various parts of the topology including the layout of devices and connections as well as group background colors to easily and quickly view and monitor devices in your SAN See the Topology Layout section in the Brocade DCFM Enterprise User s Manual for details on how to customize your topology map Migrating from Brocade ECFM to Brocade DCFM 14 of 22 FROM THE SOLUTIONS CENTER Solution Guide Views All of the user created views are migrated to DCFM during the upgrade process However there may be some views t
26. lows management of a single FOS fabric up to a 1 000 switch ports at a time It performs group switch management beyond the scope of Brocade Web Tools DCFM Professional is available with the purchase of any Brocade switch and is also available for download via the Brocade corporate Web A seamless migration path is available from DCFM Professional to DCFM Enterprise Brocade DCFM Enterprise is an enterprise class product targeted at customers that demand a management software solution with comprehensive support for e Brocade DCX Backbone based Data Center Fabric DCF e Fabric based encryption support for data at rest solutions e Unified manageability of the data center fabric from HBA ports through switch ports to storage ports DCFM Enterprise provides a holistic view of up to 24 fabrics and the connected devices whether local to the data center or geographically dispersed Policy based management enables IT organizations to meet their Service Level Agreements SLAs It provides unparalleled scalability and performance over existing Brocade management products DCFM Enterprise provides multi protocol networking support for e Fibre Channel e Fiber Connectivity FICON e Fibre Channel over IP FCIP e Fibre Channel Routing FCR e Internet SCSI iSCSI e Future Fibre Channel over Ethernet FCoE and Converged Enhanced Ethernet CEE Migrating from Brocade ECFM to Brocade DCFM 21 of 22 FROM THE SOLUTIONS CENTER Solution Guide A
27. play Ethernet Event Server Name Event St ae Web Server Port 80 Names Current Port 80 Security Misc Default Port en Software Configuration Client Export Port Server requires 14 consecutive free ports Discovery Starting Port 24600 FTP IP Configuration Memory Allocation Server IP 1166 70 134 240 Support Mode G Changes will take effect at the next application restart Cancel Apply Help Figure 10 SAN Options dialog box e If SSL is changed after the Web Start client has been installed the DCFM client link that is created in the Start Menu will no longer function This is because the network address is embedded in the link with HTTP or HTTPS That also means if the network address changes the link will fail e lf you go from no SSL to enabling SSL a Server not available message is displayed when you launch DCFM from the Start Menu DCFM 10 0 0 Log In Data Center Fabric Manager Enter User ID and Password to log onto the server Network Address main o o Server Name User ID haministrator Password ZET Kl Save password O Server not available at port 24600 To correct this you need to reinitiate the Web Start the DCFM Client from the DFCM Web page which reinstalls the client and fixes the link Migrating from Brocade ECFM to Brocade DCFM 17 of 22 FROM THE SOLUTIONS CENTER Solution Guide e lf SSL was enabled and you disable SSL a Login Erro
28. r message is displayed when you launch DCFM from the Start Menu Login Error 3 Login failed Please make sure the server is fully started To correct this you need to delete the link clear out the Java cache and reinitiate the Web Start the DCFM Client from the DFCM Web page This will reinstall the client and add the correct link If you encounter these errors you can always reach the client via the Web Start until you can fix the problem Running the Client Launch the DCFM client by either using the Start Menu link or using Web Start the DCFM Client from the DCFM Web page This displays the login screen which is very similar to the EFCM client login screen The two differences are the Network Address is now hard coded in and the setup button is missing The options that were under the setup button can be changed from inside DFCM which is a more logical place to make the changes The default user name and password have also remained the same Administrator and password User names are no longer case sensitive but passwords continue to be case sensitive In some cases a network may use virtual private network VPN or firewall technology which can prohibit communication between servers and clients In other words a client can find a server appear to log in but is immediately logged out because the server cannot reach the client To resolve this issue the ports in the table below need to be opened up in the firewall
29. tch e For pure FOS fabrics B Series switch running FOS 5 0 x or later e For mixed fabrics B Series switch running FOS 6 0 x or later in Native Interop mode Note the following e DCFM expects the FOS discovery switch to be running the most recent level of firmware in the fabric e You cannot use a switch in Access Gateway mode or a switch connected to the fabric either via EX_Ports or VEX_Ports e DCFM end users need to have administrative privileges on the discovery switch or equivalent access such as root factory or admin e Eclipse McDATA routers discovery and configuration is not Supported e Pure QLogic Cisco fabrics are not discovered e Only basic information is displayed for non Brocade devices Migrating from Brocade ECFM to Brocade DCFM 5 of 22 FROM THE SOLUTIONS CENTER Solution Guide Brocade DCFM allows you to bring down the current discovery switch for maintenance or replacement For High Availability HA with one discovery switch the recommendation is to configure Inter Switch Links ISLs to more than one switch in the fabric to handle potential port failures You could also Support HA with two discovery switches in which case the recommendation is to have at least two B Series switches for failover manual General recommendations for a discovery switch are e Small fabrics Use an entry level switch such as the Brocade 200E in switch not Access Gateway mode or the Brocade 300 e Medium fabrics You
30. tion or upgrade to deployed fabrics All the support required in Brocade switches is already in place The Brocade SMI Agent supports the evolving SMI S standard and the Brocade functionality not available through the standard The Brocade SMI Agent provides the following features e CIM agent compliant with SMI S with support for the following profiles e Server profile Supported by the SMI A with CIMOM vendor supplied providers e Fabric profile e Switch profile e Extender profile discovery only Migrating from Brocade ECFM to Brocade DCFM 12 of 22 FROM THE SOLUTIONS CENTER Solution Guide Fibre Channel FC Host Bus Adapter HBA profile Additional support for physical objects such as chassis blades fans power supplies temperature sensors and transceivers It supports the following Connection and account management Port performance and error statistics HBA and device information via FDMI Configuration download to switches Firmware download to switches SLP Service Location Protocol to discover SMI S profiles CIM agent management using CIM Indications life cycle indications for fabrics SANs nodes switches and switch ports and alert indications for many fabric events Basic support for non Brocade switches switches ports topology information and so on HTTP and HTTPS protocols HTTP and HTTPS port configuration Mutual authentication for clients and indications Security authorization using native O
31. to stay with a hybrid configuration for various reasons There may be mission critical directors on the private network while the devices on the company intranet may be much less critical Note that a hybrid configuration is a valid configuration and that the benefits and drawbacks of the private and open management network types apply to their respective portions of the hybrid management network Intranet gt a e DCFM client connections DCFM Server Figure 3 Hybrid management network configuration Migrating from Brocade ECFM to Brocade DCFM 9 of 22 FROM THE SOLUTIONS CENTER Solution Guide Split Management Network Split management networks are usually found when a Fibre Channel network spans more than one location or data center as shown in Figure 4 In a split management network some portion of the SAN is under management of a DCFM server in its location while another portion of the SAN is under management of a different DCFM server at another location The actual LAN topology for management is still likely to be either an open management network or a private network management network as described above DCFM Server DCFM Server Location 1 E Figure 4 Split management network configuration Zoning Using Brocade EFCM you can construct offline zone sets and save them into a global library or into individual per fabric libraries in the EFCM database The only time that an EFCM zone set is sent to the
Download Pdf Manuals
Related Search