Docu54667 Connectrix Manager Converged Network Edition 12.1.6 Release Notes

These release notes contain new features, code enhancements, and fixesin EMC Connectrix Manager Converged Network Edition (CMCNE)release 12.1.6.

Topics include:

◆ Product description.............................................................................. 2◆ New features and changes .................................................................. 8◆ There are no new software features with this release. ................... 8◆ Environment and system requirements .......................................... 11◆ Technical notes .................................................................................... 24◆ Documentation ................................................................................... 50◆ Software media, organization, and files.......................................... 51◆ Installation ........................................................................................... 54◆ Troubleshooting and getting help .................................................... 60

EMC® Connectrix® ManagerConverged Network Edition

Version 12.1.6

Release NotesP/N 302-000-471

Rev 03

July 28, 2014

1

2

Product description

Product descriptionConnectrix Manager Converged Network Edition (CMCNE) greatlysimplifies daily operations while improving the performance andreliability of the overall SAN and IP networking environment.CMCNE unifies under a single platform, full lifecycle networkmanagement for SAN, LAN and converged networks. CMCNEprovides a consistent user experience, across the entire ConnectrixB-series portfolio of products. This network management tool offersflexible and proactive SAN/IP network performance analysis inaddition to IP network configuration change deployment andmonitoring for compliance. CMCNE supports Fibre Channel SANs,including 16 Gbps platforms and Layer 2/3 IP networks.

CMCNE can reduce operation expenditures and help organizationsfocus on strategic IT initiatives by providing a common networkmanagement tool for provisioning, monitoring, reporting andtroubleshooting. CMCNE provides customizable health andperformance dashboards, with an easy-to-use graphical user interfaceand comprehensive features that automate repetitive tasks. WithCMCNE, storage and network administrators can proactivelymanage their SAN/IP network environments to support non-stopnetworking. CMCNE also provides network administrators theability to quickly access network topology, health and performancedata required to troubleshoot and remediate network issues.

Connectrix Manager Converged Network Edition (CMCNE) v12.1.6is the next major release of Connectrix Manager B-Series switchmanagement software. Revision 12.1.x of CMCNE introduces severalIP and SAN FC enhancements as well as dashboard improvements.

CMCNE v12.1.6 is available in several versions which can be brokendown in three major categories; SAN only management, SAN & IPmanagement, and IP only management capabilities. There are licenseoptions to enable some, all, and/or upgrade functionality from onecategory to another.

The CMCNE v12.1.6 SAN Management options are structured thesame as the previous CMCNE 11.x versions.

◆ CMCNE SAN Professional Edition — Intended for themanagement of smaller fabrics with Connectrix B Seriesdepartmental switches.

EMC Connectrix Manager Converged Network Edition (CMCNE) Version 12.1.6 Release Notes

Product description

E

◆ CMCNE SAN Professional Plus Edition — is a Professional Plusedition which is in between Professional and Enterprise forscalability support and also supports the ED-DCX-4S-B andED-DCX8510-4B.

◆ CMCNE SAN Enterprise Edition — A full-featured Enterpriseclass management solution for the largest of data center SANinfrastructures.

The three flavors differ predominantly in the set of supportedfeatures, hardware platforms, and supported scalability limits.

In addition to managing mixed fabrics, Connectrix ManagerConverged Network Edition for SAN Professional Plus and SANEnterprise have other features not found in Connectrix ManagerConverged Network Edition for SAN Professional, as detailed in thefollowing tables.

(a) Limited support(b) Basic Layer 2 configuration

Hardware PlatformCMCNE for SAN

ProfessionalCMCNE for SAN

Professional PlusCMCNE for SAN

Enterprise

Brocade 40xx, 54xx Embedded Blade Switches

DS-220B, DS-4100B, DS-5000B, ED-48000B

DS-300B, DS-5100B, DS-5300B,

MP-7500B/PB-48K-18i FCiP Port Blade(a)

AP-7600B, PB-48K-AP4-18 Application Blade (b) (b) (b)

PB-48K-16IP iSCSI Blade (2)

ED-DCX-B & ED-DCX8510-8B Directors x x

ED-DCX-4S-B & ED-DCX8510-4B Directors

ES-5832B Encryption Switch & PB-DCX-16EBEncryption Blade

MP-8000B Switch & PB-DCX-24FCOE Blade

MP-7800B FCiP Switch & PB-DCX-FX8-24 Blade

DS-6505B, DS-6510B, & DS-6520B

3MC Connectrix Manager Converged Network Edition (CMCNE) Version 12.1.6 Release Notes

4

Product description

(a) Support for Role-Based Access Control (RBAC) and security schemes (RADIUS, LDAP, ActiveDirectory, NIS/NIS+, and more)(b) Data persistence for up to two years of data, out-of-box Open Database Connectivity (ODBC), andJava Database Connectivity (JDBC) access

FeatureCMCNE for SAN

ProfessionalCMCNE for SAN

Professional Plus CMCNE for SAN Enterprise

# of fabrics 1 36 36

Type of fabrics supported FOS FOS FOS

# of ports 1,000 2, 560 9,000 (FOS)

Virtual Fabrics (Limited Support)

FICON x x

Encryption configuration

Quality of Service (QoS)

Traffic Isolation (TI) zones

FCR/LSAN Zoning x

FCIP Tunnels Interface (FOS only)

FCIP configuration

Port fencing (FOS Only)

RBAC and security schemes x (a) (a)

Real-Time Performance

Historical Performance x

DBMS (ODBC and JDBC) x (b) (b)

Top Talkers x

Performance thresholds x

HBA/CNA management

Server Virtualization support

Access Gateway

FCoE/DCB

HBA management

Partner software integration x

Call Home support x

Microsoft SCOM Management Pack x

Management Plugin for VMware vCenter x

Integrated SMI Agent x


Product description

E

CMCNE SAN Professional EditionCMCNE Professional showcases a subset of features and hardwareplatforms of CMCNE Enterprise. The Professional version, which is ano charge version, is intended for the management of smaller fabricswith Connectrix B Series departmental switches. It cannot manageDirector class products, has no FICON or routing support, and doesnot have remote clients or Call home support. The Professionalversion is limited to managing FOS departmental switch productsonly consisting of 1 fabric, 10 switches, 640 switch ports, and 1,000hosts or storage devices. CMCNE Professional presents several newbenefits to both new customers and existing Web Tools (FOS SwitchElement Manager) customers including (but not limited to):

◆ A topology view that provides a comprehensive fabricconnectivity map.

◆ Out-of-box database persistence for key information includingzoning changes, switch configuration backups, audit of changesmade to the environment, etc.

◆ The ability to perform group configuration activities acrossmultiple switches simultaneously (e.g., download firmware tomultiple switches simultaneously to meet aggressive changewindows, schedule backup of switch configurations into theCMCNE repository on an automated basis to enable rapidtroubleshooting and switch provisioning, replicate switchconfiguration from one "golden" switch to multiple otherswitches to maintain configuration consistency across theenterprise, etc.).

CMCNE SAN Professional Plus EditionCMCNE Professional Plus is designed for medium-sized businessesor departmental storage networks. Very similar in functionality to theEnterprise version but limited in features/scalability by a license keyto:

Support up to 36 fabrics and 2560 switch ports

◆ Support the ED-DCX-4S-B, ED-DCX8510-4B, encryptionproducts, extension products, and Brocade HBA/CNAs

◆ Can be updated to CMCNE SAN Enterprise (via a license keyupdate).


6

Product description

CMCNE SAN Enterprise EditionCMCNE Enterprise builds on top of the functionality available withCMCNE Professional, and provides a comprehensive fabricmanagement framework for the end-to-end management of the datacenter fabric. CMCNE Enterprise can scale to manage up to 9,000switch ports and also contains several new features to support notonly the new 16 Gb Director and switch products but some newfeatures available in FOS v7.2.0x as outlined in “New features andchanges” on page 8.

CMCNE SAN Enterprise is the full featured SAN managementpackage that supports all enterprise-class products/technologiesincluding the ED-DCX-B, ED-DCX8510-8B Backbone Directors,FICON, Fibre Channel Routing (FCR), Fibre Channel over IP (FCIP),etc.

Upgrades to CMCNE 12.1.6 will only be allowed from CMCNE 11.2.1and 12.x.x. For more information, refer to the "Migration andTransition" section of the Connectrix Manager Converged NetworkEdition Professional, Professional Plus, and Enterprise Version 12.1.6 UserGuide.

CMCNE 11.1.x users must first migrate to CMCNE 11.2.1 beforemigrating to CMCNE 12.1.6. To migrate from CMCNE 11.1.x toCMCNE 11.2.1, refer to the EMC Connectrix Manager ConvergedNetwork Edition Professional, Professional Plus and Enterprise Version11.2.1 User Guide available on EMC Online Support.

CMDCE 10.4.x users must first migrate to CMCNE 11.1.x, thenmigrate to CMCNE 11.2.1 or CMCNE 12.0.x, before migrating toCMCNE 12.1.6. To migrate from CMDCE 10.4.x to CMCNE 11.1.x,refer to the "Migration and Transition" section of the EMC ConnectrixManager Converged Network Edition Professional, Professional Plus andEnterprise Version 11.1.4 User Guide.

Note: Although migrating to CMCNE 11.1.1 is supported, EMC recommendsusing CMCNE 11.1.4 as the intermediate step when migrating from CMDCE10.4.x to CMCNE 12.0.x.

CMDCE 10.1.x and 10.3.x users must first migrate to CMDCE 10.4.5,then migrate to CMCNE 11.1.x, then migrate to CMCNE 11.2.1 orCMCNE 12.0.x, before migrating to CMCNE 12.1.6. To migrate fromCMDCE 10.1.x or 10.3.x to CMDCE 10.4.5, refer to the "Migration and


Product description

E

Transition" section of the EMC Connectrix Manager Data Center EditionProfessional, Professional Plus and Enterprise Version 10.4.5 User Guide.

Note: Upgrades from CMDCE 10.3.x or higher to CMCNE 11.1.x for SAN donot require a new software license key.

Note: Although migrating to CMCNE 11.1.1 is supported, EMC recommendsusing CMCNE 11.1.4 as the intermediate step when migrating from CMDCE10.4.x to CMCNE 12.0.x.

Connectrix Manager 9.6.x/9.7.x and Fabric Manager 5.4 / 5.5 usersmust first migrate to CMDCE 10.3.4, then migrate to CMDCE 10.4.5,then migrate to CMCNE 11.1.x, then migrate to CMCNE 11.2.1 orCMCNE 12.0.x before migrating to CMCNE 12.1.6. To migrate fromCM 9.x or Fabric Manager to CMDCE 10.3.4 and 10.4.5, refer to theEMC Connectrix Manager Data Center Edition Professional, ProfessionalPlus and Enterprise Version 10.4.5 User Guide.

To migrate from CMDCE 10.4.5 to CMCNE 11.1.x, refer to the"Migration and Transition" section of the EMC Connectrix ManagerConverged Network Edition Professional, Professional Plus and EnterpriseVersion 11.1.4 User Guide. Although migrating to CMCNE 11.1.1 issupported, EMC recommends using CMCNE 11.1.4 as theintermediate step when migrating from CMDCE 10.4.x to CMCNE12.0.x.

All of the user guides referenced in this section can be found on EMCOnline Support at http://support.emc.com.

CMCNE SAN and IP and IP only optionsCMCNE is also available in similarly scaled SAN & IP bundledversions as the SAN versions above and in IP only versions that allowincrementally scaling the number of IP switches that can be managedfrom 50 to 5050 IP switches. Refer to the table of available licenseoptions in the “Software media, organization, and files” on page 51.

Switch platform supportFor the list of supported platforms, refer to “Switch platform andfirmware requirements” on page 25.


8

New features and changes

New features and changesThis section lists new features and changes in this release.

Important updatesConnectrix Manager Converged Network Edition (CMCNE) 12.1.6 isa maintenance release based on CMCNE 12.1.5. All hardwareplatforms and features supported in CMCNE 12.1.5 are alsosupported in 12.1.6.

Note: CMCNE Professional Plus and Enterprise Editions are only supportedon 64-bit Windows operating systems. CMCNE Professional Edition issupported on 32-bit and 64-bit Windows operating systems.

Note: CMCNE 12.1.6 does not support EOS fabrics.

New hardwareThere are no new hardware features with this release.

New software featuresThere are no new software features with this release.

Fixed problemsThis section contains code enhancements and fixes for CMCNEv12.1.6. When a workaround to an issues is available, it is provided.This section contains fixed problems for the following version ofCMCNE:

◆ Closed in v12.1.6 on page 8

Closed in v12.1.6 The following defects are closed in v12.1.6 CMCNE.

Defect ID: DEFECT000490449 Technical Severity: HighSummary: SNMP Traps are not received after Network Advisor server is restarted.Symptom: Master log does not display SNMP traps.Risk of Fix: Medium Probability: HighFeature: UNDETERMINED Function: UNDER REVIEWReported In Release: Network Advisor12.1.1 Service Request ID: 1275040


Fixed problems

E

Defect ID: DEFECT000490644 Technical Severity: HighSummary: Zoning Window displays incorrect FC Addresses for ports.Symptom: User sees incorrect FC addresses for ports in the zoning window.Risk of Fix: Low Probability: HighFeature: ZONING Function: USABILITYReported In Release: Network Advisor12.1.4

Defect ID: DEFECT000491804 Technical Severity: HighSummary: WWN for Access Gateway (AG) is incorrectly computed causing device discovery to fail.Symptom: User is not able to discover the Fabric to which the AG with incorrect WWN is connected.Risk of Fix: Medium Probability: MediumFeature: DISCOVERY Function: SAN Switch DiscoveryReported In Release: Network Advisor12.1.4 Service Request ID: 1281454

Defect ID: DEFECT000477274Technical Severity: High Probability: MediumProduct: Network Advisor Technology: Partner IntegrationReported In Release: Network Advisor12.1.2 Technology Area: SMI AgentSymptom: For Brocade_Switch profile, CTP 1.4 execution fails.Condition: a. The class CIM_ElementStatisticalData expects only one instance in the output whereas it is getting

two instances – one for brocade_switchfcportstats and one for brocade_Switchfcporthistoricalstatistics.2. In the class Brocade_SwitchFCPOrtHistoricalStatistics, PacketsTransmitted and PrimitiveSeqProtocolErrCount, PacketsReceived - these are the mandatory properties which are currently not implemented in Network Advisor. As a result, CTP 1.4 execution fails for Brocade_Switch profile.

Defect ID: DEFECT000480568Technical Severity: High Probability: HighProduct: Network Advisor Technology: Application ManagementReported In Release: Network Advisor12.0.4 Technology Area: Installation & MigrationSymptom: Server does not start when doing silent installation as the console waits for user input and does not exit

the process to complete installation.Condition: Occurs only with silent installation

Defect ID: DEFECT000485113Technical Severity: High Probability: HighProduct: Network Advisor Technology: Partner IntegrationReported In Release: Network Advisor12.2.0 Technology Area: SMI AgentSymptom: Incorrect number of instances are returned for a Meta SAN for the class Brocade_SANInFabricCondition: Issue is seen for the class Brocade_SANInFabric

Defect ID: DEFECT000491552Technical Severity: Medium Probability: MediumProduct: Network Advisor Technology: Partner IntegrationReported In Release: Network Advisor12.0.3 Technology Area: SMI AgentSymptom: User cannot view all the instances of NPIV CIM_ActiveConnectionCondition: This issue occurs with NPIV connections


10

Fixed problems

Defect ID: DEFECT000497610Technical Severity: Medium Probability: MediumProduct: Network Advisor Technology: Partner IntegrationReported In Release: Network Advisor12.1.4 Technology Area: SMI AgentSymptom: With Network advisor 12.1.4, CPU usage of the application continues to spike when CIMOM is used.Condition: Occurs only when CIMOM is used.

Defect ID: DEFECT000497885Technical Severity: HighProduct: Network Advisor Technology: Partner IntegrationReported In Release: Network Advisor12.0.2 Technology Area: SMI AgentSymptom: On Network Advisor, incorrect information is returned by the class Brocade_SwitchInFabric for Access

Gateway switches, due to which Access Gateways incorrectly appear to be connected to multiple fabrics.Condition: Occurs for Access Gateways when using the class Brocade_SwitchInFabric.

Defect ID: DEFECT000500674Technical Severity: HighProduct: Network Advisor Technology: Partner IntegrationReported In Release: Network Advisor12.1.4 Technology Area: SMI AgentSymptom: User is unable to delete LSAN zones using the SMI Agent.Condition: Occurs only when using SMI Agent to delete LSAN zones

Defect ID: DEFECT000507408Technical Severity: Medium Probability: MediumProduct: Network Advisor Technology: Application ManagementReported In Release: Network Advisor12.1.6 Technology Area: Server PropertiesSymptom: Network Advisor is prone to heartbleed vulnerability if the customer enables SSL for postgresql

database.Condition: This issue occurs when Network Advisor's postgresql configuration is modified to use SSL.


Environment and system requirements

E

Environment and system requirementsThere are very important scalability limits for the Enterprise versionby type and size of the SANs to be managed by CMCNE v12.1.6. Thescalability limits are broken into three categories by size of theenvironment to be managed: small, medium and large, as detailed inTable 1, which summarizes the scalability limits for support.

Note: CMCNE Professional Plus and Enterprise Editions are only supportedon 64-bit Windows operating systems. CMCNE Professional Edition issupported on 32-bit and 64-bit Windows operating systems

a. The physical N_Port count is limited by the maximum number of switch portsallowed. Any additional N_Ports above the maximum number of switch portswould have to be virtual devices.

b. Performance Monitoring Polling is the interval at which the performance data isqueried from the managed elements when the historical data collection isturned on.

Table 2 summarizes the scalability limits for support with CMCNE.


Table 1 Enterprise supported limits by SAN size

Small Medium LargeNumber of Fabrics 8 16 36Number of Switches and Access Gateways 40 90 200Number of Switch Ports 2000 5000 9000Number of Physical/Virtual N_Ports a 5000 10000 20000PM Polling b 5 min 5 min 5 min

Table 2 Professional Plus supported limits by SAN size

Values Limits

Number of Fabrics 36

Number of Switches and Access Gateways 40

Number of Switch Ports 2560

Number of Physical/Virtual N_Ports a 4096

PM Polling b 5 min


12



Table 3 summarizes the scalability limits for support with CMCNE.



Table 4 summarizes the Enterprise supported limits by IP size.

Table 5 summarizes the Professional supported limits by IP size.

Table 3 Professional supported limits by SAN size

Values Limits

Number of Fabrics 1

Number of Switches and Access Gateways 15

Number of Switch Ports 1000

Number of Physical/Virtual N_Ports a 1000

PM Polling b N/A

Table 4 Enterprise-supported limits by IP size

Small Medium Large

Number of Products 1 - 20 21 - 200 201 - 505

Number of MPLS Products 1 1 100

Table 5 Professional-supported limits by IP size

Values Limits

Number of Products 20

Number of MPLS Products 0



E

Table 6 summarizes the enterprise supported limits by SAN size forSMI Agent only.


In conjunction with the SAN size scalability limits above thecomputing power of the service processor platform to be used for theCMCNE v12.1.6 server installation needs to be factored in. These arealso categorized by size of the SAN to be managed, as shown inTable 7.

Table 6 Enterprise-supported limits by SAN size for SMI Agent only

Values Small Medium Large

Number of Fabrics 8 16 24

Number of Switches and AccessGateways

40 90 200

Number of Switch Parts 2000 5000 9000

Number of Physical/Virtual N_Ports a 5000 10000 20000

Table 7 Operating System requirements for Server/Local client (page 1 of 2)

Operating system Supported packages

Microsoft Windows (x86 32-bit)• 2008 Server• 7 Enterprise

SAN with SMI Agent (Professional only)IP (Professional only)SMI Agent only

Microsoft Windows (x86 64-bit)• 2008 R2 Data Center Edition a

• 2008 R2 Standard Edition a

• 2008 R2 Enterprise Edition a

• 2012 R2 Data Center Edition b

• 2012 R2 Standard Edition b

• 8 Enterprise b

• 7 Enterprise c

SAN with SMI AgentIP onlySMI Agent onlySAN with SMI Agent + IP


14


a. EMCRemote 7.02.02 or higher is required to enable the remote supportcapability on this 64-bit operating system.

b. EMCRemote 7.10.02 or higher and ConnectEMC 5.04.16 or higher are requiredto enable the remote support and call home capabilities on this 64-bit operatingsystem.

c. EMCRemote 7.08.04 or higher is required to enable the remote supportcapability on this 64-bit operating system.

d. Modem based call home/remote support is forfeited when using VMs.

e. It is recommended that you run all CMCNE virtual CPUs on a single physicalCPU.

Note: The Windows-based server platform will also require one 9-pin serialport for connection of the EMC modem. For more information, refer to CallHome Setup Procedure chapter in the Connectrix Manager ConvergedNetwork Edition Professional, Professional Plus, and Enterprise Version12.1.6 User Guide.

VMware - Virtual Machines of the above 32-bit OSrunning VMWare’s OS:• ESX Server i 5.1 d, e

SAN with SMI Agent (Professional only)IP (Professional only)SMI Agent only

VMware - Virtual Machines of the above 64-bit OSrunning VMWare’s OS:• ESX Server i 5.1 d, e

SAN with SMI AgentIP onlySMI Agent onlySAN with SMI Agent + IP

Table 7 Operating System requirements for Server/Local client (page 2 of 2)

Operating system Supported packages



E

Operating system requirements for Remote clientTable 8 summarizes the minimum recommended operating systemrequirements for running the CMCNE Remote client application.

Host requirementsTable 9 through Table 11 summarize the minimum required hostrequirements for running CMCNE SAN with SMI Agent + IP onWindows systems.

Table 12 summarizes the minimum required host requirements forrunning CMCNE SAN with SMI Agent on Windows systems.

Table 13 summarizes the minimum required host requirements forrunning CMCNE IP on Windows systems.

Table 8 Operating system requirements for Remote client

Operating systems

Microsoft Windows (x86 32-bit)• 2008 Server• 7 Enterprise

Microsoft Windows (x86 64-bit)• 2008 R2 Data Center Edition• 2008 R2 Standard Edition• 2008 R2 Enterprise Edition• 2012 R2 Data Center Edition• 2012 R2 Standard Edition• 8 Enterprise• 7 Enterprise

Linux• RedHat Enterprise 6.1 Advanced Platform (x86 32-bit/64-bit)• RedHat Enterprise 6.2 Advanced Platform (x86 32-bit/64-bit)• RedHat Enterprise 6.3 Advanced Platform (x86 32-bit/64-bit)• SuSE Enterprise Server 11 (x86 32-bit)• Oracle Enterprise 6.1 (x86 32-bit/64-bit)• Oracle Enterprise 6.2 (x86 32-bit/64-bit)• Oracle Enterprise 6.3 (x86 32-bit/64-bit)

VMware - Virtual Machines of the above OS running VMWare’s OS:• ESX Server i 5.1


16


Table 14 summarizes the minimum required host requirements forrunning SMI Agent only on Windows systems.

Table 9 SAN with SMI Agent + IP host requirements

Server/Client Professional Professional Plus

Server plus 1 local client Intel Core2 duo 2GHz orequivalent

Intel Core2 duo 2GHz orequivalent

Remote client only N/A Intel Core2 duo 2GHz orequivalent

Table 10 SAN with SMI Agent + IP host requirements for server plus 1 local client

Server/Client Small LAN Medium LAN Large LAN

Small SAN Enterprise Intel Core2 duo 2GHz orequivalent

Intel Dual CPU Core2 duo2.4 GHz or equivalent


Medium SAN Enterprise Intel Dual CPU Core2 duo2.4 GHz or equivalent


Intel quad dual core or dualquad core, 2.4 GHz orequivalent

Large SAN Enterprise Intel Dual CPU Core2 duo2.4 GHz or equivalent


Intel quad dual core or dualquad core, 2.4 GHz orequivalent

Table 11 SAN with SMI Agent + IP host requirements for remote client

Server/Client Small LAN Medium LAN Large LAN

Small SAN Enterprise Intel Core2 duo 2GHz orequivalent



Medium SAN Enterprise Intel Dual CPU Core2 duo2.4 GHz or equivalent



Large SAN Enterprise Intel Dual CPU Core2 duo2.4 GHz or equivalent





E

Table 12 SAN with SMI Agent host requirements

Professional Professional Plus

Enterprise

Small Medium Large LAN

Server plus one local client Intel Core2 duo2GHz orequivalent

Intel Core2 duo2GHz or equivalent

Intel Core2 duo2GHz orequivalent

Intel Dual CPUCore2 duo 2.4GHzor equivalent

Intel Dual CPUCore2 duo 2.4 GHzor equivalent

Remote client only N/A Intel Core2 duo2GHz or equivalent


Intel Core2duo 2GHz orequivalent


Table 13 IP only host requirements

Professional

Enterprise

Small Medium Large

Server plus one local client Intel Core2 duo2GHz or equivalent


Intel Dual CPUCore2 duo 2.4GHzor equivalent


Remote client only N/A Intel Core2 duo2GHzor equivalent



Table 14 SMI Agent only host requirements

Enterprise

Small Medium Large

Server plus one local client Intel Core2 duo2GHz or equivalent



Remote client only Intel Core2 duo2GHz or equivalent

Intel Core2 duo 2GHzor equivalent



18


Memory requirementsTable 15 through Table 20 on page 19 summarize the minimumrequired system memory requirements for running CMCNE SANwith SMI Agent + IP on Windows.

Note: These requirements are only applicable when no other applications arerunning on CMCNE.

Note: Paging space should be equal to or exceed the physical memory size.

Note: The CMCNE servers for Enterprise and Professional Plus editions areonly supported on a 64 bit Windows system.

Note: CMCNE clients are supported on 32-bit and 64-bit Windows.

Table 15 SAN with SMI Agent + IP memory requirements


Server plus 1 local client 4 GB (32-bit)8 GB (64-bit)

16 GB (64-bit)

Remote client only N/A 4 GB

Table 16 SAN with SMI Agent + IP ((Enterprise) memory requirements for serverplus 1 local client

Small LAN Medium LAN Large LAN

Small SAN 8 GB 16 GB (64-bit) 16 GB (64-bit)

Medium SAN 16 GB (64-bit) 16 GB (64-bit) 16 GB (64-bit)

Large SAN 16 GB (64-bit) 16 GB (64-bit) 16 GB (64-bit)



E

Table 17 SAN with SMI Agent + IP (Enterprise) memory requirements for remoteclient


Small SAN Enterprise 4 GB 4 GB 4 GB

Medium SAN Enterprise 4 GB 4 GB 4 GB

Large SAN Enterprise 4 GB 4 GB 4 GB

Table 18 SAN with SMI Agent memory requirements

Server/Client Professional Professional Plus Enterprise Small Medium Large


16 GB (64-bit) 16 GB (64-bit) 16 GB (64-bit) 16 GB (64-bit)

Remote client only N/A 4 GB 4 GB 4 GB 4 GB

Table 19 IP only memory requirement

Server/Client Professional Enterprise Small Medium Large


16 GB (64-bit) 16 GB (64-bit) 16 GB (64-bit)

Remote client only N/A 4 GB 4 GB 4 GB

Table 20 SMI Agent only memory requirement

Server/ClientEnterpriseSmall Medium Large

Server plus 1 local client 4 GB 4 GB 4 GB

Remote client only 4 GB 4 GB 4 GB


20


Operating system cache requirementsIt is recommended that you use the System managed size (the OSallocates the required cache); however, if you choose to use a customsize, make sure you use the following memory settings for youroperating system listed in Table 21.

Disk space requirementsDisk space requirements

Table 22 through Table 24 on page 21 summarize the minimumrequired disk space requirements for running CMCNE SAN withSMI Agent + IP on Windows.

Note: It is recommended that you add an additional 100 GB of disk space ifyou use sFlow.

Note: It is recommended that you add an additional 40 GB of disk space forthe default temporary directory.

Table 21 Virtual memory requirements

Installed physicalmemory (RAM)size

Windows Server 2008 and Windows 7 Professional

Minimum pagingfile size

Maximum pagingfile size

2 GB 1 GB 4 GB

3 GB 1 GB 4 GB

4 GB 1 GB 4 GB

Greater than 4 GB 1 GB 4 GB

Table 22 SAN with SMI Agent + IP disk space requirements


Server plus 1 local client 10 GB 20 GB

Remote client only N/A 1 GB



E

Table 25 summarizes the minimum required disk space requirementsfor running CMCNE SAN with SMI Agent on Windows.

Table 23 SAN with SMI Agent + IP (Enterprise) disk space requirements for serverplus 1 local client





Table 24 SAN with SMI Agent + IP (Enterprise) disk space requirements forremote client





Table 25 SAN with SMI Agent disk space requirements

Server/Client ProfessionalProfessionalPlus

EnterpriseSmall Medium Large

Server plus 1 local client 10 GB 10 GB 20 GB 40 GB 60 GB

Remote client only N/A 1 GB 1 GB 1 GB 1 GB


22


Table 26 summarizes the minimum required disk space requirementsfor running CMCNE IP on Windows.

Table 27 summarizes the minimum required disk space requirementsfor running SMI Agent only on Windows.

Note: If you enable periodic supportSave or configure the CMCNE server asthe Upload Failure Data Capture location for monitored switches, thenadditional disc space will be required. Each switch supportSave files isapproximately 5 MB and each Upload Failure Data Capture file isapproximately 500 KB. To determine the disc space requirements, multiplythe frequency of scheduled supportSave files by 5 MB and the expectedUpload Failure Data Capture files by 500 KB, before the planned periodicpurge activity.

CMCNE 12.1.6 Client and Server system requirements

Note: CMCNE is not supported in a Network Address Translation (NAT)environment where the server and client are on different sides of the NATServer.

CMCNE has the following client and server system requirements:

◆ In the Professional edition, a single server supports a single client,which must be a local client only.

Table 26 IP only disk space requirements

Note: It is recommended that you add an additional 100 GB of disk space if you use sFlow.

Server/Client Professional PlusEnterpriseSmall Medium Large

Server plus 1 local client 10 GB 20 GB 40 GB 60 GB

Remote client only 1 GB 1 GB 1 GB 1 GB

Table 27 SMI Agent only disk space requirements

Server/ClientEnterpriseSmall Medium Large

Server plus 1 local client 20 GB 40 GB 60 GB

Remote client only 1 GB 1 GB 1 GB



E

◆ In Professional Plus and Enterprise editions, a single serversupports a maximum of 25 clients, which can be local or remoteon 64-bit servers. To support more than 8 clients, you must makethe following changes to your configuration:

• Increase the server memory size to 3 GB. You can configure theserver memory size from the Options dialog box, MemoryAllocations pane.

• Increase the PostgreSQL database shared buffers memoryallocation to 1024 MB by editing the Install_Home\data\databases\postgresql.conf file. See step 7 onpage 34 for more details.

Browser requirementsThe launch of CMCNE and the launch of Element Manager (WebTools) from the application is supported from the following browserswith Java plug-in:

Browsers◆ Windows Internet Explorer under Windows

◆ Firefox under Windows or Linux

JRE Support◆ Oracle JRE 1.7.0 update 55 for CMCNE

◆ Oracle JRE 1.7.0 update 55 for Web Tools

Note: JRE's higher than 1.7.0_55 are not supported with CMCNE 12.1.6.

Note: Web Tools launch from CMCNE is also supported for the abovecombinations.

Note: JRE 1.7_55 is not bundled with CMCNE 12.1.6, but can be used forremote clients.

For the website listing patch information, go to

http://www.oracle.com/technetwork/java/javase/downloads/index.html


24

Technical notes

Virtual Machine managementTable 28 lists the VMware vCenter, ESX and ESXi versions supportedby the Management module within CMCNE. The Managementmodule discovers the data from vCenter, ESX and ESXi servers.

Technical notesThis section contains the following information:

◆ “Switch platform and firmware requirements” on page 25

◆ “Virtual Connect Enterprise Manager (VCEM) server discoveryrequirements” on page 28

◆ “Important notes” on page 29

◆ “Performance Statistics Counters - Calculation Formulae ” onpage 36

◆ “Server platform information” on page 44

◆ “Third-party software” on page 48

◆ “Connectrix service processor information” on page 48

Table 28 Virtual Machine management

Machine management:vCenter, ESX, and ESXi supported versions

ESX 4.0, 4.1

ESXi 4.0, 5.0, 5.1

vCenter 4.0, 4.1, 5.0, 5.1


Technical notes

E

Switch platform and firmware requirementsThe following table lists the supported EMC Connectrix Director andSwitch products and supported firmware versions for use withCMCNE.

Operating system Switch/Director

Switch type (B-Model) firmware versions

FOS 6.4.2a or higher DS-4100BMP-7500BDS-4900BDS-5000BAP-7600BDS-300BDS-5100BDS-5300BES-5832BMP-7800BMP-8000BED-48000BED-DCX-BED-DCX-4S-B

FOS 6.2.2b DS-220B

FOS 7.0.0a or higher DS-6510BED-DCX8510-8BED-DCX8510-4B


26

Technical notes

a. The MP-8000B is not supported with FOS 7.2.0x or later.

Note: The minimum firmware version does not indicate the minimum switchfirmware version supported by EMC, but rather the min version that isneeded for CMCNE to properly recognize the switch. The EMC SupportMatrix takes precedence and if a higher version is listed in the ESM for acertain product / blade then that is the version that should be used.

FOS 7.0.1 or higher DS-300BDS-5100BDS-5300BES-5832BDS-6505BDS-6510BMP-7800BMP-8000BED-DCX-BED-DCX-4S-BED-DCX8510-8BED-DCX8510-4B

FOS 7.1.0a or higher DS-300BDS-5100BDS-5300BES-5832BDS-6505BDS-6510BDS-6520BMP-7800BMP-8000B a

ED-DCX-BED-DCX-4S-BED-DCX8510-8BED-DCX8510-4B

Operating system Switch/Director


Technical notes

E

a. Network OS 2.0 is not supported.

b. 12.1.0f and 12.2.1 are not supported.

Note: EMC does not supply direct support for theses Brocade Ethernetswitches; however CMCNE can manage them.

Operating system Device type

Network OS v4.0.0 & v4.0.1 VDX 6740, 6740T, 8770, 6710, 6720, 6730

Network OS v3.0.0, v3.0.0a, v3.0.0b, v3.0.1,v3.0.1a

VDX 8770, 6710, 6720, 6730

Network OS v2.1a, v2.1.1, v2.1.1a, v2.1.1b,v2.1.2a

VDX 6710, 6720, 6730

Network OS v2.1.1_fuj VDX 2730

2.7.02x, 2.7.03x, 2.8.x, 2.9.x BigIron RX

7.1.x, 7.2.x FastIron FGS, FGS-STK, FLS, FLS-STK, SuperX

7.1.x, 7.2.x, 7.3.x, 7.4.x FESX, FWS

7.1.x, 7.2.x, 7.3.x, 7.4.x, 8.0.x FastIron CX, FCX-STK

7.1.x, 7.2.x, 7.3.x, 7.4.x, 8.0.x, FastIron SX

7.3.x, 7.4.x, 8.0.x FastIron ICX 6610

7.4.x, 8.0.x FastIron ICX 6430, 6450

7.5a Brocade 6650

5.0.x, 5.1.x, 5.2.x, 5.3.x, 5.4.x, 5.5.x NetIron CES, CER, MLX, XMR, MLXe

2.0.x, 2.1.x, 2.2.x Brocade 6910

12.1.xb 12.2.xb, 12.3.x, 12.4, 12.5 ServerIron ADX

10.2.01x and 11.0.x ServerIron

4.1.x, 4.2.x and 7.3.x, 7.4.x TurboIron 24X

4.3.1.0, WiNG 5.1, 5.2, 5.3, 5.4 Wireless Controllers - RFS 4000, RFS 6000, RFS 7000

4.1.x and 4.1.01x FastIron FES


28

Technical notes

Seed switch requirements

Fabric OSRequires Fabric OS 6.4.2a or later for the seed switch in a pure FabricOS fabric.

Not supported The following switch products are not supported by CMCNE:

◆ MP-1620M, MP-2640M, and AP-7420B routers

◆ ED-10000M, ED-140M, ED-64M, ED-1032, and ED-12000BDirectors

◆ DS-8B, DS-16B, DS-8B2, and DS-16B2 switches

◆ ED-24000B

◆ DS-8B3, DS-16B3, DS-32B2

◆ DS-24M2, DS-16M, DS-32M, DS-16M2, DS-32M2

◆ DS-4700M and DS-4400M

For the most up-to-date compatibility information, refer to the EMCSupport Matrix, located at http://elabnavigator.emc.com.

Virtual Connect Enterprise Manager (VCEM) server discovery requirementsThe following table lists the supported components for discoveringVCEM servers through CMCNE.

Component Version

HP SIM Version v6.2, v7.1

HP VCEM version v6.2, v7.1

OA firmware Onboard Administrator (OA) v2.41 or later is supported

VC E-net module firmware (HP VC 8Gb 20-PortFC Module & HP VC 8Gb 24-Port FC Module)

v3.15

Hardware tested HP BladeSystem c3000 or c7000

Servers Proliant BL465c G7, Proliant BL460c G6

HBA Brocade 804 8Gb FC HBA, Emulex LPe1205-HP 8Gb FC HBA, QLogicQMH2562 8Gb FC HBA


Technical notes

E

Note: EMC does not supply direct support for these components; howeverCMCNE can manage them.

Important notesThis section lists information that you should consider before you useCMCNE 12.1.6. See the Connectrix Manager Converged Network EditionProfessional, Professional Plus, and Enterprise Version 12.1.6 User Guidefor full details on the following notes.

Important notes that apply to SAN installations1. Host based stand-alone SMI agents cannot manage products with

Fabric OS v7.0.x and higher. It requires use of the integrated SMIAgent with CMCNE 12.0.1 and higher.

2. CMCNE cannot manage an ESXi 5.0 host due to a VMware issue (KB 2012672: SFCB CIMOM on ESXi 5.0 is incompatible with JRE1.6 U29 and later). The user is hence required to update to ESXi5.0 update 1 or later to be able to manage the host in CMCNEthrough the host adapter discovery.

3. If you see the following error message “Signature could not bevalidated” during firmware download or technical support datacollection (Fabric OS and Network OS devices only) orconfiguration backup/restore (Network OS devices only) usingSCP/SFTP, then it could be due to a mismatch in the signaturekey used in the ssh handshake between the switch and SCP/SFTPserver. Try the following cli command work-around to addressthe issue:

◆ For Fabric OS devices

sw0:FID128:admin> sshutil delknownhostIP Address/Hostname to be deleted: <IP Address of SSH server to bedeleted>

◆ For Network OS devicesFirmware version 3.0 and later

sw0# clear ssh-key <IP Address of SSH server to be deleted>

◆ Firmware version 2.1.1b

sw0#execute-script sshdeleteknownhostIP Address/Hostname to be deleted: <IP Address of SSH server to bedeleted>


30

Technical notes

If the above does not work, go to Server > Options > SoftwareConfiguration > FTP/SFTP/SCP, and uncheck the SCP/SFTPoption.

4. Firmware upgrade to an MP-8000B platform using CMCNE willbe disruptive to I/O on the MP-8000B platform.

5. Firmware Download operation on Fabric OS switches fails whentrying to upgrade from FOS v6.4.2a to v7.0.2c. The workaround isto use CLI for this operation.

6. Trying to move 200+ ports to a Logical Switch with ‘Reset toDefault’ option selected, results in operation time-out.

7. During installation, if the CMCNE database initialization fails,user needs to verify access to the drive on which the installation isperformed. If the user “Administrator” alone has access to thedrive, then required permissions should also be provided to“Authenticated Users” and then continue with the installation.

8. There will be a delay in populating the Gige port details in theNetwork Advisor client if the server IP is not registered on theswitch to receive SNMP traps from the switch.

9. After upgrading to CMCNE 12.x from 11.x, SSL-based productcommunication will fail if the devices have ‘weak’ authenticationcertificates. The user will see a ‘4002’ error on attempting todiscover such devices. Devices discovered prior to migration willnot be manageable in CMCNE after migration. Java 1.7 used byCMCNE 12.x disables the use of certificates with ‘weak’authentication. The certificates on such devices need to beupdated to be compliant with JRE v1.7. Please refer to the ‘SecureSockets Layer protocol’ section of FOS Admin guide for details onupdating certificates.

10. Receive Throughput measure is not updated in Flow Visiondialog.

11. D-port test fails for F-ports with the result as “null” in the report.

12. In Real Time performance graphs, percentage utilization willfluctuate between 0 -100 if a single port is selected. Theworkaround is to select more than one port while generating RealTime performance graphs.

13. CMCNE uses SNMPv3 by default to discover SAN products. Ifrequired, user can select the “Manual” option in Discovery dialogand choose SNMPv1 for discovery.


Technical notes

E

14. There could be false alarms indicating that the Zone database andthe active zone configurations are modified if any of the names ofthe zoning elements (zones, zone configurations or aliases)contain underscores (‘_’) in the Zone database that is saved oractivated on to a fabric by Network Advisor.

15. A delay of 5 to 7 minutes is seen when Web Tools is launched on asystem (through CMCNE or directly in a web browser) whereinternet access is not available and the network does not return a‘destination unreachable’ message. This issue occurs as Java triesto validate the SSL certificates with external CAs. This problemcan be avoided on such systems by modifying the below Javaproperties:

On Windows: C:\Users\<logged inusername>\AppData\LocalLow\Sun\Java\Deployment\deployment.properties

On Linux: home/< logged in username>/.java/deployment/deployment.properties

In the ‘deployment.properties’ file, edit the below parametersand set them to ‘false’. If these parameters are not present, addthem and save the file. Then re-launch Web tools.

deployment.security.validation.ocsp = false

deployment.security.validation.crl = false

Display of Logical switchesIf you create Logical switches through the Logical Switch dialog box,the Logical switch displays under undiscovered Logical Switch in theexisting Logical Switches Panel. You have to rediscover the newlycreated logical switch fabric, by going to the discovery dialog, andadding the IP address of the chassis using the add dialog.

Destination columns are blank for ES-5832B Encryption switch intop talkers dialogWhen the Top Talkers dialog box is launched for the ES-5832BEncryption Switch, the columns Destination, Destination port andDestination switch port are sometimes empty.

SSL connections using certificates with MD5 signaturesTo avoid potential security vulnerabilities, CMCNE 12.1.x and laterdo not support SSL connections using certificates with MD5signatures. If CMCNE is configured to use HTTPS instead of HTTPwhen communicating with SAN switches, and the SAN switch has a


32

Technical notes

certificate installed that is signed with an MD5 algorithm, discoveryof the switch fails with the following pop-up message:“Authentication failure during discovery operation: 4002.”

The recommended solution is to replace the certificate on the networkdevice with a certificate using the more secure SHA signature. If thatis not practical, the CMCNE server configuration can be changed toaccept MD5 signatures. Note that accepting MD5 signatures mayresult in warnings from network security scanning tools.

To accept MD5 signatures, edit the following text file:

On 32-bit Windows: <install-dir>/jre/lib/security/java.securityOn 64-bit Windows: <install-dir>/jre64/lib/security/java.security

Remove “MD5” from the following line near the end of the file:

jdk.tls.disabledAlgorithms=MD5, DES, 3DES, RC2

The modified line should appear as:

jdk.tls.disabledAlgorithms=DES, 3DES, RC2

The change will take effect the next time the CMCNE server isrestarted.

Reset Ports operation in Logical Switches dialog◆ Reset ports to default operation is applicable only when the ports

are moved from one Logical Switch to another Logical Switchthrough the Right Arrow button i.e., from (Chassis portsTree/Tree Table) LHS to (Logical Switches Device Tree) RHSdevice tree.

It is not applicable when:

a. Ports from a Logical Switch are moved to default LogicalSwitch through Left Arrow button, i.e., from (Logical SwitchesDevice Tree) RHS to (Chassis ports Tree/Tree Table) LHS.

b. When a Logical Switch is deleted - its ports will not be reset todefault before moving to Default Logical Switch before itsdeletion.

Ports which are moved to the default logical switch can be reset todefault, if they are moved from (Chassis ports Tree/Tree Table)LHS to (Logical Switches Device Tree) RHS device tree.

◆ Reset ports to default operation will not clear FCIP configurationsin the following scenarios:


Technical notes

E

a. In MP-7500B and FR4-18i, VE ports cannot be reset to defaultunless their corresponding GE ports are cleared of their FCIPconfigurations.

b. In MP-7800B and FX8-24, GE ports cannot be reset to defaultunless their corresponding VE ports are cleared of their FCIPconfigurations.

Important notes that apply to IP installations1. Adaptive polling turned off by default for all IP devices (even for

migrated servers).

2. Each IP product has a System max value that can be configuredfor various parameters, such as "ip-filter-sys" for ACLs. CMCNEdeployments do not check whether the payload being sent to thedevice has a number greater than the system-max value. In suchdeployment scenarios, the deployment may report success eventhough the number was limited to the system-max value. Toensure successful deployments, make sure the payload being sentis no greater than System max value.

3. Syslog messages will not be received for the VDX 8770 that isconfigured with different IP addresses for CPs

4. Simplified image upgrade is recommended for NI devicesrunning 5.3 and above.

5. Fixed Form Factor switches running Network OS 4.0 aredisplayed with ‘Product Type’ as ‘Router’ in Network Advisor,even when they do not have Layer 3 license.

6. When two ports of the same storage are connected to two VDXdevices, only of the attached ports is displayed in the Zoningdialog.

IP address and detailed reportsIP Management Ports will not be consistent with the CLI port namingconventions. These are caused by SNMP index and port nameinconsistencies. In some cases, Management ports will not bedisplayed in the reports.

Boot, monitor, firmware image updates1. CMCNE does not support boot and firmware upgrade and

downgrade for ADX devices running 12.1 or above.


34

Technical notes

2. Firmware Image Update on FastIron devices using ConfigurationWizard using "SCP only" or "SCP then TFTP" results in thecorruption of the flash to which image is pushed. Use CLI asworkaround.

3. Firmware Download to NetIron CES devices fails via SCP withthe error message ‘there is not enough space on MP flash’.

Important notes that apply to both SAN and IP installations1. 64-bit OS is required to run Enterprise and Professional Plus

Editions.

2. M-series switches are unsupported as Seed switch or memberswitch from 12.0.1 and higher.

3. Privileges related to SAN and IP features are prefixed with'SAN –' and 'IP –' strings. After migration from an older version,new privilege names will be displayed in the Role Managementdialog with these prefixes.

4. CMCNE server startup and restart can take up to 10+ minutes tocomplete.

5. When configuring CMCNE in SSL enable mode in applicationconfiguration wizard, please ensure that both HTTP and HTTPSports are free and available for CMCNE. Currently theapplication checks only if the HTTPS configured port is availableand not the HTTP port.

6. To avoid excessive telnet/ssh login messages in the CMCNEmaster log and event report, and the device CLI console, disablelazy polling by un-checking the "Enable lazy polling" checkbox inIP Discovery Global Settings > Preferences Dialog.

7. In CMCNE 12.0.x, the number of client connections supportedhas increased to 25. Please refer to the "Installation" section ofCMCNE User Guide for the details. In addition to those details,the following database memory setting is required:

a. The PostgreSQL’s parameter “shared buffers” memoryallocation should be increased to 1024 MB. (This setting can bedone by editing <installation_directory>\data\databases\postgresql.conf file.)

Change “shared_buffers = 256 MB “To “shared_buffers = 1024 MB”

b. Server needs to be restarted.


Technical notes

E

8. During installation, it is recommended to use the Hostname asthe server IP configuration.

9. In CMCNE 12.x.x, 75-day Trial versions (for both full install andmigration) are only available for Enterprise Edition. ProfessionalPlus Edition is no longer available for 75-day Trials.

10. If you are using the ODBC connection from a remote host to thedatabase, after migrating to 12.0.x, you will no longer be able toconnect from the remote host. If you want to connect from theremote host, please refer to the “Configuring remote client accessto the database” section in the “Installation” chapter of theCMCNE User Guide.

Security vulnerabilityIf the CMCNE Server resides on a public lan it may be vulnerable toremote attacks which can transfer and execute arbitrary code.Resolved in CMCNE v12.1.2 under defect# 443127. For furtherinformation see EMC ESA-2013-089. As a security best practice,customers are strongly advised to isolate the CMCNE server fromexternal networks using VLANs and/or firewall rules only allowingauthorized administrators to interact with the CMCNE server.

Patch installer troubleshootingPatch installer may not launch if UAC is enabled on a Windows7/2008/2008R2 Editions. User has to first disable the UAC using theprocedure provided in the troubleshooting section of the CMCNEUser Guide and then launch the patch installer.

Support Saves may take a long time with large databasesAs databases grow larger from Event, sFlow, and PerformanceCollector data, the support save operation may take a long time torun. Larger databases will promote longer support save operations.Make sure you have a minimum of 20 GB disk space for support saveand backup operations.

Installation on Network Mounted Drives is not supportedInstallation onto a windows network mounted drive is not supportedbut install is allowed and DB fails to start.

Client disconnectsUnder heavy server load or degraded network links, there is apotential for Network Advisor client to get disconnected from theserver. Work around is to restart the client.


36

Technical notes

Performance Statistics Counters - Calculation FormulaeFor calculating the statistics for FC, GE, FCIP and TE port we useSNMP to query the respective OIDs, mentioned below in the table.

For calculating the HBA and CNA statistics, we use the APIsprovided by HCM. And for EE monitors we use HTTP to get the TX,RX and CRC error values.

Polling interval for historical graph is 5 min and for real-time, itchanges based on the granularity value selected in the Real Timegraph dialog.

Counter Name Type Protocol used

Source value Formula

TX FC SNMP .1.3.6.1.3.94.4.5.1.6 TX = (Delta valuea / (1000 * 1000))

/ (Polling intervalb)

RX FC SNMP .1.3.6.1.3.94.4.5.1.7 RX = (Delta valuea / (1000 * 1000))


TX GE SNMP .1.3.6.1.2.1.31.1.1.1.10 TX = (Delta valuea / (1000 * 1000))


RX GE SNMP .1.3.6.1.2.1.31.1.1.1.6 RX = (Delta valuea/ (1000 * 1000))


TX FCIP SNMP .1.3.6.1.2.1.31.1.1.1.10 TX = (Delta valuea / (1000 * 1000))


RX FCIP SNMP .1.3.6.1.2.1.31.1.1.1.6 RX = (Delta valuea / (1000 * 1000))


Uncompressed Tx/Rx MB/sec

FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.6 (Delta valuea / (1000 * 1000)) / (

Polling intervalb)

TX EE Monitors

HTTP PortRX (variable from the return html file)

TX = (Delta valuea / (1000 * 1000))



Technical notes

E

RX EE Monitors

HTTP PortTX (variable from the return html file)

RX = (Delta valuea / (1000 * 1000))


TX HBA, CNA HCM API NA TX = (Delta valuea / (1000 * 1000))


RX HBA, CNA HCM API NA RX = (Delta valuea / (1000 * 1000))


TX TE SNMP .1.3.6.1.2.1.31.1.1.1.6 TX = (Delta valuea / (1000 * 1000))


RX TE SNMP .1.3.6.1.2.1.31.1.1.1.10 RX = (Delta valuea / (1000 * 1000))


TX% / RX% FC, GE, FCIP, HBA, CNA

NA NA TX% or RX% = ((TX or RX) / ((105000000 * port speed)*( Polling

interval2))) * 100

If Utilization is less than 1 then the value is it to 0.0

TX% / RX% (Pre 6.4.1 Edison release)

TE NA NA TX% or RX% = ((TX or RX) / ((105000000 * 10)*( Polling

intervalb))) * 100

If Utilization is less than 1 then the value is it to 0.0

Compression Ratio

FCIP .1.3.6.1.4.1.1588.4.1.1.4 Compression Ratio = current value/ 1000

Since for compression ratio we will take the current compression ratio value

Receive EOF TE .1.3.6.1.2.1.16.1.1.1.5 Receive EOF = Delta valuea / (1000 * 1000)

Other Counters Other counters = Delta valuea

Counter Name Type Protocol used

Source value Formula


38

Technical notes

a. Delta value1: is the difference of value retrieved between the two consecutivepoling cycles.

b. Polling interval2: duration between the two polling cycle in seconds.

Other counters are listed in the following table:

Counter Name Type Protocol used Source value

CRC Errors FC SNMP .1.3.6.1.3.94.4.5.1.40

Signal Losses FC SNMP .1.3.6.1.3.94.4.5.1.43

Sync Losses FC SNMP .1.3.6.1.3.94.4.5.1.44

Link Failures FC SNMP .1.3.6.1.3.94.4.5.1.39

Sequence Errors FC SNMP .1.3.6.1.3.94.4.5.1.42

Invalid Transmissions FC SNMP .1.3.6.1.3.94.4.5.1.41

Rx Link Resets FC SNMP .1.3.6.1.3.94.4.5.1.33

Tx Link Resets FC SNMP .1.3.6.1.3.94.4.5.1.34

C3 Discard FC SNMP .1.3.6.1.3.94.4.5.1.28

C3 Discard Rx Timeout FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.27.1.25

C3 Discard Unreachable

FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.27.1.26

C3 Discard Tx Timeout FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.27.1.27

C3 Discard Others FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.27.1.28

Encode Error Out FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.27.1.29

Temperature FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.1

Voltage FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.2

Current FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.3

Rx Power FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.4

Tx Power FC SNMP .1.3.6.1.4.1.1588.2.1.1.1.28.1.1.5

Latency FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.5


Technical notes

E

Important notes for the SMI Agent1. For CMCNE that has more than 30K instances (2 MB zones), the

CIMOM takes more memory to generate CIM instances.

If user performs Enumerate Instances or Enumerate InstancesNames and total number of size is more than 2 MB for allmanaged fabrics, then CIM_ERROR_FAILED will be thrown asthe Total Zone DB size is more than 2 MB. For such configuration,User need to use Association calls.

Note: If the total zone DB is more than 1 MB/more than 10000 instancesthen user should change the max jvm heap size to 2048 MB to fetch thedata without failure in 64 bit machine.

2. SMI alert indication BRCD60 is not sent out to SMI clients ifFabric OS switches are discovered but SNMP trap registration hasfailed. Ensure that CMCNE server is successfully registered fortraps on all switches.

Dropped Packets FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.3

Link Retransmits FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.2

Timeout Retransmits FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.9

Fast Retransmits FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.10

Duplicate Ack Received FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.11

Window Size RTT FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.12

TCP Out of Order Segments

FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.13

SlowStart Status FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.14

CRC Errors EE Monitors HTTP PortCRC (variable from the return html file)

Counter Name Type Protocol used Source value


40

Technical notes

3. If DCB switches are running Fabric OS 6.3.x and 6.3.1_cee,VLAN/ACL deployment through SMI-A will fail. It is required toupgrade the DCB Fabric OS to 6.4.x/6.3.1_dcb/7.0.x forVLAN/ACL deployment support through SMI Agent.

Indications delivery depends on SAN size and SNMP registrationThe time to deliver the indication will vary based on CMCNE SANsize selected during installation. If large SAN size is selected,indication delivery time will be longer.

Provider classes may take more time to update the fabric changes ifthe switches managed in CMCNE are not SNMP registered. As thiswould cause a delay in indication delivery, all the switches managedin CMCNE should be SNMP registered.

Logging for CIMOMThe default logging level is "INFO" in integrated Agent. To changethe logging level to DEBUG, update the "com.brocade" categoryvalue in cimom-log4j.xml file present in <Installation Dir>\conffolder.

The log file size and number of log files also can be changed bymodifying the file rolling appender parameters in thiscimom-log4j.xml file.

Logging Level, File size and Number of Log files can be changed bymodifying the following fields:"Log Level", "File Size" and "Numberof Files" from Configuration Tool through CIMOM tab.

Service Location Protocol (SLP) supportThe Management application SMI Agent uses Service LocationProtocol (SLP) to allow applications to discover the existence,location, and configuration of WBEM services in enterprise networks.

You do not need a WBEM client to use SLP discovery to find a WBEMServer; that is, SLP discovery might already know about the locationand capabilities of the WBEM Server to which it wants to send itsrequests. In such environments, you do not need to start the SLPcomponent of the Management application SMI Agent.

However, in a dynamically changing enterprise networkenvironment, many WBEM clients might choose to use SLP discoveryto find the location and capabilities of other WBEM Servers. In suchenvironments, start the SLP component of the Managementapplication SMI Agent to allow advertisement of its existence,location, and capabilities.


Technical notes

E

SLP installation is optional and you can configure it duringManagement application configuration. Once installed, SLP startswhenever the Management application SMI Agent starts.

Management SMI Agent SLP application supportManagement SMI Agent SLP application support includes thefollowing components:

◆ slpd script starts the slpd platform.

◆ slpd program acts as a Service Agent (SA). A different slpd binaryexecutable file exists for UNIX and Windows systems.

◆ slptool script starts the slptool platform-specific program.

◆ slptool program can be used to verify whether SLP is operatingproperly or not.

By default, the Management application SMI Agent is configured toadvertise itself as a Service Agent (SA). The advertised SLP templateshows its location (IP address) and the WBEM Services it supports.The default advertised WBEM services show the Managementapplication SMI Agent:

◆ Accepts WBEM requests over HTTP without SSL on TCP port5988

◆ Accepts WBEM requests over HTTPS using SSL on TCP port 5989

slptool commandsUse the following slptool commands to verify whether the SLP isoperating properly.

◆ slptool findsrvs service:service-agent

Use this command to verify that the Management applicationSMI Agent SLP service is properly advertising its WBEM services.

Example output: service:service-agent://127.0.0.1,65535

◆ slptool findsrvs service:wbem

Use this command to verify that the Management applicationSMI Agent SLP service is properly advertising its WBEM services.

Example outputs:

service:wbem:https://10.0.1.3:5989,65535service:wbem:http://10.0.1.3:5988,65535

This output shows the functionalities of Management applicationSMI Agent:


42

Technical notes

◆ Accepts WBEM requests over HTTP using SSL on TCP port 5989

◆ Accepts WBEM requests over HTTP without SSL on TCP port5988

◆ slptool findattrs service:wbem:http://IP_Address:Port

Use this command to verify that Management application SMIAgent SLP service is properly advertising its WBEM SLPtemplate over the HTTP protocol.

Example input:

slptool findattrs service:wbem: http://10.0.1.2:5988

Note: Where IP_Address:Port is the IP address and port number thatdisplay when you use the slptool findsrvs service:wbem command.

◆ slptool findattrs service:wbem:https://IP_Address:Port

Use this command to verify that the Management applicationSMI Agent SLP service is properly advertising its WBEM SLPtemplate over the HTTPS protocol.

Example input:

slptool findattrs service:wbem:https://10.0.1.2:5989

Note: Where IP_Address:Port is the IP address and port number thatdisplay when you use the slptool findsrvs service:wbem command.

SLP on Windows systemsThis section describes how to verify the SLP daemon on Windowssystems.

SLP file locations:

◆ SLP log—Management_Application\cimom \cfg\slp.log

◆ SLP daemon—Management_Application\cimom\cfg\slp.confThe SLP daemon can be reconfigured by modifying this file.

◆ SLP register—Management_Application\cimom\cfg\slp.regstatically register an application that does not dynamicallyregister with SLP using SLPAPIs by modifying this file.

For more information about these files, read the commentscontained in them, or refer to

http://www.openslp.org/doc/html/UsersGuide/index.html


Technical notes

E

Verifying SLP service installation and operation on Windowssystems:

1. Launch the Server Management Console from the Start menu.

2. Click Start to start the SLP service.

3. Open a command window.

4. Type cd c:\Management_Application\cimom \bin and pressEnter to change to the directory where slpd.bat is located.

5. Type > slptool findsrvs service:service-agent and press Enter toverify the SLP service is running as a Service Agent.

6. Type > slptool findsrvs service:wbem and press Enter to verifythe SLP service is advertising its WBEM services.

7. Choose one of the following options to verify the SLP service isadvertising the WBEM SLP template over its configured clientprotocol adapters:

• Type > slptool findattrs service:wbem:http://IP_Address:Portand press Enter.

• Type> slptool findattrsservice:wbem:https://IP_Address:Portand press Enter.

Note: Where IP_Address:Port is the IP address and port number that displaywhen you use the slptool findsrvs service:wbem

Enumeration issue with MP-8000B running on Fabric OS 6.3.x orlowerEnumeration instance fails for the following classes:

Brocade_EthernetPortLANEndPoint, Brocade_EthernetAdminDomainHostedLanEndPoint, Brocade_EndpointOfNetworkPipe, Brocade_EthernetSwitchHostedLANEndPoint, Brocade_InEthernetLogicalNetwork, Brocade_LANEndpoint, Brocade_PlatformHostedLANEndPoint

When CMCNE manages a MP-8000B running on Fabric OS 6.3.x orlower, connected to FDMI enabled CNA.

Instance class key property with special characterGetinstance operation fails if the key property value containssemicolon or non printable character.


44

Technical notes

FC port type value for imported HBAsBrocade_topologyview.AntecedentFCPortType property valuecorresponding to the imported HBA is shown as L_port.

Server platform informationThe 1u Connectrix service processor platform is no longer available.Therefore the customer should supply their own Intel basedworkstation running Windows 2008 or Windows 7 per the processingpower requirements described in“Environment and systemrequirements” on page 11.

Operating System services such as SNMP, http, and ftp will causeconflicts with the embedded functions within CMCNE. Theseoperating system, or other third-party services, must be disabled.Note that sometimes Windows Automatic Update will installupdates for these services and, in turn, re-enable the service.Therefore, if you plan to run Windows Automatic Update it isrecommended that the Microsoft operating services for the above notbe installed.

Automatic backup deviceCMCNE has an automatic backup service that runs in thebackground. This service will backup critical CMCNE information toa drive/directory location. This service can be configured so that thebackups occur to the drive directory location of choice.

If the platform being used can contain multiple hard drives thenselecting a secondary hard drive destination would probably be themost convenient and reliable choice. Also, if the customer systemcontains two hard drives that are mirrored and then divided into twopartitions (logical drives), this will lessen the chances of data loss. Asingle hard-drive system could be partitioned into two logical drives,with the secondary partition (D:\ drive) being smaller in size; 1~ 5gig and the automatic backup could occur to the D:\ drive; however,there is no data protection in the event the hard drive were to fail.

External storage devices can also be used for a backup destination,such as a CD-RW drive, USB attached storage device, such as USBZip Drive 250 MB, or a mapped network drive.

Note: Backing up to CD-RW drive is not the recommended method. Theusable capacity of a CD is approximately 700 MB and needs to be replacedwhen full. Also, CD media has a limited number of re-writes before the


Technical notes

E

medium is exhausted and write errors occur.

It is recommended that you configure the backup system to target a harddrive or a network drive as described in the “Data Backup” section in“Application Configuration” chapter in the Connectrix Manager ConvergedNetwork Edition Professional, Professional Plus, and Enterprise Version12.1.6 User Guide.

If a CD-RW drive is chosen then the CD drive should be a CD-RWdrive and blank CD-RW UDF formatted media will need to remain inthe CD-RW drive so that the automatic backup of CMCNE data canoccur to the CD-RW disk. Note drivers and software for the CD-RWdrive must present CD-RW to the OS as an accessible storage devicefor the writing of files without the need to launch special CD-RW diskburning software. The automatic backup application just writes to theD:\ drive; it does not interface with special CD burning software.

A suitable software tool would be Nero InCD by Ahead Software.Note a regular CD-R or DVD burner is not a suitable alternativebecause the backup function needs to write to the CD-RW diskrepeatedly. Therefore, media will have to be monitored and replacedwhen it becomes full and/or if it becomes defective, with a mappednetwork drive and/or second hard drive replacing media is not anissue.

Whichever external drive type is chosen, it will need to bemounted/mapped to the platform such that the OS can utilize thedevice as a standard drive letter. Devices that require manualintervention before being written to, such as a CD-R drive, will notwork.

Note: The network drive backup is the EMC-recommended option. Toconfigure an alternate backup destination, follow the procedures in“Application Configuration” chapter in the Connectrix Manager ConvergedNetwork Edition Professional, Professional Plus, and Enterprise Version12.1.6 User Guide.

There are specific settings for the backup service that must be configuredproperly for backing up to a network drive detailed in “Data Backup” sectionin the “Application Configuration” chapter in the Connectrix ManagerConverged Network Edition Professional, Professional Plus, and EnterpriseVersion 12.1.6 User Guide.


46

Technical notes

EMC Call Home and remote supportThe Call Home feature, in conjunction with ConnectEMC, allows theConnectrix service processor to automatically call home to the EMCsupport center to report system problems. The support center Serveraccepts calls from the Connectrix service processor, logs reportedevents, and can notify one or more support center representatives.

ConnectEMC can be configured to Call Home using either a dialupconnection or by sending an email directly to the EMC Call Homecenter. It can also be configured to call home via an ESRS Gateway,utilizing either the email, ftp or https options.

You will need to purchase the EMC Multitech MT9234ZBA modem tocall home using a dialup connection. Contact your EMC salesrepresentative to order the correct modem for your country/location.No other brand/type modem can be used. You also will need toprovide a DB9 Female to DB25 Male, 9-Conductor Standard ATModem Cable, similar to BlackBox part# BC00302 for connection ofthe modem to the COM1 port on your Server platform.

Note: EMC personnel can obtain the support applications, ConnectEMC v5.xand EMCRemote Host v7.x, from EMC Online Support athttp://support.emc.com or the Connectrix Manager ConvergedNetwork Edition - Enterprise Software CD shipped with thecustomer's order.

EMC will need to install its remote support applications,ConnectEMC v5.x and EMCRemote Host v7.x on the customersupplied service processor. The EMC Multitech MT9234ZBA modemwill need to be connected to a COM port on the Server for theseapplications. Refer to the “Call Home Setup Procedure” chapter inthe Connectrix Manager Converged Network Edition Professional,Professional Plus, and Enterprise Version 12.1.6 User Guide for furtherinformation on ConnectEMC and Call Home setup procedures. Notethe EMC modem will need to be connected to a COM port and theabove software configured to utilize this modem/com port.

The COM port should have the following settings:

◆ 115,200 Bits per second

◆ 8 bits, 1 stop, No Parity

The following modem init string will need to be configured for theEMC Multitech modem:

&E1&E4&E13$R1S10=100&S0&SF1#F1&E7


Technical notes

E

The Microsoft Windows operating system will need to be configuredwith a user for EMC support personnel to log on for local and remotesupport work.

The EMC Call Home software must be installed, configured, andtested by EMC service personnel before putting the platform intooperation. The “Call Home Setup Procedure” chapter in the EMCConnectrix Manager Converged Network Edition Professional, ProfessionalPlus, and Enterprise Version 12.1.6 User Guide contains the appropriateprocedures.

Note: Modem-based call home and/or remote support is not for use whenthe CMCNE server platform is running as a Windows guest OS VM onVMWare ESX Server. ESRS Gateway would be needed for VMWare-basedCMDCE server platforms.

ESRS GatewayThe ESRS Gateway is a secure IP-based infrastructure that supports astandard remote support technology for EMC hardware and softwareproducts. It also enables customers to actively participate inmanagement of remote support, including authorization,authentication, and notification of “Dial-in” and “Connect Home”access for their installed EMC products. For more information,contact your EMC Sales Representative.

Dedicated for CMCNEThe CMCNE service processor platform must be dedicated forCMCNE and EMC's remote support applications. This platformcannot also be used for other services such as file, print, email,database, web server, etc.

Network / LAN considerationsThe customer-supplied CMCNE service processor platform mayhave one or two NICs. There are configuration options for theconnection of the management ports on the switches and themanagement platform, dependant upon the number of NICs andnetwork environment to be utilized.

The CMCNE service processor platform should be connected to amanagement LAN used by the SAN administrators to use remoteCMCNE Client installations. The customers’ network securityguidelines may dictate what type of LAN this is, but it isrecommended that it not be a generally-available, wide-open publicLAN, but rather one restricted for use by the SAN administrators.


48

Technical notes

Field experience with large data center networks that introduce newor unusual Ethernet technologies, including aggressive monitoringsystems, may be disruptive to the management services provided bythe Connectrix service processor. Careful thought and planningshould go into connecting LAN interfaces on the same networkshared by the customer-supplied service processor.

See the “Deployment best practices for public/private networks”section in the “Installation” chapter in the Connectrix ManagerConverged Network Edition Professional, Professional Plus, and EnterpriseVersion 12.1.6 User Guide for further information.

Third-party softwareGenerally speaking, anti-virus software is the most commonthird-party application requested for installation, such as Norton andMcAfee. There are no issues that prevent the use of these anti-virusapplications. However, EMC cannot guarantee any level ofperformance and/or reliability with third-party applications. If acustomer deems a certain piece of software necessary to install ontheir Server, then they can do so with the condition that it may needto be uninstalled in the event it causes conflicts with the EMCapplications. Remote control applications such as PCAnywherecannot be installed because they will directly conflict withEMCRemote. Other remote control applications, such as TerminalServices and VNC, may work, but it is recommended that they not beinstalled.

Customer assumes responsibility for support of hardware platformand software compatibility for any other applications they choose toload onto that platform.

Connectrix service processor informationThis section contains information on the Connectrix serviceprocessor.

Operating system upgradesIf a customer wants to activate Microsoft Automatic Update on theservice processor for the Microsoft Windows Operating System theycan do so; however, they should probably review which updates theywant to install for their particular environment. It is the customer's


Technical notes

EMC

responsibility to install any updates they deem necessary for theirenvironment.

IMPORTANT

CMCNE is not supported on the older original 1u Service Processorthat shipped with Windows 2000 or the newer EMC 1u serviceprocessor that shipped with Windows 2003. To run CMCNE thecustomer must supply their own platform that meets the minimumhardware requirements as published in the CMCNE 12.1.6 ReleaseNotes and User Guide.

Dedicated for CMCNE The Connectrix service processor must be dedicated for CMCNE andEMC's remote support applications designed for Connectrix serviceprocessors. This platform cannot also be used for other services suchas file, print, email, database, web server, etc.

Management network topology best practicesSee the “Deployment best practices for public/private networks”section in “Installation” chapter in the Connectrix Manager ConvergedNetwork Edition Professional, Professional Plus, and Enterprise Version12.1.6 User Guide for further information.

By default, the Connectrix service processor ships from the factorywith one network interface configured to connect to the private10.x.x.x network inside the Connectrix cabinet. There is a second NICthat can be configured and connected to a customer managementLAN. It is up to the customer's discretion to configure this secondnetwork interface as they deem appropriate to manage theConnectrix service processor and managed products. It isrecommended that this second network be as secure as possible andbe restricted to the administrators of the Connectrix products.

If FOS-based products are configured to reside on a different IPnetwork than the management LAN that remote CMCNE clientworkstations are on, then launching of the FOS-based productsmanagement tools will not work from the remote CMCNE clients.However, the FOS-based products could be configured to reside onthe same network as the remote CMCNE clients and/or the remoteCMCNE clients could be dual-homed to also have access to theswitch management LAN. It is recommended that these switchmanagement LANs be as secure as possible and be restricted to justthe SAN administrator personnel that need access.

49Connectrix Manager Converged Network Edition (CMCNE) Version 12.1.6 Release Notes

50

Documentation

Management network security considerations and third-party applicationsAs most customers are keenly aware, connecting any workstation to apublic LAN adds risk. The customer should factor in all aspects ofmanagement objectives for this Connectrix service processor versusthe risk level of the type of LAN it will be connected to. Manycustomers have various other tools they use to mitigate this risk, i.e.,restricted LANs/subnets, anti-virus software, and other systemadministrative tools. Adding third-party software to the Connectrixservice processor is not recommended; however, it is allowed underthe following conditions:

◆ Generally speaking, anti-virus software is the most commonthird-party application requested for installation; i.e., Norton andMcAfee. There are no issues that prevent the use of theseanti-virus applications. However, EMC cannot guarantee anylevel of performance, compatibility, and/or reliability withthird-party applications.

◆ If a customer deems a certain piece of software necessary toinstall on their service processor for their particular environment,they can do so with the condition that it may need to beuninstalled if it causes conflicts and incompatibilities with theEMC applications. It is the customers responsibility to maintainthis software.

Note: Remote control applications, such as PCAnywhere, cannot beinstalled because they will directly conflict with the EMC remote supportapplications.

DocumentationThe following related documentation can be found on EMC OnlineSupport at http://support.emc.com.

◆ Connectrix Manager Converged Network Edition Professional,Professional Plus, and Enterprise Version 12.1.6 User Guide

◆ Below is a link to a collection of EMC networked storage topologyTech Books and Reference Manuals.

http://www.emc.com/products/interoperability/topology-resource-center.htm


Software media, organization, and files

E

Software media, organization, and filesThe Connectrix Manager Converged Network Edition v12.1.6 isavailable in SAN only, SAN & IP, and IP only model options. See themodel table below. CMCNE-SAN-ENT, CTX MGR CNE SANEnterprise would be the equivalent to the CMCNE 11.x SANEnterprise and CMDCE 10.x SAN Enterprise versions.

SAN and the SAN and IP licenses bundles are available inProfessional Plus and Enterprise versions. The IP only managementoptions are built off and IP base starting point then incrementaldevice count or feature add-on licenses can be added to that IP basestarting point and/or upgraded with SAN upgrade licenses to enablea SAN & IP Professional Plus or Enterprise level of capabilities. Theavailable Professional, Professional Plus, and Enterprise packagesand capabilities are listed in the following two tables.

Package Versions

SAN with SMI Agent +IP Licensed Version—Enterprise• SAN—Support for 36 fabrics, 10,000 devices, and 9,000

switch ports• IP—Support for 5,050 devices, 252,500 ports, and 100

MPLS devices

Professional• SAN—Support for 1 fabric and 1,000 switch ports• IP—Support for 20 devices and 1,000 ports

Note: SMI Agent is not supported on Professional.

SAN with SMI Agent Licensed Version—Enterprise• SAN—Support for 36 fabrics, 10,000 devices, and 9,000switch ports

Licensed Version—Professional Plus• SAN—Support for 36 fabrics, 4,096 devices, and ,2560

switch ports

Professional• SAN—Support for 1 fabric and 1,000 ports

Note: SMI Agent is not supported on Professional.


52


CMCNE v12.1.6 is available for download fromhttp://support.emc.com. If a physical software media kit is required,it can be ordered via the following model:

CMCNE-SW-KIT CMCNE Software Media Kit - No License

IP Licensed Version—Enterprise• IP—Support for 5,050 devices, 252,500 ports, and 100

MPLS devices

Professional• IP—Support for 20 devices and 1,000 ports

SMI Agent only N/A

Package Versions

Model Description Notes

SAN Only Models SAN only models mirror the previous generation11.x model options.

CMCNE-SAN-ENT CTX MGR CNE SAN Enterprise Most like the CMCNE 11.X SAN Enterprise.SAN management SW license for up to 9000 switchports (~120 devices) and 36 fabrics

CMCNE-SAN-PLU CTX MGR CNE SAN Pro Plus Most like the CMCNE 11.X Professional PlusSAN management SW license for up to 2,560 switchports (~40 devices) and 36 fabrics

CNESANPLUSUPG CTX MGR CNE SAN Pro Plus to ENT UPG LIC Upgrades Pro Plus SAN to Enterprise SAN

Add IP to SAN Add IP Base capabilities to SAN Only install

CNE-SAN-IP150 CTX MGR CNE SAN ADD IP BASE LIC Adds base IP management capabilities to a SAN onlylic.Must install this lic first to a SAN only install beforeadding any incremental IP Add-Ons

SAN & IP Bundles

CNE-SANIP-ENT CTX MGR CNE SAN-IP Enterprise IP and SAN management SW license for 550 IPdevices, Advanced IP capabilities, 9000 SAN switchports (~120 devices), and 36 SAN fabrics

CNE-SANIP-PLU CTX MGR CNE SAN-IP Pro Plus IP and SAN management SW license for 150 IPdevices, Advanced IP capabilities,2560 SAN switch ports

CNE-SANIPUPLS CTX MGR CNE - Plus SAN-IP to ENT UPG LIC Upgrade SAN & IP ProPlus to SAN & IP Enterprise

IP Only Models Base IP Models for base IP functionality



E

The CMCNE v12.1.6 installer package can be downloaded bylicensed Connectrix Manager users at the following location:

EMC Online Support at http://support.emc.com.

No license is required for the Professional version; however a licenseis required for the Professional Plus or Enterprise version which canbe obtained by ordering the models listed above.

CNE-IPB-50 CTX MGR CNE IP BASE Base starting point for IP only management license forup to 50 devices,No Advanced IP functions. Cannot add SANcapabilities to this license. Must first AddCNE-IPADV100 in order to have Adv IP and/or addSAN functions.

IP Upgrades Incremental IP Add-Ons to IP Bases

CNE-IPADV100 CTX MGR CNE - ADD IP DATA CTR TO IPBASE

Adds IP Data Center Management for 1 VCS Fabric toan IP Base. Add one for each VCS.

CNE-IPU100 CTX MGR CNE - ADD 100 IP DEV UPG LIC Adds IP management SW license for 100 devices




CNE-MPLS10 CTX MGR CNE - ADD 10 MPLS IP DEV UPGLIC

Adds MPLS management for up to 10 devices





IP-to-SAN Upgrades Add SAN functionality to IP Base

CNE-IPUSANENT CTX MGR CNE - IP ADD SAN ENT UPG LIC Adds SAN Enterprise management for 9000 switchports (~120 devices) and 36 fabrics to IP onlymanagement. Must have already addedCNE-IPADV100 to an IP Base first.

CNE-IPUSANPLU CTX MGR CNE - IP ADD SAN PLUS UPG LIC Adds SAN ProPlus management for 9000 switch ports(~120 devices) and 36 fabrics to IP management. Musthave already added CNE-IPADV100 to an IP Basefirst.

CNE-IPSANPLUE CTX MGR CNE - IP ADD ENT TO PLUS LIC Upgrades SAN and IP install from ProPlus SAN levelto SAN Enterprise level. Must have previously installedCNE-IPUSANPLU

Model Description Notes


54

Installation

It is possible to run the CMCNE Enterprise version under a 75 daytrial license; however this should only be done for short termevaluation purposes. After 75 days you will not be able to log in witha CMCNE client; therefore production environments are onlysupported if fully licensed.

Note: In CMCNE 12.x.x, 75-day Trial versions (for both full install andmigration) are only available for the Enterprise Edition. Professional PlusEdition is no longer available for 75-day Trials.

EMC customers upgrading from Connectrix Manager or FabricManager who's current software installations are covered by a validEMC Software Support contract can obtain an upgrade license bycontacting the EMC Software Refresh Group at one of the followingnumbers:

◆ United States: 800 782-4362 (SVC-4EMC)◆ Canada:800 543-4782 (543-4SVC)◆ Worldwide:+1.508.497.7901

For after hours emergency assistance, contact the EMC SupportCenter at the numbers above, and select Option 2.

InstallationThis section contains installation and upgrade and downgradeconsiderations.

For more detailed information, refer to the "Installation" chapter inthe Connectrix Manager Converged Network Edition Professional,Professional Plus, and Enterprise Version 12.1.6 User Guide.

Installing CMCNE

IMPORTANT

Thoroughly review the installation and migration instructionsbefore beginning the installation process.

For detailed instructions for new installations refer to the"Installation" chapter in the Connectrix Manager Converged NetworkEdition Professional, Professional Plus, and Enterprise Version 12.1.6 UserGuide.


Installation

E

Migrating from a previous version◆ Upgrades to CMCNE v12.1.6 will only be allowed from CMCNE

11.2.1, 12.0.1, 12.0.3, 12.1.2 and 12.1.5. For more information, referto the "Migration and Transition" section of the ConnectrixManager Converged Network Edition Professional, Professional Plus,and Enterprise Version 12.1.6 User Guide.

◆ You cannot migrate directly from CMCNE 11.1.x to CMCNE12.1.6. You must first migrate to CMCNE 11.2.1 before migratingto CMCNE 12.1.6. To migrate from CMCNE 11.1.x to CMCNE11.2.1, refer to the EMC Connectrix Manager Converged NetworkEdition Professional, Professional Plus and Enterprise Version 11.2.1User Guide available on EMC Online Support.

◆ You cannot migrate directly from CMDCE 10.4.x to CMCNEv12.1.6. CMDCE 10.4.x users must first migrate to CMCNE 11.1.x,then migrate CMCNE 12.0.x, before migrating to CMCNE v12.1.6.To migrate from CMDCE 10.4.x to CMCNE 11.1.x, refer to the"Migration and Transition" section of the EMC Connectrix ManagerConverged Network Edition Professional, Professional Plus andEnterprise Version 11.1.4 User Guide.

Note: Although migrating to CMCNE 11.1.1 is supported, EMCrecommends using CMCNE 11.1.4 as the intermediate step whenmigrating from CMDCE 10.4.x to CMCNE 12.1.6 Using CMCNE 11.2.1 asthe intermediate step when migrating from CMDCE 10.4.x to CMCNE12.0.x is NOT supported.

◆ You cannot migrate directly from CMDCE 10.1.X or 10.3.X toCMCNE 12.1.6. CMDCE 10.1.X and 10.3.X users must firstmigrate to CMDCE 10.4.5, then migrate to CMCNE 11.1.x, thenmigrate to CMCNE 11.2.1 or CMCNE 12.0.x, before migrating toCMCNE 12.1.6. To migrate from CMDCE 10.1.X or 10.3.X toCMDCE 10.4.5, refer to the "Migration and Transition" section ofthe EMC Connectrix Manager Data Center Edition Professional,Professional Plus and Enterprise Version 10.4.5 User Guide.

◆ Connectrix Manager 9.6.x/9.7.x and Fabric Manager 5.4 / 5.5users must first migrate to CMDCE 10.3.4, then migrate toCMDCE 10.4.5, then migrate to CMCNE 11.1.x, then migrate to CMCNE 11.2.1 or CMCNE 12.0.x, before migrating to CMCNE12.1.6. To migrate from CM 9.x or Fabric Manager to CMDCE


56

Installation

10.3.4 and 10.4.5, refer to the EMC Connectrix Manager Data CenterEdition Professional, Professional Plus and Enterprise Version 10.4.5User Guide.

◆ To migrate from CMDCE 10.4.5 to CMCNE 11.1.x, refer to the"Migration and Transition" section of the EMC Connectrix ManagerConverged Network Edition Professional, Professional Plus andEnterprise Version 11.1.4 User Guide.

Note: Although migrating to CMCNE 11.1.1 is supported, EMCrecommends using CMCNE 11.1.4 as the intermediate step whenmigrating from CMDCE 10.4.x to CMCNE 12.0.x. Using CMCNE 11.2.1as the intermediate step when migrating from CMDCE 10.4.x to CMCNE12.0.x is NOT supported.

◆ Customers running CMDCE 10.x.x, who have a validmaintenance contract, can migrate to the CMCNE 11.1.x “SANwith SMI Agent" package, then migrate to CMCNE 11.2.1 "SANwith SMI Agent" package, and then migrate to the CMCNE 12.1.6“SAN with SMI Agent" package at no additional charge.Migrating to the CMCNE 12.1.6 "SAN with SMI Agent + IP"package requires a new license at an additional charge. For moreinformation, please contact your local EMC Representative.

◆ A customer's existing CMDCE 10.x or CMCNE 11.x EnterpriseEdition license can be used to install the CMCNE 12.1.6Enterprise Edition “SAN with SMI Agent” package or to upgradea CMCNE 12.1.6 Enterprise Trial “SAN with SMI Agent” packageto CMCNE 12.1.6 Enterprise Edition “SAN with SMI Agent”package.

◆ A customer's existing CMDCE 10.x or CMCNE 11.x ProfessionalPlus Edition license can be used to install the CMCNE 12.1.6Professional Plus Edition “SAN with SMI Agent” package.

In v12.1.6, 75-day Trial versions (for both full install andmigration) are only for Enterprise Edition. Professional PlusEdition is no longer supported for 75-day Trials. Therefore, acustomer's existing CMDCE 10.x or CMCNE 11.x ProfessionalPlus Edition license can only be used to change a CMCNE 12.1.6Enterprise Trial” SAN with SMI Agent” package to CMCNE12.1.6. Professional Plus Edition “SAN with SMI Agent” package.

◆ Network path migrations from CMCNE 11.2.1 on one server toCMCNE 12.1.6 on another are not supported and requireadditional steps to complete a successful migration. This includes


Installation

E

a 32-bit Windows server to a 64-bit Windows server, a 32-bitWindows server to a 32-bit Windows server, or a 64-bit Windowsserver to a 64-bit Windows server. For more information on thesupported migration path, refer to the "Pre-migrationrequirements" section in the "Migration and Transition" chapter ofthe EMC Connectrix Manager Converged Network EditionProfessional, Professional Plus and Enterprise Version 12.1.6 UserGuide.

◆ Network path migrations from CMCNE 12.0.x on one server toCMCNE 12.1.6 on another are not supported and require abackup and restore process to complete a successful migration.This includes a 32-bit Windows server to a 64-bit Windows server,a 32-bit Windows server to a 32-bit Windows server, or a 64-bitWindows server to a 64-bit Windows server. For moreinformation on the supported migration path, refer to the"Pre-migration requirements" section in the "Migration andTransition" chapter of the EMC Connectrix Manager ConvergedNetwork Edition Professional, Professional Plus and Enterprise Version12.1.6 User Guide.

Note: Migrating from Brocade's version (DCFM) to EMC's version (CMCNE) is not supported.

Note: Migrating from Brocade's version (BNA) to EMC's version (CMCNE) is not supported.

◆ All of the user guides referenced in this section can be found onEMC Online Support at http://support.emc.com.

Launching the CMCNE Client◆ To launch the CMCNE Client on the same local machine as the

CMCNE Server, launch the client as follows:

Windows: Select Start > Programs > CMCNE 12.1.6 > CMCNE12.1.6.

Windows:

◆ Client can be launched via Desktop icon.

Launch command prompt and go to the location C:\ProgramFiles\CMCNE 12.1.6\bin “and type” “dcmclient”.


58

Installation

Follow the steps below on launching the client from a web browser.

◆ To launch the CMCNE Client from a remote host, launch theclient as follows:

Open a browser window and type the CMCNE server hostnameor IP address in the Address field; for example:

http: //CMCNEserverhost1.companyname.com/http: //192.x.y.z/

◆ If when the CMCNE server was installed, a CMCNE web serverport number was specified (instead of the default 80), you mustspecify the port number after the hostname or IP address. In thefollowing examples, 8080 is the web server port number:

http: //CMCNEserverhost1.companyname.com: 8080/http: //192.x.y.z: 8080/

Note: Launching element manager applications within CMCNE Client isdone using Java Web Start technology. This requires the local system’s webbrowser to be able to run Java web start applications. This setting may havebeen turned off in the wake of recent Java zero-day vulnerabilities.

To turn on Java content in the browser, please follow the below steps:

1. Launch “Java Control Panel” (refer tohttp://java.com/en/download/help/win_controlpanel.xmlto locate Java Control Panel application on Windows).

2. In the Java Control Panel, click on the Security tab.

3. Select the check box for Enable Java content in the browser.This will enable the Java plug-in in the browser.

4. Click Apply. When the Windows User Account Control (UAC)dialog appears, allow permissions to make the changes. ClickOK in the Java Plug-in confirmation window.

5. Now launch Element Manager from CMCNE client.

Note: On a Windows server, if only ‘Administrators’ have access to a drive,windows does not allow Postgres to create some required directories and aresult, migration from a previous version of CMCNE to a newer supportedversion fails.

The following steps need to be followed to resolve the issue:


Installation

E

1. Make sure that the previous version of CMCNE is up andrunning.

2. Right click on the drive where the new version of CMCNE isintended to be installed (E.g. :D).

3. Navigate to the Security tab -> Edit -> Add.

4. Add “Authenticated Users” and give full permission, clickOk.

5. Now install the new version of CMCNE and start themigration progress.

Installation notesFor complete installation information, or if you are upgrading fromthe professional or enterprise trial versions of CMCNE, refer to the“Installation” and “Migration and Transition” chapters in theConnectrix Manager Converged Network Edition Professional, ProfessionalPlus, and Enterprise Version 12.1.6 User Guide.

◆ Ensure the network environment does not have any firewallinstallations between the client and the server and the switches. Ifone exists, ensure that proper rules are set up to allow access.

◆ You must choose the SAN size during the installation of CMCNEEnterprise v12.1.6.

◆ If you install CMCNE Server on a Windows host that hasanti-virus software, you must disable the anti-virus softwareduring the installation.

◆ Install CMCNE Server on a dedicated machine that is not runningany other server applications, such as another database server.

◆ CMCNE is supported under Windows 7, Windows 8, Windows2008 or Windows 2012 guest operating systems that run underVMWare ESXi 5.1. Other virtualization software is not supported.

◆ Modem-based Call Home is not supported under Windows guestoperating system that runs under ESXi 5.1.

◆ CMCNE v12.1.6 is tested under English only. All other foreignlanguages are not supported.

◆ CMCNE cannot run on the same host as Connectrix Manager,Connectrix Manager Data Center Edition or Fabric Manager,when actively monitoring fabrics.


60

Troubleshooting and getting help

◆ Fabrics running with SecureFOS enabled are not supported andare not discoverable in CMCNE.

◆ If you are upgrading from the professional or enterprise trialversions of CMCNE, refer to “Installation” and “Migration andTransition” chapters in the Connectrix Manager Converged NetworkEdition Professional, Professional Plus, and Enterprise Version 12.1.6User Guide.

Troubleshooting and getting helpEMC support, product, and licensing information can be obtained asfollows.

Product information — For documentation, release notes, softwareupdates, or for information about EMC products and services, go tothe EMC Online Support website (registration required) at:

http://support.emc.com

For EMC product licensing, go to the EMC Online Support website (registration required) at:


Then select Support > Service Center > Get and Manage Licenses >Connectrix.

Technical support — For technical support, go to the Service Centeron EMC Online Support at


To open a service request you must have a valid support agreement.Please contact your EMC sales representative for details aboutobtaining a valid support agreement or to answer any questionsabout your account.


Troubleshooting and getting help

E

Copyright © 2014 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information issubject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION INTHIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation inthe United State and other countries. All other trademarks used herein are the property of theirrespective owners.

For the most up-to-date regulator document for your product line, go to EMC Online Support (https://support.emc.com).


Documents

Docu54667 Connectrix Manager Converged Network Edition 12.1.6 Release Notes