Brocade M-Series Products

Fabric Guidelines
P/N: 53-1000646-02

Corporate Headquarters Asia-Pacific Headquarters

Brocade Communications Systems, Inc. Brocade Communications Singapore Pte. Ltd.
1745 Technology Drive 9 Raffles Place
San Jose, CA 95110 #59-02 Republic Plaza 1
Tel: 1-408-333-8000 Singapore 048619
Fax: 1-408-333-8101 Tel: +65-6538-4700
Email: info@brocade.com Fax: +65-6538-0302
Email: apac-info@brocade.com
European and Latin American Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour A - 2ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: +41 22 799 56 40
Fax: +41 22 799 56 41
Email: emea-info@brocade.com
Copyright © 2007 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, the Brocade B-weave logo, Fabric OS, File Lifecycle Manager, MyView, SilkWorm, and StorageX are registered
trademarks and the Brocade B-wing symbol, SAN Health, and Tapestry are trademarks of Brocade Communications Systems,
Inc., in the United States and/or in other countries. FICON is a registered trademark of IBM Corporation in the U.S. and other
countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify,
products or services of their respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning
any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to
this document at any time, without notice, and assumes no responsibility for its use. This informational document describes
features that may not be currently available. Contact a Brocade sales office for information on feature and product availability.
Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that
accompany it.
The product described by this document may contain “open source” software covered by the GNU General Public License or other
open source license agreements. To find-out which open source software is included in Brocade products, view the licensing
terms applicable to the open source software, and obtain a copy of the programming source code, please visit http://
www.brocade.com/support/oscd.

Record of Revisions and Updates

Revision Date Description Revision Date Description
620-000208-030 4/2005 Support for current M-EOSi, 620-000208-080 12/2006 Support for M-EOS 9.x and
M-EOS, and M-EOSn releases M-EOSn 9.x
620-000208-040 7/2005 Support for M-EOS 8.0, M- 620-000208-090 1/2007 Support for M-EOSi 5.0
EOSn 6.3, and EFCM 8.7
620-000208-050 8/2005 Newer 4xxx switches and 620-000208-010 8/2007 Rebrand and update with current
other corrections Brocade EFCM data
620-000208-060 1/2006 Support for M-EOSi 4.7 53-1000646-02 12/2007 Deleted ED-5000 table; revised
metric on p. 5; added issue on p. 7
620-000208-070 3/2006 Minor update

Brocade Product Names

In this document, former product names may be used, and sometimes you will see names in abbreviated forms, for example,
“6140” or “E-OS.” Use this table to note current product names.

Former Product Name Current Product Name

McDATA Intrepid 10000 Brocade Mi10K Director
McDATA Intrepid 6140 Brocade M6140 Director
McDATA EFCM Enterprise, Standard, Basic Brocade Enterprise Fabric Connectivity Manager (EFCM)
McDATA 2640 SAN Router Brocade M2640 SAN Router
McDATA 1620 SAN Router Brocade M1620 SAN Router
McDATA UltraNet Edge Storage Router Brocade Edge M3000
McDATA UltraNet Director eXtended (6 slots) Brocade USD-X6
McDATA UltraNet Director eXtended (12 slots) Brocade USD-X12
McDATA FSP 2000 DWDM Brocade FSP 2000 Dense Wavelength Division Multiplexer (DWDM)
McDATA Sphereon 4700 Brocade M4700 Switch
McDATA Sphereon 4500 Brocade M4500 Switch
McDATA Sphereon 4400 Brocade M4400 Switch
McDATA Virtual Tape Library Brocade Virtual Tape Library
McDATA Virtualizer and the Application Services Module Brocade Virtualizer
McDATA Open Trunking Brocade Open Trunking
Enterprise OS - McDATA OS (E-OS) Brocade Enterprise OS (M-EOS)
McDATA SANtegrity Security Software Brocade SANtegrity Security Software
McDATA Cabinet Brocade Cabinet
McDATA SpectraNet WDS Accelerator Brocade WDS Accelerator
McDATA SpectraNet Replicator Brocade FAN Replicator
 Invisible Body Tag
1

M-EOS Fabric Guidelines

This document provides guidelines to produce stable fabrics.

The configuration of deployments in the field vary considerably from the SANs that were tested.

CAUTION: Extreme or unusual configurations may lead to unexpected results.

While a switch may support 1,024 members and 1,024 zones, it will not support 1,024 zones with
1,024 members. Consult Brocade Services before deploying extreme or unusual configurations.

NOTE: In cases where McDATA classic products are End of Life (EOL), their McDATA name is used.
Otherwise, current product names are used. For a list of former and current product names, see the
second (copyright) page of this document.

NOTE: If these guidelines cannot be met, contact your Brocade representative to pursue further
testing before deploying the configuration into production environments.

• Fibre Channel Guidelines on page 1

• SAN Router Guidelines on page 3
• Brocade EFCM Guidelines on page 5

Fibre Channel Guidelines

This section provides the general guidelines for Fibre Channel switches to follow for stable fabrics.
• Table 1: M-Series Switches and Directors (M-EOSc 5.0.7.x and M-EOSn 6.0–6.2.1)
• Table 2: M-Series Switches and Directors (M-EOSc 8.0 and M-EOSn 6.3-6.5.2)
• Table 3: M-Series Switches and Directors (M-EOSc 9.x and M-EOSn 9.x)

Table 1 M-Series Switches and Directors (M-EOSc 5.0.7.x and M-EOSn 6.0–6.2.1)

Intrepid 6064
Director
Sphereon 3x32 IMi10K
M4500 Sphereon 3x16 M6140 Director Directora
Product (M-EOSc) (M-EOSc) (M-EOSc) (M-EOSn)

Number of end ports 1,024 1,024 1,024 1,024

1,024 1,024 1,024

Unique zone members 2,048 (M-EOSc 2,048 (M-EOSc 2,048 (M-EOSc 2,048
6.0-7.x) 6.0-7.x) 6.0-7.x)

1,024 1,024 1,024

Members per zone 2,048 (M-EOSc 2,048 (M-EOSc 2,048 (M-EOSc 2,048
6.0-7.x) 6.0-7.x) 6.0-7.x)

Fabric Guidelines for Brocade M-Series Products December 16, 2007 1

 M-EOS Fabric Guidelines

Table 1 M-Series Switches and Directors (M-EOSc 5.0.7.x and M-EOSn 6.0–6.2.1)

Intrepid 6064
Director
Sphereon 3x32 IMi10K
M4500 Sphereon 3x16 M6140 Director Directora
Product (M-EOSc) (M-EOSc) (M-EOSc) (M-EOSn)

1,024 1,024 1,024

Zonesb 2,048 (M-EOSc 2,048 (M-EOSc 2,048 (M-EOSc 2,048
6.0-7.x) 6.0-7.x) 6.0-7.x)

Maximum devices supported 1,024 1,024 1,024 1,024

Maximum number of switches in a fabric when

24 24 24 24
this switch is present

70
Maximum number of ISLs per switchc 32
24 140 (M-EOSc 7.0 140d
48 (6064 only)
and later)

a The limits for the Mi10K Director are for aggregate counts across all Director Flexpars (partitions) on the chassis, regardless of whether
the partitions are in the same fabric or separate fabrics.
b The supported number of zones is based on a zone name with a maximum of 64 characters.
c The Sphereon 3016 switch can only support 16 ISLs as it only has 16 ports.
d This is the tested limit of ISLs per director regardless of which LIM-type is installed.

Table 2 M-Series Switches and Directors (M-EOSc 8.0 and M-EOSn 6.3-6.5.2)

Intrepid 6064
All M4xxx Sphereon 3x32
Product Switchesa Sphereon 3x16 M6140 Director Mi10K Directorb

Unique zone members 4,096 4,096 4,096 2,048

Members per zone 4,096 4,096 4,096 2,048

Zonesc 2,048 2,048 2,048 2,048

Maximum devices supported (logged in devices

1,500 1,500 1,500 1,500
including NV_Port logins)

Maximum virtual devices logged in per

256/1000 256/1000 256/1000 N/A
NV_port/switch (with NPIV feature)

Maximum number of domain IDs in a fabric

24 24 24 24
when this switch is present

Maximum total of domain IDs in all attached

N/A N/A N/A 50
fabrics (using multiple Director Flexpars)

32
Maximum number of ISLs per switchd 32
48 (6064 only)
140 140e

a Sphereon 4300, 4500, 4700, and M4400

b The limits for the Brocade Mi10K Director are for aggregate counts across all Director Flexpars (partitions) on the chassis, regardless of
whether the partitions are in the same fabric or separate fabrics.
c The supported number of zones is based on a zone name with a maximum of 64 characters.
d The maximum number of ISLs cannot exceed the number of physical ports available on the switch.
e This is the tested limit of ISLs per director regardless of which LIM-type is installed.

Table 3 M-Series Switches and Directors (M-EOSc 9.x and M-EOSn 9.x)

Intrepid 6064
All M4xxx Sphereon 3x32
Product Switchesa Sphereon 3x16 M6140 Director Mi10K Directorb

Unique zone members 4,096 4,096 4,096 2,048

Members per zone 4,096 4,096 4,096 2,048

Zonesc 2,048 2,048 2,048 2,048

2
December 16, 2007 Fabric Guidelines for Brocade M-Series Products
 M-EOS Fabric Guidelines

Table 3 M-Series Switches and Directors (M-EOSc 9.x and M-EOSn 9.x)

Intrepid 6064
All M4xxx Sphereon 3x32
Product Switchesa Sphereon 3x16 M6140 Director Mi10K Directorb

Maximum devices supported (logged in devices

2,048 2,048d 2,048 2,048
including NV_port logins)

Maximum virtual devices logged in per

256/1000 256/1000 256/1000 N/A
NV_port/switch (with NPIV feature)

Maximum number of domain IDs in a fabric

31 31d 31 31
when this switch is present

Maximum total of domain IDs in all attached

N/A N/A N/A 50
fabrics (using multiple Director Flexpars)

32
Maximum number of ISLs per switche 32
48 (6064 only)
140 140f

a Sphereon 4300, 4400, 4500, and 4700.

b The limits for the Mi10K Director are for aggregate counts across all director Flexpars (partitions) on the chassis, regardless of whether
the partitions are in the same fabric or separate fabrics.
c The supported number of zones is based on a zone name with a maximum of 64 characters.
d In fabric configurations exceeding 24 Domain IDs or 1500 devices, Sphereon 3XXX-series switches and the Intrepid 6064 should be de-
ployed only at the edge of the fabric.
e The maximum number of ISLs cannot exceed the number of physical ports available on the switch.
f This is the tested limit of ISLs per director regardless of which LIM-type is installed.

SAN Router Guidelines

This section provides general guidelines for Brocade SAN Routers to ensure stable fabrics.
• Table 4: Brocade M1620, M2640, Eclipse 3300, and Eclipse 4300 SAN Routers

Table 4 Brocade M1620, M2640, Eclipse 3300, and Eclipse 4300 SAN Routers

Brocade M1620 Brocade M2640

Eclipse Eclipse
3300, 4300, M-EOSi
M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi 5.0
Metric 4.5 4.7 5.0 4.5 4.4.5 4.6.2 4.7 5.0 FC-HA

Fibre Channel

Maximum number of (tested) FC fabrics

2 N/A 2 2 2 6 N/A 10 5
per mSAN

Maximum FC fabrics attached to a single

N/A 2 N/A N/A N/A N/A 6 N/A N/A
SAN Router

Maximum number FC switches (domains) 12 12 12 12 12 16 16 24 24

in a single FC fabric

Maximum FC switches in all N/A 24 24 N/A N/A 24 24 48 48

interconnected fabrics in an mSAN

Maximum imported FC devices from a

N/A 64 64 N/A N/A N/A 256 504 504
single FC fabric

Maximum imported FC devices from all 64 64 64 64 64 64 256 512 512

FC fabrics in an mSAN

Maximum imported FC devices from all

N/A 64 N/A N/A N/A N/A 256 N/A N/A
FC fabrics from a single FC fabric

Maximum number of (tested) Router

E_Ports connected to a fabric from one or 2 N/A N/A 2 2 N/A N/A N/A N/A
more Routers

Maximum SAN Router R_Ports connected

N/A 2 2 N/A N/A 4 4 6 8
to a single fabric

Maximum FC devices in a single

1,024 1,024 1,024 1,024 1,024 1,024 1,024 2,048 2,048
connected FC fabric

3
M-EOS Fabric Guidelines December 16, 2007
 M-EOS Fabric Guidelines

Table 4 Brocade M1620, M2640, Eclipse 3300, and Eclipse 4300 SAN Routers (continued)

Brocade M1620 Brocade M2640

Eclipse Eclipse
3300, 4300, M-EOSi
M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi 5.0
Metric 4.5 4.7 5.0 4.5 4.4.5 4.6.2 4.7 5.0 FC-HA

Maximum loop devices attached to a

N/A 32 32 N/A N/A 2 32 32 N/A
single SAN Router FL_Port

Maximum loop devices attached to a

N/A 64 64 N/A N/A 24 384 384 N/A
single SAN Router

Zoning

Maximum imported FC devices from a

64 N/A N/A 64 64 64 N/A N/A N/A
single fabric

Maximum zones in a connected FC fabric 512 512 512 512 512 1,024 1,024 2,047 2,047

Maximum iSCSI, iFCP, or FC devices

included in an exportable zone (an N/A 64 N/A N/A N/A N/A 64 N/A N/A
exportable zone across a single iFCP link)

Maximum FC-to-FC devices included in a

N/A 64 N/A N/A N/A N/A 128 N/A N/A
zone

Maximum SAN Router zones 128 128 128 128 128 256 256 256 256
(recommended)

iFCP

Maximum iFCP sessions (initiator-target

pairs)a on a single GE-TCP port 64 64 64 64 64 64 64 64 64

Maximum iFCP sessions (initiator-target

64 64 64 64 64 256 256 256 256
pairs)a per SAN Router

Maximum iFCP point to multipoint remote

8 8 N/A N/A N/A N/A 8 N/A N/A
SAN Router connections per GE-TCP port

Maximum iFCP point to multipoint remote

N/A 16 N/A N/A N/A 32 32 N/A N/A
SAN Router connections per SAN Router

Maximum iFCP point-to-point multipoint

connections (one “site” to many “sites”) N/A 8 8 N/A N/A N/A 8 8 8
per port

Maximum iFCP point-to-point multipoint

connections (one “site” to many “sites”) 8 16 32 N/A N/A N/A 32 32 32
per SAN Router port

iSCSI

Maximum iSCSI sessions (initiator-target

pairs)a on a single GE-TCP port 64 64 64 64 64 64 64 64 64

Maximum iSCSI sessions (initiator-target

64 64 64 64 64 256 256 256 256
pairs)a per SAN Router

Maximum number of iSCSI initiators per

50 50 25 50 50 50 50 25 25
GE-TCP port

Maximum number of iSCSI initiators per

SAN Router 50 50 50 100 200 200 200 200 100

mFCP

Maximum number of SAN Routers in an

1 1 N/A 2 2 2 1 N/A N/A
mSAN

Maximum (tested) mFCP connections

between two SAN Routersb N/A N/A N/A 4 4 4 N/A N/A N/A

FC-HA

4
December 16, 2007 Fabric Guidelines for Brocade M-Series Products
 M-EOS Fabric Guidelines

Table 4 Brocade M1620, M2640, Eclipse 3300, and Eclipse 4300 SAN Routers (continued)

Brocade M1620 Brocade M2640

Eclipse Eclipse
3300, 4300, M-EOSi
M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi M-EOSi 5.0
Metric 4.5 4.7 5.0 4.5 4.4.5 4.6.2 4.7 5.0 FC-HA

Maximum number of SAN routers in an

N/A 1 1 N/A N/A N/A 1 1 2
mSAN

Others

Maximum direct-attached FC, iSCSI, and

N/A 128 128 N/A N/A N/A 512 512 512
imported devices

a With iFCP and iSCSI configurations, each initiator port WWN and target port WWN pair will form a session and will count towards the maximum supported
iFCP+iSCSI sessions. For example, if you have an iFCP shared zone with one server (single HBA WWN) and a JBOD with four disks (four port WWNs), then it
will result in four unique iFCP sessions (TCP connections).
b mFCP ISLs between routers is not supported on the M1620, which prevents more than one M1620 to connect to the same fabric. The limit of two on the
Eclipse 3300/4300 is the tested limit. The primary reason for using multiple routers in the same mSAN is for high-availability configurations.

Brocade EFCM Guidelines

Brocade Enterprise Fabric Connectivity Manager (EFCM) version 9.x is tested and supported to
discover and manage approximately 2,500 ports. The purpose of this section is to provide server
hardware requirements and best practices to achieve this level of scalability. It also describes known
issues you should consider when you deploy Brocade EFCM 9.x.

NOTE: EFCM does not impose any limits on zone activations. Zoning restrictions are imposed by the
hardware or firmware.

Table 5 Requirements for Windows client and server machines

Requirements
Operating System Machine Type
1–512 Ports 513–1,280 Ports 1281–2,500 Ports

2.0 GHz Pentium 4 CPU 3.0 GHz Pentium 4 CPU 3.0 GHz Pentium 4 CPU
Client 1 GB RAM 2 GB RAM 2 GB RAM
512 MB virtual memory 2 GB virtual memory 2 GB virtual memory

2.0 GHz Pentium 4 CPU 3.0 GHz Pentium 4 CPU 3.0 GHz Pentium 4 CPU
Server 1 GB RAM 2 GB RAM 2 GB RAM
Windows 512 MB virtual 2 GB virtual memory 2 GB virtual memory

Combineda
3.0 GHz Pentium 4 CPU 3.6 GHz Pentium 4 CPU
(1 local client and 2 GB RAM 2GB RAM Not Recommended
no remote desktop
2GB virtual memory 2GB virtual memory
clients)

a Windows 2003 Standard or Enterprise Edition preferred

NOTE: A more powerful server may help in managing larger or multiple fabrics in which the discovery
port count exceeds 2,500. However, you may also see impacts to client and server performance
when the fabric experiences rebuilds or malfunctioning devices.

Best Practices
Consider the following best practices when you deploy Brocade EFCM:
• Address all fabric instabilities that include, but are not limited to, switch anomalies, misbehaving
fabric ports, and problematic devices. Events generated from each occurrence will cause the
client Central Processor Unit (CPU) to increase for long periods of time, depending on the
frequency and number of these events.
• Brocade EFCM does not support the addition of a second EFCM server to discover and manage
the same set of ports. Discovering M-Series switches that are managed by another EFCM server
can degrade client performance.

5
M-EOS Fabric Guidelines December 16, 2007
 M-EOS Fabric Guidelines

• Customers with large fabrics with fabric instabilities should consider upgrading the server
platforms meeting specifications greater than those recommended.
• Allow 5 to 10 minutes for server and client to stabilize if a fabric rebuild is encountered.
• Allow 5 to 10 minutes for server and client to stabilize after a discovery schedule has changed
when a switch IP is removed or added to the discovery list.
• Restart the server and client after multiple fabric rebuilds.
• For large fabric with topology updates, restart the server every 7 days.
• Restart the client if responsiveness is slow.
• Restart the client if topology updates are slow to display.
• For large fabrics with frequent topology updates, restart the client every 2 to 3 days.
• For EFCM servers managing multiple fabrics, create a customized view for each fabric.

Known Issues
This section outlines known issues with Brocade EFCM 9.x.
Importing large number of nicknames
Importing a large set of nicknames causes client performance problems where client
responsiveness becomes slow. Also display of the product list and topology is slow when the
nicknames are added. Restart the client to avoid performance problems and view all imported
nicknames. This issue impacts all clients logged in at that time.
Selecting devices from the tree view
Selecting devices from the tree view can cause client performance problems. Allow extra time when
viewing device information from the product tree view.
Moving from View All to Security Tab
When there are large fabrics in the view, it will take some time to move from the View All tab to the
Security tab.
Platform fails to meet minimum client recommendations
For remote client users whose platform does not meet minimum recommendations (a laptop for
example), you can remote desktop into a high-performance platform from which you can launch a
remote client into an EFCM server managing a large fabric. This involves adding a server whose
operating system supports multiple remote desktop sessions, which is limited by the installed
Windows license key.
Caveats:
• If multiple remote clients are launched from the remote desktop server, the server hardware
requirements need to be multiplied by the number of remote client sessions. For example, for a
single remote client, the CPU requirement is 2.0 GHz. If you add a remote client, you would need
4.0 GhZ, and so on.
• The installed Windows license key limits the number of remote desktop session. The
Brocade-supplied 1U server has a limit of two remote desktop sessions, plus the console
session.

6
December 16, 2007 Fabric Guidelines for Brocade M-Series Products
 M-EOS Fabric Guidelines

Remote client configurations

In Figure 1, three remote clients are connected directly to an EFCM server. The advantages are:
• The number or remote client connections is not limited by Remote Desktop Connection (RDC),
but by the EFCM license key. The license key for EFCM Enterprise Base enables 25 clients.
• Uses the minimum EFCM server hardware requirements.
A disadvantage is:
• It uses the recommended or greater hardware requirements for remote clients.

Figure 1. Remote clients connected directly to EFCM server

NOTE: Remote client performance is better in environments with high-bandwidth networks between
the client and server.

Figure 2 illustrates remote clients that do not meet the minimum recommended hardware
requirements and uses a Remote Desktop server. The advantages of this configuration are:
• It uses below the minimum hardware requirements for remote clients.
• It uses the minimum hardware requirements for the EFCM server.
The disadvantage is:
• There is a limited number of remote desktop connections controlled by the installed Windows
license key.

Figure 2. Remote clients connected through a dedicated RDP server

7
M-EOS Fabric Guidelines December 16, 2007
 M-EOS Fabric Guidelines

Performance utilization view

Enabling the performance utilization view (colored “marching ants”), increases the CPU utilization,
and may decrease the scalability potential of EFCM.

Considerations for Using MoM Servers

Management of Managers (MoM) is an EFCM server that discovers one or more other EFCM servers
directly managing fabrics. The MoM server is limited in feature scope—however, it can report on more
ports than an EFCM server directly managing fabrics if a MoM server discovers multiple EFCM servers.
Table 6 Requirements for EFCM MoM server and client machines

Operating System Server and Client 3200+ Port Count

3.0 GHz CPU

MoM server and
Windows 2003 2 GB RAM
local MoM client
2 GB virtual memory

Figure 3 illustrates MoM server setup. The advantages of this setup are:
• The number of remote client connections is not limited by RDP, but by the EFCM license key.
• MoM server and client hardware requirements are less than the requirements for the EFCM
server and client.
The disadvantages are:
• EFCM features not supported in MoM require a remote client for each EFCM server.
• No Element Management capability.
• Support only for fabrics that contain managed M-Series switches.
• No EFCM management support for Security Center, port fencing, or fabric binding.
• No EFCM management support for Show Route.

Figure 3. Remote clients connected directly into a MoM server

8
December 16, 2007 Fabric Guidelines for Brocade M-Series Products
 M-EOS Fabric Guidelines

Non-default EFCM Configuration Changes for Managing Large Fabrics

Modify server memory allocation to 1024 Mb as follows:
1. From EFCM SAN menu, select Options.
2. From the Option dialog, select Software Configuration > Memory Allocation.
3. Modify server memory allocation to 1024 Mb (default is 512).
4. Restart the server.

NOTE: The server memory allocation should never equal or exceed total Random Access Memory
(RAM).

Allocate more client memory as follows:

1. From the EFCM SAN menu, select Options.
2. From the Option dialog, select Software Configuration > Memory Allocation.
3. Modify the client memory allocation to 1024 Mb (default is 512).
4. Restart the client.

Platform Resources
EFCM must be run on a server that meets or exceeds the minimum requirements. If you have a large
fabric (see Table 5), use a server that meets or exceeds the recommended requirements. Brocade
offers a RoHS-compliant 1U EFCM server. Users may also choose to source their own servers.

Recommended Platform Requirements1

• Intel Pentium 4 CPU 3.00 GHz
• 2 GB RAM
• 2x 250 Gb Maxtor SATA HDD (Intel Raid Controller)
• Windows 2003 SP1 Standard Edition (Unit #1)
• Intel PRO/1000 PM NIC (dual)
• Minimum virtual memory 2 GB, recommended 3 GB

Minimum Platform Requirements2

• 1.8 or 2.0 GHz CPU
• 1 GB RAM
• 40 Gb Maxtor IDE HDD
• Windows 2000 SP4 Professional
• Intel PRO/100 NIC
• Minimum virtual memory 1 GB, recommended 1.5 GB

1. The Brocade 1U Server for EFCM meets the recommended platform requirements. The Brocade
1U Server is RoHS compliant.
2. This original 1U (non-RoHS compliant) meets the minimum recommended requirements for small-
to medium-size fabrics.

9
M-EOS Fabric Guidelines December 16, 2007
 M-EOS Fabric Guidelines

10
December 16, 2007 Fabric Guidelines for Brocade M-Series Products