Docu54667 Connectrix Manager Converged Network Edition 12.1.6 Release Notes

1
These release notes contain new features, code enhancements, and fixes
in 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
Manager
Converged Network Edition
Version 12.1.6
Release Notes
P/N 302-000-471
Rev 03
July 28, 2014
2 EMC Connectrix Manager Converged Network Edition (CMCNE) Version 12.1.6 Release Notes
Product description
Product description
Connectrix Manager Converged Network Edition (CMCNE) greatly
simplifies daily operations while improving the performance and
reliability of the overall SAN and IP networking environment.
CMCNE unifies under a single platform, full lifecycle network
management for SAN, LAN and converged networks. CMCNE
provides a consistent user experience, across the entire Connectrix
B-series portfolio of products. This network management tool offers
flexible and proactive SAN/IP network performance analysis in
addition to IP network configuration change deployment and
monitoring for compliance. CMCNE supports Fibre Channel SANs,
including 16 Gbps platforms and Layer 2/3 IP networks.
CMCNE can reduce operation expenditures and help organizations
focus on strategic IT initiatives by providing a common network
management tool for provisioning, monitoring, reporting and
troubleshooting. CMCNE provides customizable health and
performance dashboards, with an easy-to-use graphical user interface
and comprehensive features that automate repetitive tasks. With
CMCNE, storage and network administrators can proactively
manage their SAN/IP network environments to support non-stop
networking. CMCNE also provides network administrators the
ability to quickly access network topology, health and performance
data required to troubleshoot and remediate network issues.
Connectrix Manager Converged Network Edition (CMCNE) v12.1.6
is the next major release of Connectrix Manager B-Series switch
management software. Revision 12.1.x of CMCNE introduces several
IP and SAN FC enhancements as well as dashboard improvements.
CMCNE v12.1.6 is available in several versions which can be broken
down in three major categories; SAN only management, SAN & IP
management, and IP only management capabilities. There are license
options to enable some, all, and/or upgrade functionality from one
category to another.
The CMCNE v12.1.6 SAN Management options are structured the
same as the previous CMCNE 11.x versions.
CMCNE SAN Professional Edition Intended for the
management of smaller fabrics with Connectrix B Series
departmental switches.
3
Product description
EMC Connectrix Manager Converged Network Edition (CMCNE) Version 12.1.6 Release Notes
CMCNE SAN Professional Plus Edition is a Professional Plus
edition which is in between Professional and Enterprise for
scalability support and also supports the ED-DCX-4S-B and
ED-DCX8510-4B.
CMCNE SAN Enterprise Edition A full-featured Enterprise
class management solution for the largest of data center SAN
infrastructures.
The three flavors differ predominantly in the set of supported
features, hardware platforms, and supported scalability limits.
In addition to managing mixed fabrics, Connectrix Manager
Converged Network Edition for SAN Professional Plus and SAN
Enterprise have other features not found in Connectrix Manager
Converged Network Edition for SAN Professional, as detailed in the
following tables.
(a) Limited support
(b) Basic Layer 2 configuration
Hardware Platform
CMCNE for SAN
Professional
CMCNE for SAN
Professional Plus
CMCNE 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-16EB
Encryption Blade

MP-8000B Switch & PB-DCX-24FCOE Blade
MP-7800B FCiP Switch & PB-DCX-FX8-24 Blade
DS-6505B, DS-6510B, & DS-6520B
Product description
(a) Support for Role-Based Access Control (RBAC) and security schemes (RADIUS, LDAP, Active
Directory, NIS/NIS+, and more)
(b) Data persistence for up to two years of data, out-of-box Open Database Connectivity (ODBC), and
Java Database Connectivity (JDBC) access
Feature
CMCNE for SAN
Professional
CMCNE 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
5
Product description
CMCNE SAN Professional Edition
CMCNE Professional showcases a subset of features and hardware
platforms of CMCNE Enterprise. The Professional version, which is a
no charge version, is intended for the management of smaller fabrics
with Connectrix B Series departmental switches. It cannot manage
Director class products, has no FICON or routing support, and does
not have remote clients or Call home support. The Professional
version is limited to managing FOS departmental switch products
only consisting of 1 fabric, 10 switches, 640 switch ports, and 1,000
hosts or storage devices. CMCNE Professional presents several new
benefits to both new customers and existing Web Tools (FOS Switch
Element Manager) customers including (but not limited to):
A topology view that provides a comprehensive fabric
connectivity map.
Out-of-box database persistence for key information including
zoning changes, switch configuration backups, audit of changes
made to the environment, etc.
The ability to perform group configuration activities across
multiple switches simultaneously (e.g., download firmware to
multiple switches simultaneously to meet aggressive change
windows, schedule backup of switch configurations into the
CMCNE repository on an automated basis to enable rapid
troubleshooting and switch provisioning, replicate switch
configuration from one "golden" switch to multiple other
switches to maintain configuration consistency across the
enterprise, etc.).
CMCNE SAN Professional Plus Edition
CMCNE Professional Plus is designed for medium-sized businesses
or departmental storage networks. Very similar in functionality to the
Enterprise version but limited in features/scalability by a license key
to:
Support up to 36 fabrics and 2560 switch ports
Support the ED-DCX-4S-B, ED-DCX8510-4B, encryption
products, extension products, and Brocade HBA/CNAs
Can be updated to CMCNE SAN Enterprise (via a license key
update).
Product description
CMCNE SAN Enterprise Edition
CMCNE Enterprise builds on top of the functionality available with
CMCNE Professional, and provides a comprehensive fabric
management framework for the end-to-end management of the data
center fabric. CMCNE Enterprise can scale to manage up to 9,000
switch ports and also contains several new features to support not
only the new 16 Gb Director and switch products but some new
features available in FOS v7.2.0x as outlined in New features and
changes on page 8.
CMCNE SAN Enterprise is the full featured SAN management
package that supports all enterprise-class products/technologies
including 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 fromCMCNE 11.2.1
and 12.x.x. For more information, refer to the "Migration and
Transition" section of the Connectrix Manager Converged Network
Edition Professional, Professional Plus, and Enterprise Version 12.1.6 User
Guide.
CMCNE 11.1.x users must first migrate to CMCNE 11.2.1 before
migrating to CMCNE 12.1.6. To migrate from CMCNE 11.1.x to
CMCNE 11.2.1, refer to the EMC Connectrix Manager Converged
Network Edition Professional, Professional Plus and Enterprise Version
11.2.1 User Guide available on EMC Online Support.
CMDCE 10.4.x users must first migrate to CMCNE 11.1.x, then
migrate to CMCNE 11.2.1 or CMCNE 12.0.x, before migrating to
CMCNE 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 Connectrix
Manager Converged Network Edition Professional, Professional Plus and
Enterprise Version 11.1.4 User Guide.
Note: Although migrating to CMCNE 11.1.1 is supported, EMC recommends
using CMCNE 11.1.4 as the intermediate step when migrating from CMDCE
10.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 or
CMCNE 12.0.x, before migrating to CMCNE 12.1.6. To migrate from
CMDCE 10.1.x or 10.3.x to CMDCE 10.4.5, refer to the "Migration and
7
Product description
Transition" section of the EMC Connectrix Manager Data Center Edition
Professional, 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 do
not require a new software license key.
Note: Although migrating to CMCNE 11.1.1 is supported, EMC recommends
using CMCNE 11.1.4 as the intermediate step when migrating from CMDCE
10.4.x to CMCNE 12.0.x.
Connectrix Manager 9.6.x/9.7.x and Fabric Manager 5.4 / 5.5 users
must 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 or
CMCNE 12.0.x before migrating to CMCNE 12.1.6. To migrate from
CM 9.x or Fabric Manager to CMDCE 10.3.4 and 10.4.5, refer to the
EMC Connectrix Manager Data Center Edition Professional, Professional
Plus 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 Manager
Converged Network Edition Professional, Professional Plus and Enterprise
Version 11.1.4 User Guide. Although migrating to CMCNE 11.1.1 is
supported, EMC recommends using CMCNE 11.1.4 as the
intermediate step when migrating from CMDCE 10.4.x to CMCNE
12.0.x.
All of the user guides referenced in this section can be found on EMC
Online Support at http://support.emc.com.
CMCNE SAN and IP and IP only options
CMCNE is also available in similarly scaled SAN & IP bundled
versions as the SANversions above and in IP only versions that allow
incrementally scaling the number of IP switches that can be managed
from 50 to 5050 IP switches. Refer to the table of available license
options in the Software media, organization, and files on page 51.
Switch platform support
For the list of supported platforms, refer to Switch platform and
firmware requirements on page 25.
New features and changes
New features and changes
This section lists new features and changes in this release.
Important updates
Connectrix Manager Converged Network Edition (CMCNE) 12.1.6 is
a maintenance release based on CMCNE 12.1.5. All hardware
platforms and features supported in CMCNE 12.1.5 are also
supported in 12.1.6.
Note: CMCNE Professional Plus and Enterprise Editions are only supported
on 64-bit Windows operating systems. CMCNE Professional Edition is
supported on 32-bit and 64-bit Windows operating systems.
Note: CMCNE 12.1.6 does not support EOS fabrics.
New hardware
There are no new hardware features with this release.
New software features
There are no new software features with this release.
Fixed problems
This section contains code enhancements and fixes for CMCNE
v12.1.6. When a workaround to an issues is available, it is provided.
This section contains fixed problems for the following version of
CMCNE:
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: High
Summary: SNMP Traps are not received after Network Advisor server is restarted.
Symptom: Master log does not display SNMP traps.
Risk of Fix: Medium Probability: High
Feature: UNDETERMINED Function: UNDER REVIEW
Reported In Release: Network Advisor12.1.1 Service Request ID: 1275040
9
Fixed problems
Summary: 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: High
Feature: ZONING Function: USABILITY
Reported In Release: Network Advisor12.1.4
Summary: 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: Medium
Feature: DISCOVERY Function: SAN Switch Discovery
Reported In Release: Network Advisor12.1.4 Service Request ID: 1281454
Defect ID: DEFECT000477274
Technical Severity: High Probability: Medium
Product: Network Advisor Technology: Partner Integration
Reported In Release: Network Advisor12.1.2 Technology Area: SMI Agent
Symptom: 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.
Technical Severity: High Probability: High
Product: Network Advisor Technology: Application Management
Reported In Release: Network Advisor12.0.4 Technology Area: Installation & Migration
Symptom: 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
Technical Severity: High Probability: High
Symptom: Incorrect number of instances are returned for a Meta SAN for the class Brocade_SANInFabric
Condition: Issue is seen for the class Brocade_SANInFabric
Technical Severity: Medium Probability: Medium
Symptom: User cannot view all the instances of NPIV CIM_ActiveConnection
Condition: This issue occurs with NPIV connections
Fixed problems
Symptom: 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.
Technical Severity: High
Reported In Release: Network Advisor12.0.2 Technology Area:
SMI Agent
Symptom: 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.
Technical Severity: High
Symptom: User is unable to delete LSAN zones using the SMI Agent.
Condition: Occurs only when using SMI Agent to delete LSAN zones
Product: Network Advisor Technology: Application Management
Reported In Release: Network Advisor12.1.6 Technology Area: Server Properties
Symptom: 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.
11
Environment and system requirements
There are very important scalability limits for the Enterprise version
by type and size of the SANs to be managed by CMCNE v12.1.6. The
scalability limits are broken into three categories by size of the
environment to be managed: small, medium and large, as detailed in
Table 1, which summarizes the scalability limits for support.
Note: CMCNE Professional Plus and Enterprise Editions are only supported
on 64-bit Windows operating systems. CMCNE Professional Edition is
supported on 32-bit and 64-bit Windows operating systems
a. The physical N_Port count is limited by the maximum number of switch ports
allowed. Any additional N_Ports above the maximum number of switch ports
would have to be virtual devices.
b. Performance Monitoring Polling is the interval at which the performance data is
queried from the managed elements when the historical data collection is
turned on.
Table 2 summarizes the scalability limits for support with CMCNE.
Table 1 Enterprise supported limits by SAN size
Small Medium Large
Number of Fabrics 8 16 36
Number of Switches and Access Gateways 40 90 200
Number of Switch Ports 2000 5000 9000
Number of Physical/Virtual N_Ports
a
5000 10000 20000
PM 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
a
4096
PM Polling
b
5 min
turned on.
Table 3 summarizes the scalability limits for support with CMCNE.
turned on.
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
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
13
Table 6 summarizes the enterprise supported limits by SAN size for
SMI Agent only.
In conjunction with the SAN size scalability limits above the
computing power of the service processor platform to be used for the
CMCNE v12.1.6 server installation needs to be factored in. These are
also categorized by size of the SAN to be managed, as shown in
Table 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 Access
Gateways
40 90 200
Number of Switch Parts 2000 5000 9000
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
2008 R2 Data Center Edition
a
2008 R2 Standard Edition
a
2008 R2 Enterprise Edition
a
b
b
8 Enterprise
b
7 Enterprise
c
SAN with SMI Agent
IP only
SMI Agent only
SAN with SMI Agent + IP
a. EMCRemote 7.02.02 or higher is required to enable the remote support
capability on this 64-bit operating system.
b. EMCRemote 7.10.02 or higher and ConnectEMC 5.04.16 or higher are required
to enable the remote support and call home capabilities on this 64-bit operating
system.
c. EMCRemote 7.08.04 or higher is required to enable the remote support
capability 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 physical
CPU.
Note: The Windows-based server platform will also require one 9-pin serial
port for connection of the EMC modem. For more information, refer to Call
Home Setup Procedure chapter in the Connectrix Manager Converged
Network Edition Professional, Professional Plus, and Enterprise Version
12.1.6 User Guide.
VMware - Virtual Machines of the above 32-bit OS
running VMWares 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 OS
running VMWares OS:
ESX Server i 5.1
d, e
SAN with SMI Agent
IP only
SMI Agent only
SAN with SMI Agent + IP
Table 7 Operating System requirements for Server/Local client (page 2 of 2)
Operating system Supported packages
15
Operating system requirements for Remote client
Table 8 summarizes the minimum recommended operating system
requirements for running the CMCNE Remote client application.
Host requirements
Table 9 through Table 11 summarize the minimum required host
requirements for running CMCNE SAN with SMI Agent + IP on
Windows systems.
Table 12 summarizes the minimum required host requirements for
running CMCNE SAN with SMI Agent on Windows systems.
running CMCNE IP on Windows systems.
Table 8 Operating system requirements for Remote client
Operating systems
2008 Server
7 Enterprise
2008 R2 Enterprise Edition
8 Enterprise
7 Enterprise
Linux
RedHat Enterprise 6.1 Advanced Platform (x86 32-bit/64-bit)
SuSE Enterprise Server 11 (x86 32-bit)
Oracle Enterprise 6.1 (x86 32-bit/64-bit)
VMware - Virtual Machines of the above OS running VMWares OS:
ESX Server i 5.1
running 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 or
equivalent
Intel Core2 duo 2GHz or
equivalent
Remote client only N/A Intel Core2 duo 2GHz or
equivalent
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 or
equivalent
Intel Dual CPU Core2 duo
2.4 GHz or equivalent
Medium SAN Enterprise Intel Dual CPU Core2 duo
Intel quad dual core or dual
quad core, 2.4 GHz or
equivalent
Large SAN Enterprise Intel Dual CPU Core2 duo
Intel quad dual core or dual
quad core, 2.4 GHz or
equivalent
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 or
equivalent
Medium SAN Enterprise Intel Dual CPU Core2 duo
Large SAN Enterprise Intel Dual CPU Core2 duo
17
Table 12 SAN with SMI Agent host requirements
Professional Professional Plus
Enterprise
Small Medium Large LAN
Server plus one local client Intel Core2 duo
2GHz or
equivalent
Intel Core2 duo
2GHz or equivalent
Intel Core2 duo
2GHz or
equivalent
Intel Dual CPU
Core2 duo 2.4
GHz
or equivalent
Intel Dual CPU
Core2 duo 2.4 GHz
or equivalent
Remote client only N/A Intel Core2 duo
2GHz or equivalent
Intel Core2 duo
2GHz or
equivalent
Intel Core2
duo 2GHz or
equivalent
Intel Core2 duo
2GHz or equivalent
Table 13 IP only host requirements
Professional
Enterprise
Small Medium Large
2GHz or equivalent
Intel Core2 duo
2GHz or equivalent
Intel Dual CPU
Core2 duo 2.4
GHz
or equivalent
Intel Dual CPU
Core2 duo 2.4 GHz
or equivalent
Remote client only N/A Intel Core2 duo2GHz
or equivalent
Intel Core2 duo
2GHz or
equivalent
Intel Core2 duo
2GHz or equivalent
Table 14 SMI Agent only host requirements
Enterprise
Small Medium Large
2GHz or equivalent
Intel Dual CPU
Core2 duo 2.4 GHz
or equivalent
Intel Dual CPU
Core2 duo 2.4 GHz
or equivalent
Remote client only Intel Core2 duo
2GHz or equivalent
Intel Core2 duo 2GHz
or equivalent
Intel Core2 duo
2GHz or equivalent
Memory requirements
Table 15 through Table 20 on page 19 summarize the minimum
required system memory requirements for running CMCNE SAN
with SMI Agent + IP on Windows.
Note: These requirements are only applicable when no other applications are
running 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 are
only 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 server
plus 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)
19
Table 17 SAN with SMI Agent + IP (Enterprise) memory requirements for remote
client
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
8 GB (64-bit)
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
8 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
Table 20 SMI Agent only memory requirement
Server/Client
Enterprise
Small Medium Large
Server plus 1 local client 4 GB 4 GB 4 GB
Remote client only 4 GB 4 GB 4 GB
Operating system cache requirements
It is recommended that you use the System managed size (the OS
allocates the required cache); however, if you choose to use a custom
size, make sure you use the following memory settings for your
operating system listed in Table 21.
Disk space requirements
Disk space requirements
Table 22 through Table 24 on page 21 summarize the minimum
required disk space requirements for running CMCNE SAN with
SMI Agent + IP on Windows.
Note: It is recommended that you add an additional 100 GB of disk space if
you use sFlow.
Note: It is recommended that you add an additional 40 GB of disk space for
the default temporary directory.
Table 21 Virtual memory requirements
Installed physical
memory (RAM)
size
Windows Server 2008 and Windows 7 Professional
Minimum paging
file size
Maximum paging
file 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
21
Table 25 summarizes the minimum required disk space requirements
for running CMCNE SAN with SMI Agent on Windows.
Table 23 SAN with SMI Agent + IP (Enterprise) disk space requirements for server
plus 1 local client
Table 24 SAN with SMI Agent + IP (Enterprise) disk space requirements for
remote client
Table 25 SAN with SMI Agent disk space requirements
Server/Client Professional
Professional
Plus
Enterprise
Small 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
for running CMCNE IP on Windows.
for running SMI Agent only on Windows.
Note: If you enable periodic supportSave or configure the CMCNE server as
the Upload Failure Data Capture location for monitored switches, then
additional disc space will be required. Each switch supportSave files is
approximately 5 MB and each Upload Failure Data Capture file is
approximately 500 KB. To determine the disc space requirements, multiply
the frequency of scheduled supportSave files by 5 MB and the expected
Upload Failure Data Capture files by 500 KB, before the planned periodic
purge 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 NAT
Server.
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 Plus
Enterprise
Small 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/Client
Enterprise
Small Medium Large
Server plus 1 local client 20 GB 40 GB 60 GB
Remote client only 1 GB 1 GB 1 GB
23
In Professional Plus and Enterprise editions, a single server
supports a maximum of 25 clients, which can be local or remote
on 64-bit servers. To support more than 8 clients, you must make
the following changes to your configuration:
Increase the server memory size to 3 GB. You can configure the
server memory size from the Options dialog box, Memory
Allocations pane.
Increase the PostgreSQL database shared buffers memory
allocation to 1024 MB by editing the Install_
Home\data\databases\postgresql.conf file. See step 7 on
page 34 for more details.
Browser requirements
The launch of CMCNE and the launch of Element Manager (Web
Tools) from the application is supported from the following browsers
with 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 above
combinations.
Note: JRE 1.7_55 is not bundled with CMCNE 12.1.6, but can be used for
remote clients.
For the website listing patch information, go to
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Technical notes
Virtual Machine management
Table 28 lists the VMware vCenter, ESX and ESXi versions supported
by the Management module within CMCNE. The Management
module discovers the data from vCenter, ESX and ESXi servers.
Technical notes
This section contains the following information:
Switch platform and firmware requirements on page 25
Virtual Connect Enterprise Manager (VCEM) server discovery
requirements on page 28
Important notes on page 29
Performance Statistics Counters - Calculation Formulae on
page 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
25
Technical notes
Switch platform and firmware requirements
The following table lists the supported EMC Connectrix Director and
Switch products and supported firmware versions for use with
CMCNE.
Operating system Switch/Director
Switch type (B-Model) firmware versions
FOS 6.4.2a or higher DS-4100B
MP-7500B
DS-4900B
DS-5000B
AP-7600B
DS-300B
DS-5100B
DS-5300B
ES-5832B
MP-7800B
MP-8000B
ED-48000B
ED-DCX-B
ED-DCX-4S-B
FOS 6.2.2b DS-220B
ED-DCX8510-8B
ED-DCX8510-4B
Technical notes
a. The MP-8000B is not supported with FOS 7.2.0x or later.
Note: The minimumfirmware version does not indicate the minimumswitch
firmware version supported by EMC, but rather the min version that is
needed for CMCNE to properly recognize the switch. The EMC Support
Matrix takes precedence and if a higher version is listed in the ESM for a
certain product / blade then that is the version that should be used.
FOS 7.0.1 or higher DS-300B
DS-5100B
DS-5300B
ES-5832B
DS-6505B
DS-6510B
MP-7800B
MP-8000B
ED-DCX-B
ED-DCX-4S-B
ED-DCX8510-8B
ED-DCX8510-4B
DS-5100B
DS-5300B
ES-5832B
DS-6505B
DS-6510B
DS-6520B
MP-7800B
MP-8000B
a
ED-DCX-B
ED-DCX-4S-B
ED-DCX8510-8B
ED-DCX8510-4B
Operating system Switch/Director
27
Technical notes
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 Ethernet
switches; 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.1
a
, 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.x
b
12.2.x
b
, 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
Technical notes
Seed switch requirements
Fabric OS
Requires Fabric OS 6.4.2a or later for the seed switch in a pure Fabric
OS 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-12000B
Directors
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 EMC
Support Matrix, located at http://elabnavigator.emc.com.
Virtual Connect Enterprise Manager (VCEM) server discovery requirements
The following table lists the supported components for discovering
VCEM 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-Port
FC 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, QLogic
QMH2562 8Gb FC HBA
29
Technical notes
Note: EMC does not supply direct support for these components; however
CMCNE can manage them.
Important notes
This section lists information that you should consider before you use
CMCNE 12.1.6. See the Connectrix Manager Converged Network Edition
Professional, Professional Plus, and Enterprise Version 12.1.6 User Guide
for full details on the following notes.
Important notes that apply to SAN installations
1. Host based stand-alone SMI agents cannot manage products with
Fabric OS v7.0.x and higher. It requires use of the integrated SMI
Agent 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 JRE
1.6 U29 and later). The user is hence required to update to ESXi
5.0 update 1 or later to be able to manage the host in CMCNE
through the host adapter discovery.
3. If you see the following error message Signature could not be
validated during firmware download or technical support data
collection (Fabric OS and Network OS devices only) or
configuration backup/restore (Network OS devices only) using
SCP/SFTP, then it could be due to a mismatch in the signature
key used in the ssh handshake between the switch and SCP/SFTP
server. Try the following cli command work-around to address
the issue:
For Fabric OS devices
sw0:FID128:admin> sshutil delknownhost
IP Address/Hostname to be deleted: <IP Address of SSH server to be
deleted>
For Network OS devices
Firmware 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 sshdeleteknownhost
IP Address/Hostname to be deleted: <IP Address of SSH server to be
deleted>
Technical notes
If the above does not work, go to Server > Options > Software
Configuration > FTP/SFTP/SCP, and uncheck the SCP/SFTP
option.
4. Firmware upgrade to an MP-8000B platform using CMCNE will
be disruptive to I/O on the MP-8000B platform.
5. Firmware Download operation on Fabric OS switches fails when
trying to upgrade from FOS v6.4.2a to v7.0.2c. The workaround is
to use CLI for this operation.
6. Trying to move 200+ ports to a Logical Switch with Reset to
Default 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 is
performed. If the user Administrator alone has access to the
drive, 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 the
Network Advisor client if the server IP is not registered on the
switch to receive SNMP traps from the switch.
9. After upgrading to CMCNE 12.x from 11.x, SSL-based product
communication will fail if the devices have weak authentication
certificates. The user will see a 4002 error on attempting to
discover such devices. Devices discovered prior to migration will
not be manageable in CMCNE after migration. Java 1.7 used by
CMCNE 12.x disables the use of certificates with weak
authentication. The certificates on such devices need to be
updated to be compliant with JRE v1.7. Please refer to the Secure
Sockets Layer protocol section of FOS Admin guide for details on
updating certificates.
10. Receive Throughput measure is not updated in Flow Vision
dialog.
11. D-port test fails for F-ports with the result as null in the report.
12. In Real Time performance graphs, percentage utilization will
fluctuate between 0 -100 if a single port is selected. The
workaround is to select more than one port while generating Real
Time performance graphs.
13. CMCNE uses SNMPv3 by default to discover SAN products. If
required, user can select the Manual option in Discovery dialog
and choose SNMPv1 for discovery.
31
Technical notes
14. There could be false alarms indicating that the Zone database and
the active zone configurations are modified if any of the names of
the zoning elements (zones, zone configurations or aliases)
contain underscores (_) in the Zone database that is saved or
activated on to a fabric by Network Advisor.
15. Adelay of 5 to 7 minutes is seen when Web Tools is launched on a
system (through CMCNE or directly in a web browser) where
internet access is not available and the network does not return a
destination unreachable message. This issue occurs as Java tries
to validate the SSL certificates with external CAs. This problem
can be avoided on such systems by modifying the below Java
properties:
On Windows: C:\Users\<logged in
username>\AppData\LocalLow\Sun\Java\Deployment\depl
oyment.properties
On Linux: home/< logged in user
name>/.java/deployment/deployment.properties
In the deployment.properties file, edit the below parameters
and set them to false. If these parameters are not present, add
them and save the file. Then re-launch Web tools.
deployment.security.validation.ocsp = false
deployment.security.validation.crl = false
Display of Logical switches
If you create Logical switches through the Logical Switch dialog box,
the Logical switch displays under undiscovered Logical Switch in the
existing Logical Switches Panel. You have to rediscover the newly
created logical switch fabric, by going to the discovery dialog, and
adding the IP address of the chassis using the add dialog.
Destination columns are blank for ES-5832B Encryption switch in
top talkers dialog
When the Top Talkers dialog box is launched for the ES-5832B
Encryption Switch, the columns Destination, Destination port and
Destination switch port are sometimes empty.
SSL connections using certificates with MD5 signatures
To avoid potential security vulnerabilities, CMCNE 12.1.x and later
do not support SSL connections using certificates with MD5
signatures. If CMCNE is configured to use HTTPS instead of HTTP
when communicating with SAN switches, and the SAN switch has a
Technical notes
certificate installed that is signed with an MD5 algorithm, discovery
of 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 network
device with a certificate using the more secure SHA signature. If that
is not practical, the CMCNE server configuration can be changed to
accept MD5 signatures. Note that accepting MD5 signatures may
result 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.security
On 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 is
restarted.
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 Switch
through the Right Arrow button i.e., from (Chassis ports
Tree/Tree Table) LHS to (Logical Switches Device Tree) RHS
device tree.
It is not applicable when:
a. Ports from a Logical Switch are moved to default Logical
Switch through Left Arrowbutton, i.e., from(Logical Switches
Device Tree) RHS to (Chassis ports Tree/Tree Table) LHS.
b. When a Logical Switch is deleted - its ports will not be reset to
default before moving to Default Logical Switch before its
deletion.
Ports which are moved to the default logical switch can be reset to
default, 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 configurations
in the following scenarios:
33
Technical notes
a. In MP-7500B and FR4-18i, VE ports cannot be reset to default
unless their corresponding GE ports are cleared of their FCIP
configurations.
b. In MP-7800B and FX8-24, GE ports cannot be reset to default
unless their corresponding VE ports are cleared of their FCIP
configurations.
Important notes that apply to IP installations
1. 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 configured
for various parameters, such as "ip-filter-sys" for ACLs. CMCNE
deployments do not check whether the payload being sent to the
device has a number greater than the system-max value. In such
deployment scenarios, the deployment may report success even
though the number was limited to the system-max value. To
ensure successful deployments, make sure the payload being sent
is no greater than System max value.
3. Syslog messages will not be received for the VDX 8770 that is
configured with different IP addresses for CPs
4. Simplified image upgrade is recommended for NI devices
running 5.3 and above.
5. Fixed Form Factor switches running Network OS 4.0 are
displayed 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 VDX
devices, only of the attached ports is displayed in the Zoning
dialog.
IP address and detailed reports
IP Management Ports will not be consistent with the CLI port naming
conventions. These are caused by SNMP index and port name
inconsistencies. In some cases, Management ports will not be
displayed in the reports.
Boot, monitor, firmware image updates
1. CMCNE does not support boot and firmware upgrade and
downgrade for ADX devices running 12.1 or above.
Technical notes
2. Firmware Image Update on FastIron devices using Configuration
Wizard using "SCP only" or "SCP then TFTP" results in the
corruption of the flash to which image is pushed. Use CLI as
workaround.
3. Firmware Download to NetIron CES devices fails via SCP with
the error message there is not enough space on MP flash.
Important notes that apply to both SAN and IP installations
1. 64-bit OS is required to run Enterprise and Professional Plus
Editions.
2. M-series switches are unsupported as Seed switch or member
switch 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 Management
dialog with these prefixes.
4. CMCNE server startup and restart can take up to 10+ minutes to
complete.
5. When configuring CMCNE in SSL enable mode in application
configuration wizard, please ensure that both HTTP and HTTPS
ports are free and available for CMCNE. Currently the
application checks only if the HTTPS configured port is available
and not the HTTP port.
6. To avoid excessive telnet/ssh login messages in the CMCNE
master log and event report, and the device CLI console, disable
lazy polling by un-checking the "Enable lazy polling" checkbox in
IP Discovery Global Settings > Preferences Dialog.
7. In CMCNE 12.0.x, the number of client connections supported
has increased to 25. Please refer to the "Installation" section of
CMCNE User Guide for the details. In addition to those details,
the following database memory setting is required:
a. The PostgreSQLs parameter shared buffers memory
allocation should be increased to 1024 MB. (This setting can be
done 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.
35
Technical notes
8. During installation, it is recommended to use the Hostname as
the server IP configuration.
9. In CMCNE 12.x.x, 75-day Trial versions (for both full install and
migration) are only available for Enterprise Edition. Professional
Plus Edition is no longer available for 75-day Trials.
10. If you are using the ODBC connection from a remote host to the
database, after migrating to 12.0.x, you will no longer be able to
connect from the remote host. If you want to connect from the
remote host, please refer to the Configuring remote client access
to the database section in the Installation chapter of the
CMCNE User Guide.
Security vulnerability
If the CMCNE Server resides on a public lan it may be vulnerable to
remote attacks which can transfer and execute arbitrary code.
Resolved in CMCNE v12.1.2 under defect# 443127. For further
information see EMC ESA-2013-089. As a security best practice,
customers are strongly advised to isolate the CMCNE server from
external networks using VLANs and/or firewall rules only allowing
authorized administrators to interact with the CMCNE server.
Patch installer troubleshooting
Patch installer may not launch if UAC is enabled on a Windows
7/2008/2008R2 Editions. User has to first disable the UAC using the
procedure provided in the troubleshooting section of the CMCNE
User Guide and then launch the patch installer.
Support Saves may take a long time with large databases
As databases grow larger from Event, sFlow, and Performance
Collector data, the support save operation may take a long time to
run. Larger databases will promote longer support save operations.
Make sure you have a minimum of 20 GB disk space for support save
and backup operations.
Installation on Network Mounted Drives is not supported
Installation onto a windows network mounted drive is not supported
but install is allowed and DB fails to start.
Client disconnects
Under heavy server load or degraded network links, there is a
potential for Network Advisor client to get disconnected from the
server. Work around is to restart the client.
Technical notes
Performance Statistics Counters - Calculation Formulae
For calculating the statistics for FC, GE, FCIP and TE port we use
SNMP to query the respective OIDs, mentioned below in the table.
For calculating the HBA and CNA statistics, we use the APIs
provided 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, it
changes based on the granularity value selected in the Real Time
graph dialog.
Counter Name Type Protocol
used
Source value Formula
TX FC SNMP .1.3.6.1.3.94.4.5.1.6
TX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
RX FC SNMP .1.3.6.1.3.94.4.5.1.7
RX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
TX GE SNMP .1.3.6.1.2.1.31.1.1.1.10
TX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
RX GE SNMP .1.3.6.1.2.1.31.1.1.1.6
RX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
TX FCIP SNMP .1.3.6.1.2.1.31.1.1.1.10
TX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
RX FCIP SNMP .1.3.6.1.2.1.31.1.1.1.6
RX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
Uncompressed
Tx/Rx MB/sec
FCIP SNMP .1.3.6.1.4.1.1588.4.1.1.6
(Delta value
a
/ (1000 * 1000)) / (
Polling interval
b
)
TX EE
Monitors
HTTP PortRX (variable from the
return html file)
TX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
37
Technical notes
RX EE
Monitors
HTTP PortTX (variable from the
return html file)
RX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
TX HBA, CNA HCM API NA
TX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
RX HBA, CNA HCM API NA
RX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
TX TE SNMP .1.3.6.1.2.1.31.1.1.1.6
TX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
RX TE SNMP .1.3.6.1.2.1.31.1.1.1.10
RX = (Delta value
a
/ (1000 * 1000))
/ (Polling interval
b
)
TX% / RX% FC, GE,
FCIP,
HBA, CNA
NA NA TX% or RX% = ((TX or RX) / ((
105000000 * port speed)*( Polling
interval
2
))) * 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
interval
b
))) * 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 value
a
/ (1000
* 1000)
Other Counters
Other counters = Delta value
a

Counter Name Type Protocol
used
Source value Formula
Technical notes
a. Delta value1: is the difference of value retrieved between the two consecutive
poling 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
39
Technical notes
Important notes for the SMI Agent
1. 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 Instances
Names and total number of size is more than 2 MB for all
managed fabrics, then CIM_ERROR_FAILED will be thrown as
the 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 instances
then user should change the max jvm heap size to 2048 MB to fetch the
data without failure in 64 bit machine.
2. SMI alert indication BRCD60 is not sent out to SMI clients if
Fabric OS switches are discovered but SNMP trap registration has
failed. Ensure that CMCNE server is successfully registered for
traps 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
Technical notes
3. If DCB switches are running Fabric OS 6.3.x and 6.3.1_cee,
VLAN/ACL deployment through SMI-Awill fail. It is required to
upgrade the DCB Fabric OS to 6.4.x/6.3.1_dcb/7.0.x for
VLAN/ACL deployment support through SMI Agent.
Indications delivery depends on SAN size and SNMP registration
The time to deliver the indication will vary based on CMCNE SAN
size 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 if
the switches managed in CMCNE are not SNMP registered. As this
would cause a delay in indication delivery, all the switches managed
in CMCNE should be SNMP registered.
Logging for CIMOM
The default logging level is "INFO" in integrated Agent. To change
the logging level to DEBUG, update the "com.brocade" category
value in cimom-log4j.xml file present in <Installation Dir>\conf
folder.
The log file size and number of log files also can be changed by
modifying the file rolling appender parameters in this
cimom-log4j.xml file.
Logging Level, File size and Number of Log files can be changed by
modifying the following fields:"Log Level", "File Size" and "Number
of Files" from Configuration Tool through CIMOM tab.
Service Location Protocol (SLP) support
The Management application SMI Agent uses Service Location
Protocol (SLP) to allow applications to discover the existence,
location, and configuration of WBEMservices in enterprise networks.
You do not need a WBEMclient to use SLP discovery to find a WBEM
Server; that is, SLP discovery might already know about the location
and capabilities of the WBEM Server to which it wants to send its
requests. In such environments, you do not need to start the SLP
component of the Management application SMI Agent.
However, in a dynamically changing enterprise network
environment, many WBEMclients might choose to use SLP discovery
to find the location and capabilities of other WBEM Servers. In such
environments, start the SLP component of the Management
application SMI Agent to allow advertisement of its existence,
location, and capabilities.
41
Technical notes
SLP installation is optional and you can configure it during
Management application configuration. Once installed, SLP starts
whenever the Management application SMI Agent starts.
Management SMI Agent SLP application support
Management SMI Agent SLP application support includes the
following components:
slpd script starts the slpd platform.
slpd programacts as a Service Agent (SA). Adifferent slpd binary
executable 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 operating
properly or not.
By default, the Management application SMI Agent is configured to
advertise itself as a Service Agent (SA). The advertised SLP template
shows its location (IP address) and the WBEM Services it supports.
The default advertised WBEM services show the Management
application SMI Agent:
Accepts WBEM requests over HTTP without SSL on TCP port
5988
Accepts WBEM requests over HTTPS using SSL on TCP port 5989
slptool commands
Use the following slptool commands to verify whether the SLP is
operating properly.
slptool findsrvs service:service-agent
Use this command to verify that the Management application
SMI Agent SLP service is properly advertising its WBEMservices.
Example output: service:service-agent://127.0.0.1,65535
slptool findsrvs service:wbem
SMI Agent SLP service is properly advertising its WBEMservices.
Example outputs:
service:wbem:https://10.0.1.3:5989,65535
service:wbem:http://10.0.1.3:5988,65535
This output shows the functionalities of Management application
SMI Agent:
Technical notes
Accepts WBEM requests over HTTP using SSL on TCP port 5989
Accepts WBEM requests over HTTP without SSL on TCP port
5988
slptool findattrs service:wbem:http://IP_Address:Port
Use this command to verify that Management application SMI
Agent SLP service is properly advertising its WBEM SLP
template 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 that
display when you use the slptool findsrvs service:wbem command.
slptool findattrs service:wbem:https://IP_Address:Port
SMI Agent SLP service is properly advertising its WBEM SLP
template 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 that
display when you use the slptool findsrvs service:wbem command.
SLP on Windows systems
This section describes how to verify the SLP daemon on Windows
systems.
SLP file locations:
SLP logManagement_Application\cimom \cfg\slp.log
SLP daemonManagement_Application\cimom\cfg\slp.conf
The SLP daemon can be reconfigured by modifying this file.
SLP registerManagement_Application\cimom\cfg\slp.reg
statically register an application that does not dynamically
register with SLP using SLPAPIs by modifying this file.
For more information about these files, read the comments
contained in them, or refer to
http://www.openslp.org/doc/html/UsersGuide/index.html
43
Technical notes
Verifying SLP service installation and operation on Windows
systems:
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 press
Enter to change to the directory where slpd.bat is located.
5. Type > slptool findsrvs service:service-agent and press Enter to
verify the SLP service is running as a Service Agent.
6. Type > slptool findsrvs service:wbem and press Enter to verify
the SLP service is advertising its WBEM services.
7. Choose one of the following options to verify the SLP service is
advertising the WBEM SLP template over its configured client
protocol adapters:
Type > slptool findattrs service:wbem:http://IP_Address:Port
and press Enter.
Type>slptool findattrsservice:wbem:https://IP_Address:Port
and press Enter.
Note: Where IP_Address:Port is the IP address and port number that display
when you use the slptool findsrvs service:wbem
Enumeration issue with MP-8000B running on Fabric OS 6.3.x or
lower
Enumeration 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 or
lower, connected to FDMI enabled CNA.
Instance class key property with special character
Getinstance operation fails if the key property value contains
semicolon or non printable character.
Technical notes
FC port type value for imported HBAs
Brocade_topologyview.AntecedentFCPortType property value
corresponding to the imported HBA is shown as L_port.
Server platform information
The 1u Connectrix service processor platform is no longer available.
Therefore the customer should supply their own Intel based
workstation running Windows 2008 or Windows 7 per the processing
power requirements described inEnvironment and system
requirements on page 11.
Operating System services such as SNMP, http, and ftp will cause
conflicts with the embedded functions within CMCNE. These
operating system, or other third-party services, must be disabled.
Note that sometimes Windows Automatic Update will install
updates for these services and, in turn, re-enable the service.
Therefore, if you plan to run Windows Automatic Update it is
recommended that the Microsoft operating services for the above not
be installed.
Automatic backup device
CMCNE has an automatic backup service that runs in the
background. This service will backup critical CMCNE information to
a drive/directory location. This service can be configured so that the
backups occur to the drive directory location of choice.
If the platform being used can contain multiple hard drives then
selecting a secondary hard drive destination would probably be the
most convenient and reliable choice. Also, if the customer system
contains two hard drives that are mirrored and then divided into two
partitions (logical drives), this will lessen the chances of data loss. A
single hard-drive system could be partitioned into two logical drives,
with the secondary partition (D:\ drive) being smaller in size; 1~ 5
gig 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 USB
Zip Drive 250 MB, or a mapped network drive.
Note: Backing up to CD-RW drive is not the recommended method. The
usable capacity of a CD is approximately 700 MB and needs to be replaced
when full. Also, CD media has a limited number of re-writes before the
45
Technical notes
medium is exhausted and write errors occur.
It is recommended that you configure the backup system to target a hard
drive or a network drive as described in the Data Backup section in
Application Configuration chapter in the Connectrix Manager Converged
12.1.6 User Guide.
If a CD-RW drive is chosen then the CD drive should be a CD-RW
drive and blank CD-RWUDF formatted media will need to remain in
the CD-RW drive so that the automatic backup of CMCNE data can
occur to the CD-RW disk. Note drivers and software for the CD-RW
drive must present CD-RW to the OS as an accessible storage device
for the writing of files without the need to launch special CD-RWdisk
burning software. The automatic backup application just writes to the
D:\ 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 alternative
because the backup function needs to write to the CD-RW disk
repeatedly. Therefore, media will have to be monitored and replaced
when it becomes full and/or if it becomes defective, with a mapped
network drive and/or second hard drive replacing media is not an
issue.
Whichever external drive type is chosen, it will need to be
mounted/mapped to the platform such that the OS can utilize the
device as a standard drive letter. Devices that require manual
intervention before being written to, such as a CD-R drive, will not
work.
Note: The network drive backup is the EMC-recommended option. To
configure an alternate backup destination, follow the procedures in
Application Configuration chapter in the Connectrix Manager Converged
12.1.6 User Guide.
There are specific settings for the backup service that must be configured
properly for backing up to a network drive detailed in Data Backup section
in the Application Configuration chapter in the Connectrix Manager
Converged Network Edition Professional, Professional Plus, and Enterprise
Version 12.1.6 User Guide.
Technical notes
EMC Call Home and remote support
The Call Home feature, in conjunction with ConnectEMC, allows the
Connectrix service processor to automatically call home to the EMC
support center to report system problems. The support center Server
accepts calls from the Connectrix service processor, logs reported
events, and can notify one or more support center representatives.
ConnectEMC can be configured to Call Home using either a dialup
connection or by sending an email directly to the EMC Call Home
center. 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 EMCMultitech MT9234ZBAmodemto
call home using a dialup connection. Contact your EMC sales
representative to order the correct modem for your country/location.
No other brand/type modem can be used. You also will need to
provide a DB9 Female to DB25 Male, 9-Conductor Standard AT
Modem Cable, similar to BlackBox part# BC00302 for connection of
the modem to the COM1 port on your Server platform.
Note: EMC personnel can obtain the support applications, ConnectEMC v5.x
and EMCRemote Host v7.x, from EMC Online Support at
http://support.emc.com or the Connectrix Manager Converged
Network Edition - Enterprise Software CD shipped with the
customer's order.
EMC will need to install its remote support applications,
ConnectEMC v5.x and EMCRemote Host v7.x on the customer
supplied service processor. The EMC Multitech MT9234ZBA modem
will need to be connected to a COM port on the Server for these
applications. Refer to the Call Home Setup Procedure chapter in
the Connectrix Manager Converged Network Edition Professional,
Professional Plus, and Enterprise Version 12.1.6 User Guide for further
information on ConnectEMC and Call Home setup procedures. Note
the EMC modem will need to be connected to a COM port and the
above 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 the
EMC Multitech modem:
&E1&E4&E13$R1S10=100&S0&SF1#F1&E7
47
Technical notes
The Microsoft Windows operating system will need to be configured
with a user for EMC support personnel to log on for local and remote
support work.
The EMC Call Home software must be installed, configured, and
tested by EMC service personnel before putting the platform into
operation. The Call Home Setup Procedure chapter in the EMC
Connectrix Manager Converged Network Edition Professional, Professional
Plus, and Enterprise Version 12.1.6 User Guide contains the appropriate
procedures.
Note: Modem-based call home and/or remote support is not for use when
the CMCNE server platform is running as a Windows guest OS VM on
VMWare ESX Server. ESRS Gateway would be needed for VMWare-based
CMDCE server platforms.
ESRS Gateway
The ESRS Gateway is a secure IP-based infrastructure that supports a
standard remote support technology for EMChardware and software
products. It also enables customers to actively participate in
management 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 CMCNE
The CMCNE service processor platform must be dedicated for
CMCNE and EMC's remote support applications. This platform
cannot also be used for other services such as file, print, email,
database, web server, etc.
Network / LAN considerations
The customer-supplied CMCNE service processor platform may
have one or two NICs. There are configuration options for the
connection of the management ports on the switches and the
management platform, dependant upon the number of NICs and
network environment to be utilized.
The CMCNE service processor platform should be connected to a
management LAN used by the SAN administrators to use remote
CMCNE Client installations. The customers network security
guidelines may dictate what type of LAN this is, but it is
recommended that it not be a generally-available, wide-open public
LAN, but rather one restricted for use by the SAN administrators.
Technical notes
Field experience with large data center networks that introduce new
or unusual Ethernet technologies, including aggressive monitoring
systems, may be disruptive to the management services provided by
the Connectrix service processor. Careful thought and planning
should go into connecting LAN interfaces on the same network
shared by the customer-supplied service processor.
See the Deployment best practices for public/private networks
section in the Installation chapter in the Connectrix Manager
Converged Network Edition Professional, Professional Plus, and Enterprise
Version 12.1.6 User Guide for further information.
Third-party software
Generally speaking, anti-virus software is the most common
third-party application requested for installation, such as Norton and
McAfee. There are no issues that prevent the use of these anti-virus
applications. However, EMC cannot guarantee any level of
performance and/or reliability with third-party applications. If a
customer deems a certain piece of software necessary to install on
their Server, then they can do so with the condition that it may need
to be uninstalled in the event it causes conflicts with the EMC
applications. Remote control applications such as PCAnywhere
cannot be installed because they will directly conflict with
EMCRemote. Other remote control applications, such as Terminal
Services and VNC, may work, but it is recommended that they not be
installed.
Customer assumes responsibility for support of hardware platform
and software compatibility for any other applications they choose to
load onto that platform.
Connectrix service processor information
This section contains information on the Connectrix service
processor.
Operating system upgrades
If a customer wants to activate Microsoft Automatic Update on the
service processor for the Microsoft Windows Operating System they
can do so; however, they should probably reviewwhich updates they
want to install for their particular environment. It is the customer's
49
Technical notes
responsibility to install any updates they deem necessary for their
environment.
IMPORTANT
CMCNE is not supported on the older original 1u Service Processor
that shipped with Windows 2000 or the newer EMC 1u service
processor that shipped with Windows 2003. To run CMCNE the
customer must supply their own platform that meets the minimum
hardware requirements as published in the CMCNE 12.1.6 Release
Notes and User Guide.
Dedicated for CMCNE The Connectrix service processor must be dedicated for CMCNE and
EMC's remote support applications designed for Connectrix service
processors. This platform cannot also be used for other services such
as file, print, email, database, web server, etc.
Management network topology best practices
See the Deployment best practices for public/private networks
section in Installation chapter in the Connectrix Manager Converged
12.1.6 User Guide for further information.
By default, the Connectrix service processor ships from the factory
with one network interface configured to connect to the private
10.x.x.x network inside the Connectrix cabinet. There is a second NIC
that can be configured and connected to a customer management
LAN. It is up to the customer's discretion to configure this second
network interface as they deem appropriate to manage the
Connectrix service processor and managed products. It is
recommended that this second network be as secure as possible and
be restricted to the administrators of the Connectrix products.
If FOS-based products are configured to reside on a different IP
network than the management LAN that remote CMCNE client
workstations are on, then launching of the FOS-based products
management tools will not work from the remote CMCNE clients.
However, the FOS-based products could be configured to reside on
the same network as the remote CMCNE clients and/or the remote
CMCNE clients could be dual-homed to also have access to the
switch management LAN. It is recommended that these switch
management LANs be as secure as possible and be restricted to just
the SAN administrator personnel that need access.
Documentation
Management network security considerations and third-party applications
As most customers are keenly aware, connecting any workstation to a
public LAN adds risk. The customer should factor in all aspects of
management objectives for this Connectrix service processor versus
the risk level of the type of LAN it will be connected to. Many
customers have various other tools they use to mitigate this risk, i.e.,
restricted LANs/subnets, anti-virus software, and other system
administrative tools. Adding third-party software to the Connectrix
service processor is not recommended; however, it is allowed under
the following conditions:
Generally speaking, anti-virus software is the most common
third-party application requested for installation; i.e., Norton and
McAfee. There are no issues that prevent the use of these
anti-virus applications. However, EMC cannot guarantee any
level of performance, compatibility, and/or reliability with
third-party applications.
If a customer deems a certain piece of software necessary to
install on their service processor for their particular environment,
they can do so with the condition that it may need to be
uninstalled if it causes conflicts and incompatibilities with the
EMC applications. It is the customers responsibility to maintain
this software.
Note: Remote control applications, such as PCAnywhere, cannot be
installed because they will directly conflict with the EMCremote support
applications.
Documentation
The following related documentation can be found on EMC Online
Support at http://support.emc.com.
Connectrix Manager Converged Network Edition Professional,
Professional Plus, and Enterprise Version 12.1.6 User Guide
Belowis a link to a collection of EMCnetworked storage topology
Tech Books and Reference Manuals.
http://www.emc.com/products/interoperability/topology-resource-center.htm
51
Software media, organization, and files
The Connectrix Manager Converged Network Edition v12.1.6 is
available in SAN only, SAN & IP, and IP only model options. See the
model table below. CMCNE-SAN-ENT, CTX MGR CNE SAN
Enterprise would be the equivalent to the CMCNE 11.x SAN
Enterprise and CMDCE 10.x SAN Enterprise versions.
SAN and the SAN and IP licenses bundles are available in
Professional Plus and Enterprise versions. The IP only management
options are built off and IP base starting point then incremental
device count or feature add-on licenses can be added to that IP base
starting point and/or upgraded with SANupgrade licenses to enable
a SAN & IP Professional Plus or Enterprise level of capabilities. The
available Professional, Professional Plus, and Enterprise packages
and capabilities are listed in the following two tables.
Package Versions
SAN with SMI Agent +IP Licensed VersionEnterprise
SANSupport for 36 fabrics, 10,000 devices, and 9,000
switch ports
IPSupport for 5,050 devices, 252,500 ports, and 100
MPLS devices
Professional
SANSupport for 1 fabric and 1,000 switch ports
IPSupport for 20 devices and 1,000 ports
Note: SMI Agent is not supported on Professional.
SAN with SMI Agent Licensed VersionEnterprise
SANSupport for 36 fabrics, 10,000 devices, and 9,000
switch ports
Licensed VersionProfessional Plus
SANSupport for 36 fabrics, 4,096 devices, and ,2560
switch ports
Professional
SANSupport for 1 fabric and 1,000 ports
Note: SMI Agent is not supported on Professional.
CMCNE v12.1.6 is available for download from
http://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 VersionEnterprise
IPSupport for 5,050 devices, 252,500 ports, and 100
MPLS devices
Professional
IPSupport 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 generation
11.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 switch
ports (~120 devices) and 36 fabrics
CMCNE-SAN-PLU CTX MGR CNE SAN Pro Plus Most like the CMCNE 11.X Professional Plus
SAN management SW license for up to 2,560 switch
ports (~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 only
lic.
Must install this lic first to a SAN only install before
adding 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 IP
devices, Advanced IP capabilities, 9000 SAN switch
ports (~120 devices), and 36 SAN fabrics
CNE-SANIP-PLU CTX MGR CNE SAN-IP Pro Plus IP and SAN management SW license for 150 IP
devices, 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
53
The CMCNE v12.1.6 installer package can be downloaded by
licensed 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 license
is required for the Professional Plus or Enterprise version which can
be obtained by ordering the models listed above.
CNE-IPB-50 CTX MGR CNE IP BASE Base starting point for IP only management license for
up to 50 devices,
No Advanced IP functions. Cannot add SAN
capabilities to this license. Must first Add
CNE-IPADV100 in order to have Adv IP and/or add
SAN functions.
IP Upgrades Incremental IP Add-Ons to IP Bases
CNE-IPADV100 CTX MGR CNE - ADD IP DATA CTR TO IP
BASE
Adds IP Data Center Management for 1 VCS Fabric to
an 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 UPG
LIC
Adds MPLS management for up to 10 devices
LIC
LIC
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 switch
ports (~120 devices) and 36 fabrics to IP only
management. Must have already added
CNE-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. Must
have already added CNE-IPADV100 to an IP Base
first.
CNE-IPSANPLUE CTX MGR CNE - IP ADD ENT TO PLUS LIC Upgrades SAN and IP install from ProPlus SAN level
to SAN Enterprise level. Must have previously installed
CNE-IPUSANPLU
Model Description Notes
Installation
It is possible to run the CMCNE Enterprise version under a 75 day
trial license; however this should only be done for short term
evaluation purposes. After 75 days you will not be able to log in with
a CMCNE client; therefore production environments are only
supported if fully licensed.
Note: In CMCNE 12.x.x, 75-day Trial versions (for both full install and
migration) are only available for the Enterprise Edition. Professional Plus
Edition is no longer available for 75-day Trials.
EMC customers upgrading from Connectrix Manager or Fabric
Manager who's current software installations are covered by a valid
EMC Software Support contract can obtain an upgrade license by
contacting the EMC Software Refresh Group at one of the following
numbers:
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 Support
Center at the numbers above, and select Option 2.
Installation
This section contains installation and upgrade and downgrade
considerations.
For more detailed information, refer to the "Installation" chapter in
the 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 instructions
before beginning the installation process.
For detailed instructions for new installations refer to the
"Installation" chapter in the Connectrix Manager Converged Network
Edition Professional, Professional Plus, and Enterprise Version 12.1.6 User
Guide.
55
Installation
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, refer
to the "Migration and Transition" section of the Connectrix
Manager Converged Network Edition Professional, Professional Plus,
and Enterprise Version 12.1.6 User Guide.
You cannot migrate directly from CMCNE 11.1.x to CMCNE
12.1.6. You must first migrate to CMCNE 11.2.1 before migrating
to CMCNE 12.1.6. To migrate from CMCNE 11.1.x to CMCNE
11.2.1, refer to the EMC Connectrix Manager Converged Network
Edition Professional, Professional Plus and Enterprise Version 11.2.1
User Guide available on EMC Online Support.
You cannot migrate directly from CMDCE 10.4.x to CMCNE
v12.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
Converged Network Edition Professional, Professional Plus and
Note: Although migrating to CMCNE 11.1.1 is supported, EMC
recommends using CMCNE 11.1.4 as the intermediate step when
migrating fromCMDCE 10.4.x to CMCNE 12.1.6 Using CMCNE 11.2.1 as
the intermediate step when migrating from CMDCE 10.4.x to CMCNE
12.0.x is NOT supported.
You cannot migrate directly from CMDCE 10.1.X or 10.3.X to
CMCNE 12.1.6. 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 or CMCNE 12.0.x, before migrating to
CMCNE 12.1.6. To migrate from CMDCE 10.1.X or 10.3.X to
CMDCE 10.4.5, refer to the "Migration and Transition" section of
the 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.5
users must 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 or CMCNE 12.0.x, before migrating to CMCNE
12.1.6. To migrate from CM 9.x or Fabric Manager to CMDCE
Installation
10.3.4 and 10.4.5, refer to the EMC Connectrix Manager Data Center
Edition Professional, Professional Plus and Enterprise Version 10.4.5
User Guide.
To migrate from CMDCE 10.4.5 to CMCNE 11.1.x, refer to the
Converged Network Edition Professional, Professional Plus and
Note: Although migrating to CMCNE 11.1.1 is supported, EMC
recommends using CMCNE 11.1.4 as the intermediate step when
migrating from CMDCE 10.4.x to CMCNE 12.0.x. Using CMCNE 11.2.1
as the intermediate step when migrating from CMDCE 10.4.x to CMCNE
12.0.x is NOT supported.
Customers running CMDCE 10.x.x, who have a valid
maintenance contract, can migrate to the CMCNE 11.1.x SAN
with SMI Agent" package, then migrate to CMCNE 11.2.1 "SAN
with 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 more
information, please contact your local EMC Representative.
A customer's existing CMDCE 10.x or CMCNE 11.x Enterprise
Edition license can be used to install the CMCNE 12.1.6
Enterprise Edition SAN with SMI Agent package or to upgrade
a CMCNE 12.1.6 Enterprise Trial SAN with SMI Agent package
to CMCNE 12.1.6 Enterprise Edition SAN with SMI Agent
package.
A customer's existing CMDCE 10.x or CMCNE 11.x Professional
Plus Edition license can be used to install the CMCNE 12.1.6
Professional Plus Edition SAN with SMI Agent package.
In v12.1.6, 75-day Trial versions (for both full install and
migration) are only for Enterprise Edition. Professional Plus
Edition is no longer supported for 75-day Trials. Therefore, a
customer's existing CMDCE 10.x or CMCNE 11.x Professional
Plus Edition license can only be used to change a CMCNE 12.1.6
Enterprise Trial SAN with SMI Agent package to CMCNE
12.1.6. Professional Plus Edition SAN with SMI Agent package.
Network path migrations from CMCNE 11.2.1 on one server to
CMCNE 12.1.6 on another are not supported and require
additional steps to complete a successful migration. This includes
57
Installation
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-bit Windows
server to a 64-bit Windows server. For more information on the
supported migration path, refer to the "Pre-migration
requirements" section in the "Migration and Transition" chapter of
the EMC Connectrix Manager Converged Network Edition
Professional, Professional Plus and Enterprise Version 12.1.6 User
Guide.
Network path migrations from CMCNE 12.0.x on one server to
CMCNE 12.1.6 on another are not supported and require a
backup 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-bit
Windows server to a 64-bit Windows server. For more
information on the supported migration path, refer to the
"Pre-migration requirements" section in the "Migration and
Transition" chapter of the EMC Connectrix Manager Converged
Network Edition Professional, Professional Plus and Enterprise Version
12.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 on
EMC 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 > CMCNE
12.1.6.
Windows:
Client can be launched via Desktop icon.
Launch command prompt and go to the location C:\Program
Files\CMCNE 12.1.6\bin and type dcmclient.
Installation
Follow the steps below on launching the client from a web browser.
To launch the CMCNE Client from a remote host, launch the
client as follows:
Open a browser window and type the CMCNE server hostname
or 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 server
port number was specified (instead of the default 80), you must
specify the port number after the hostname or IP address. In the
following 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 is
done using Java Web Start technology. This requires the local systems web
browser to be able to run Java web start applications. This setting may have
been 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 to
http://java.com/en/download/help/win_controlpanel.xml
to 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. Click
OK 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 a
result, migration from a previous version of CMCNE to a newer supported
version fails.
The following steps need to be followed to resolve the issue:
59
Installation
1. Make sure that the previous version of CMCNE is up and
running.
2. Right click on the drive where the new version of CMCNE is
intended to be installed (E.g. :D).
3. Navigate to the Security tab -> Edit -> Add.
4. Add Authenticated Users and give full permission, click
Ok.
5. Now install the new version of CMCNE and start the
migration progress.
Installation notes
For complete installation information, or if you are upgrading from
the professional or enterprise trial versions of CMCNE, refer to the
Installation and Migration and Transition chapters in the
Connectrix Manager Converged Network Edition Professional, Professional
Plus, and Enterprise Version 12.1.6 User Guide.
Ensure the network environment does not have any firewall
installations between the client and the server and the switches. If
one exists, ensure that proper rules are set up to allow access.
You must choose the SAN size during the installation of CMCNE
Enterprise v12.1.6.
If you install CMCNE Server on a Windows host that has
anti-virus software, you must disable the anti-virus software
during the installation.
Install CMCNE Server on a dedicated machine that is not running
any other server applications, such as another database server.
CMCNE is supported under Windows 7, Windows 8, Windows
2008 or Windows 2012 guest operating systems that run under
VMWare ESXi 5.1. Other virtualization software is not supported.
Modem-based Call Home is not supported under Windows guest
operating system that runs under ESXi 5.1.
CMCNE v12.1.6 is tested under English only. All other foreign
languages 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.
Troubleshooting and getting help
Fabrics running with SecureFOS enabled are not supported and
are not discoverable in CMCNE.
If you are upgrading from the professional or enterprise trial
versions of CMCNE, refer to Installation and Migration and
Transition chapters in the Connectrix Manager Converged Network
Edition Professional, Professional Plus, and Enterprise Version 12.1.6
User Guide.
EMC support, product, and licensing information can be obtained as
follows.
Product information For documentation, release notes, software
updates, or for information about EMC products and services, go to
the 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 Center
on EMC Online Support at
To open a service request you must have a valid support agreement.
Please contact your EMC sales representative for details about
obtaining a valid support agreement or to answer any questions
about your account.
61
Copyright 2014 EMC Corporation. All rights reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
THE INFORMATIONINTHIS PUBLICATIONIS PROVIDEDAS IS. EMC CORPORATIONMAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN
THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in
the United State and other countries. All other trademarks used herein are the property of their
respective owners.
For the most up-to-date regulator document for your product line, go to EMC Online Support (
https://support.emc.com).

Docu54667 Connectrix Manager Converged Network Edition 12.1.6 Release Notes

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Docu54667 Connectrix Manager Converged Network Edition 12.1.6 Release Notes

Caricato da

Copyright:

Formati disponibili

1

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

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

Potrebbero piacerti anche