Brocade Data Center Ready

Compatibility Test Report: SAN Extension

Alcatel - Lucent 1830 PSS with 11QPA4 card

Document Revision:

1.0

Test completion date:

10/07/2011

Prepared by:

Edward G. Tuazon

Brocade Confidential

Brocade Data Center Ready

2007 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the Brocade B weave logo, Fabric OS, File Lifecycle Manager, MyView, Secure Fabric OS, SilkWorm, and
StorageX are registered trademarks and the Brocade B wing logo 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.

Compatibility Test Report: SAN Extension

Page 2

Brocade Confidential

INTRODUCTION

1.1

Introduction

Brocade Data Center Ready

This report captures the results of the test performed for compatibility with the Alcatel-Lucent
1830 PSS and 11QPA4 card. The tests were conducted with a 16 slot Shelf, the PSS-16,
that runs the same software as the 32 slot shelf, the PSS-32.
This document covers the following areas:

Product & Technology Overview

Test Methodology

Configurations Tested

Test Procedures

Test Bed Data & Test Results

PRODUCT & TECHNOLOGY OVERVIEW

The Alcatel-Lucent 1830 Photonic Service Switch (PSS) product family provides
increased network flexibility and operational automation through zero-touch, transparent
photonic networking. Photonic networks use simplified and accelerated operations to
transform wavelength division multiplexing (WDM) into true transport networking with
advanced flexibility, performance, automation, and integration.
Alcatel-Lucent 1830 PSS product family includes the following:
Universal slot-based shelves
Alcatel-Lucent 1830 PSS-36 Shelf
Alcatel-Lucent 1830 PSS-32 Central Office Shelf
Alcatel-Lucent 1830 PSS-16 Central Office Shelf
Alcatel-Lucent 1830 PSS-4 Shelf
Edge device (1 RU) shelves
Alcatel-Lucent 1830 PSS-1 GBEH Edge Device
Alcatel-Lucent 1830 PSS-1 MD4H Edge Device
Alcatel-Lucent 1830 PSS-1 MSAH Edge Device
Alcatel-Lucent 1830 PSS-1 AHP amplifier

The testing with Brocade systems was conducted on the Alcatel-Lucent 1830 PSS-16
that uses the same software releases as the PSS-32.

Compatibility Test Report: SAN Extension

Page 3

Brocade Confidential

Brocade Data Center Ready

The Alcatel-Lucent 1830 PSS-16 shelf supports:

16 paired half height application cards (or 8 full height application cards)
2 equipment controllers (EC)
2 redundant power input filters
1 user panel (occupies one of the paired application card slots)
1 fan tray
The 16 universal slots are arranged in two rows of 8, on either side of each other. There
are 21 total slots, including slots for Equipment Controllers, Power Filters, and fans. Slots
are numbered 1 through 21 as illustrated in the following figure,

Compatibility Test Report: SAN Extension

Page 4

Brocade Confidential

Brocade Data Center Ready

The 11QPA4 is a 10G, Quad port, any rate module with four client interfaces. This
module supports four independent multi-rate 10G channels. The 11QPA4A is the
temperature hardened version of this module.
The 11QPA4(A) has four pluggable client interfaces (C1, C2, C3, and C4), four pluggable
line interfaces (L1, L2, L3 and L4) and four VOA sockets (VA1, VA2, VA3 and VA4). The
pack has a status LED, but does not support status LEDs for the optical ports and VOA
ports due to physical limitations on the faceplate, but the WEBUI does support LED
status for all ports.
The 10G pluggable line port of the 11QPA4(A) supports 88 channels when configured
with a tunable XFP. When configured with a fixed channel XFP, only 44 even channels
are supported. Fixed odd channel XFPs are not supported. The fixed channel XFPs
supported on these line ports are not wavelength locked, therefore traffic from these
XFPs may only traverse 100 GHz systems.
The client side supports the following functional features:
The client side supports four B&W or CWDM XFPs
The following Client signal types are supported for each channel: OC-192, STM-64,
10GbEWAN PHY, 10GbE LAN PHY, OTU-2 with G.709 FEC (10.709,
11.04,11.09,11.31,11.27), 10G/8G Fibre Channel (8G FC requires SFP+ or 8G FCcapable XFP)
The line side supports the following functional features:
The module is equipped with four SFP cages, which are shared by slow eVOA for
output power equalization, and fast eVOA for WT encoding.
The line signal of each channel is OTU2 with provisionable RS-FEC or EFEC (AMCC
EFEC and ALU EFEC).
11QPA4 Pack

The configuration for these tests were point to point network testing the transport of
8GFC and 10GFC across the 11QPA4 optical transponder packs between a pair of PSS16 systems. A single 11QPA4 pack support the transport of up to four transponder
functions (8GFC or 10GFC or 10GbE) simultaneously, Each transponder function is
handled by a separate 11G WDM wavelength using a line XFP. Fixed wavelength XFPs
were used for this test.
Since the protection switch testing was already completed by ALU as part of self-testing
with the Brocade 5100, the multiple wavelengths were passed over separate 50 km fibers
to test Brocade Frame trunking.

Compatibility Test Report: SAN Extension

Page 5

Brocade Confidential

Brocade Data Center Ready

TEST METHODOLOGY
Begin by identifying the objectives, functionality, and interface requirements of the Device
Under Test (DUT), paying particular attention to the areas that relate directly to its interface
with the Brocade product.

For a DUT with a Fibre Channel (FC) interface, start by testing a single DUT interface port for
correct and consistent initialization of the port on selected Brocade switches.

Perform login testing to verify correct speed negotiation, link initialization, fabric login, name
server registration, state change registration, and acknowledgements. Introduce errors, such
as cable pulls and switch resets, during the login.

Next, perform target discovery and I/O traffic. Introduce errors to test these areas: monitoring
of data corruption, I/O stoppage, and throughput changes.

Introduce the DUT into a larger configuration consisting of multiple Brocade switches, storage
systems, and host types. Test relevant features and functionality of the DUT and compatibility
of the DUT with the Brocade product. Add multiple host OS and storage LUNs as appropriate.
Introduce errors, such as Inter-Switch Link (ISL) toggling and principal switch reset, to verify
stability of the DUT.

Run traffic for longer periods to check consistent I/O throughput and sustainability.
NOTE: During the testing period, work with the Partner to ensure the relevance of test
procedures and made modifications as required.

CONFIGURATIONS TESTED
The following sections describe and illustrate topologies used in testing.

4.1

Flat-fabric Topologies
Flat-fabric topologies are connected through the DUT using FC and/or Fibre Channel over IP
(FCIP). Switches tested should merge into a single unified fabric.

Figure 1. Basic link initialization test configuration (FC port and FCIP port)

Compatibility Test Report: SAN Extension

Page 6

Brocade Confidential

Brocade Data Center Ready

Figure 2. Large-fabric configuration (FC and FCIP)

4.2

Routed Topologies
These topologies route FC frames across independent fabrics through the DUT. Test
configurations include Fibre Channel Routing (FCR) backbone over distance using FC/FCIP ISL
connections as well as FCR edge extension over distance using Inter-Fabric Link (IFL)
connections.

Figure 3. Basic link initialization test configuration (FC port and FCIP port)

Compatibility Test Report: SAN Extension

Page 7

Brocade Confidential

Brocade Data Center Ready

Figure 4. Large-fabric configuration (FC and FCIP)

TEST PROCEDURES

5.1

Link Initialization
Link initialization is allowed to complete when switches are connected through the DUT. The
DUT can optionally participate in ELP exchange and then enter a pass-through state after link
reset. In either case, the fabric is allowed to successfully merge and pass FC traffic. This
section focuses on tests for compatibility as well as robustness.
Each switch in the Data Center Ready test bed should be verified to operate correctly when
connected directly to the DUT. The following scenarios should be tested where available.

5.1.1

Single ISL Link Initialization

Verify that link initialization completes successfully for the DUT. Operation may vary
depending on DUT and switch operating parameters. After a successful merge, pass traffic
across the data link to verify correct operation.

5.1.2

Multiple ISL Link Initialization

Verify that two or more FC or FCIP ISLs can be established through the DUT. After a successful
merge, pass traffic across the data link to verify correct operation.

5.1.3

IFL Link Initialization

Verify that link initialization can complete across IFLs (FC and/or FCIP) through the DUT. After
a successful merge, pass traffic across the data link to verify correct operation.

5.1.4

Mismatched Fabric Operation Parameters

Observe the outcome of interconnecting two switches through the DUT with mismatched
fabric operating parameters. Under normal circumstances, the ISL/IFL should segment and
fabrics should remain separate, but this may not be the case. Note any cases where the
fabric merges successfully with mismatched parameters.

Compatibility Test Report: SAN Extension

Page 8

Brocade Confidential

5.2

Brocade Data Center Ready

SpinFab (if supported)

SpinFab is a Fabric OS (FOS) diagnostics utility (FC only) that can be used to verify ISL and
trunk group operation. Routing is set up so that frames received on each ISL are
retransmitted on the same ISL port. Several frames are then transmitted through ISLs so that
they circulate back and forth until the test stops. While frames are circulating, the RX frame
count, port CRC, and encoding error statistics are monitored for errors.
SpinFab should be executed from the switch directly connected to the DUT with a frame
circulation count of 1000 million frames. (The test may be terminated after two hours.) Verify
successful completion of test and monitor portStatsS
portStatsShow
StatsShow output for DUT connected ports.
Since SpinFab may not operate as desired through all tested equipment, firmware revisions,
or fabric configuration settings, it is the responsibility of the Test Engineer to ascertain the
validity of the test.
Example: switch# spinfab nmegs 1000

5.3

Speed Negotiation
Verify the ability of the DUT to perform speed negotiation (FC only) when a Brocade switch
port is configured for auto-negotiation. Many Metro Area Network (MAN)/Wide Area Network
(WAN) devices do not perform speed negotiation as defined in FC-FS standards and should be
permitted to pass when a port is locked at the desired speed.
1. If auto-negotiation is set, verify the ability of the device to negotiate to the highest supported
speed and perform link initialization.
2. If Speed Locked FC is supported, verify the ability of the device to enter online state and perform
link initialization.

5.4

Trunking over Distance

Some fabric configurations may support the use of Dynamic Path Selection or Brocade ISL
trunking through the DUT. Support should be determined on a case-by-case basis depending
on the functional operation of the DUT and successful completion of test cases.

5.4.1

Dynamic Path Selection (if supported)

Verify the ability to perform Dynamic Path Selection (multiplexing FC frames across multiple
ISLs based on exchange ID) over multiple ISL/IFL through the DUT and simulated long
distance network. Verify in-order delivery of all traffic crossing the trunks using host/target or
traffic generator with out-of-order delivery notification.

5.4.2

Brocade ISL Trunking (if supported)

Verify the ability to perform ISL Trunking (multiplexing FC frames across multiple ISLs at the
frame level) through multiple E_Ports or EX_Ports over the DUT and simulated long-distance
network. Due to strict requirements of ISL trunking, only certain configurations are supported.
Trunking at frame level requires 2 Gbit/sec FC speeds and identical length fibers (latency
restriction) between end points.
The DUT cannot buffer frames as they are received, and out-of-order delivery may result.
Verify in-order delivery of all traffic crossing the trunks using host/target or traffic generator
with out-of-order delivery notification.

Compatibility Test Report: SAN Extension

Page 9

Brocade Confidential

5.5

Brocade Data Center Ready

Link-down Notification
When a failure occurs on the long haul network or remote switch ISL port, the local switch ISL
port should be notified by the DUT that the path is no longer available by sending NOS/OLS or
shutting off its laser. If this function does not occur, fabric services and connected devices
may become unstable.

5.6

Port Disable/Enable
An FC or FCIP port that is disabled should cause the associated ISL/IFL to go offline. This
should be observed through the perspective of both previously interconnected switches. Link
initialization should occur once the port is re-enabled and the ISL/IFL should become
available for transport of frames.
Vary the amount of time between when a port is disabled and then re-enabled (for example,
0, 20, and 300 seconds between disabling a port and re enabling the port) in order to cover
different scenarios. Repeat each instance of the test a number of times in order to verify
consistency. Test both principal and subordinate ISLs.

5.7

Port Cable Toggle

Disconnecting the fiber connecting the switch to the DUT should cause the associated ISL/IFL
to enter offline state. This should be observed through the perspective of both previously
interconnected switches. Link initialization should occur once the fibre is re-connected and
the ISL should become available for transport of frames.

5.8

WAN Port Cable Toggle

Disconnecting or disabling the WAN side interface between test devices (so that switches are
physically separated) should cause the associated ISL/IFL to enter offline state. This should
be observed through the perspective of both previously interconnected switches. Link
initialization should occur once the path is re-established and the ISL should become
available for transport of frames.
When a failure occurs on the long haul network, the local switch ports should be notified in
some way via the DUT that the path is no longer available. This can be accomplished by
transmitting NOS/OLS or shutting off its laser.

5.9

WAN Side HA Failover

Some FC extension devices may provide protection-switching capabilities on the long haul
network in order provide increased availability. If it is available, protection switching should be
tested to verify correct operation and survivability of ISL/IFL.

5.10

Impaired Network Stability

Since some devices (that is, FCIP) may be designed to operate over impaired networks, test
fabric stability during worst-case conditions. It may also be of interest to determine FC
performance under impaired network conditions. Perform this test if equipment is available.

5.11

Fabric Services
Test basic fabric services possibly incorporated into previous test cases, in order to verify
fabric operation and stability. This includes, but is not limited to, zone merges, name server,
and Registered State Change Notification (RSCN) propagation.

Compatibility Test Report: SAN Extension

Page 10

Brocade Confidential

Brocade Data Center Ready

5.11.1 Zone Merge

Verify the ability to perform a zone merge of a large database across the DUT.

5.11.2 Name Server

Verify name server updates occur as appropriate to switches in the test fabric when a new
device is added or removed.

5.11.3 State Change Notification

Verify that when a target is removed from the fabric, a zoned initiator is notified through the
DUT via the RSCN mechanism.

5.12

Switch Device Reboot

Rebooting various switches in the test fabric should deliver expected results, including fabric
reconfiguration and temporary separation from the remote fabric(s). After the rebooted switch
comes back online, fabric merge should occur and the entire fabric should become stabilized.

5.13

DUT Device Reboot

Rebooting the device under test should cause temporary fabric segmentation. Once the
device enters operational state, a merge should occur and the entire fabric should become
stabilized.

5.14

Extended Duration Test

Pass traffic (host/target or data generator) through the test fabric and DUT for more than 12
hours to verify stability and minimal bit or frame-level errors. Collect statistics for port
throughput and port error counter.

5.15

Partner-Unique Features
Some devices may provide additional features of interest to validate compatibility with
Brocade switches.

5.16

Application Testing
Validate basic operation of a real-world application in the test configuration. Since many SAN
extension devices are used for business continuance solutions, data replication or remote
tape backup applications would be an optimal choice.

Compatibility Test Report: SAN Extension

Page 11

Brocade Confidential

Brocade Data Center Ready

TEST BED DATA AND TEST RESULTS

6.1

Contact Details
Alcatel Lucent

Test Requestor

6.2

Brocade Data Center

Ready Lead

Edward G. Tuazon, 408-333-5528

Partner Contact

Carl Krentz, 613-784-3209

Device Under Test (DUT) Details

Product

1830 PSS-16

Card(s)

11QPA4

Protocol

FC

Revision

V3.5.96
65 km

Distance Tested
Comments

6.3

Brocade Products
Switch Model
DCX/DCX-4S

Version
V7.0.0

Protocol

Comments

FC

Brocade always recommends hard setting port speed on extended fabrics E_Ports connected
across WDM networks.

Compatibility Test Report: SAN Extension

Page 12

Brocade Confidential

Brocade Data Center Ready

The DUT may operate under various configurations or modes and require different switch
configuration parameters for each mode. Tested configurations are noted below. Some
commonly modified switch configuration parameters for FOS switches include:

Extended Fabrics Mode

ISL R-RDY Mode

The total set of tested E_Port credit model modes are L0 (normal), LD, and LS. LD mode
operates by dynamically allocating credit based on the ASIC round-trip timer up to a specified
maximum distance (km) defined by the user. LD mode uses a Virtual Channel (VC) credit
model. LS mode is similar to LD mode, but allocates buffers based only on the distance (km)
specified by the user. No round-trip timer is used and the user has the option to over-allocate
buffers for the port (for example, some devices may use only a 1024-byte data field size thus
requiring double the amount of credits normally required). LS mode also uses a VC credit
model by default, but ISL R_RDY mode can be enabled and used in conjunction with LS mode
if inter-connecting devices require R_RDY flow control or idle fill words.

6.4

Brocade Dynamic Path Selection (exchange based trunking) only

BLOOM-based switch platforms and FOS releases prior to 5.1.0 require

fabric.ops.mode.longDistance=1.

Test Cases and Results

#

Test Case

Result
(Pass/Fail)

11QPA4 @8G

11QPA4@10G

5.1

Link Initialization

pass

pass

pass

5.2

SpinFab

pass

pass

pass

5.3

Speed Negotiation

pass

pass

pass

5.4

Trunking Over Distance

pass

pass

not supported on
Brocade DCX card

5.5

Link Down Notification

pass

pass

pass

5.6

Port Disable/Enable

pass

pass

pass

5.7

Port Cable Toggle

pass

pass

pass

5.8

WAN Port Cable Toggle

pass

pass

pass

Compatibility Test Report: SAN Extension

Page 13

Brocade Confidential

6.5

Brocade Data Center Ready

5.9

WAN Side HA Failover

n/a

Note 1

Note 1

5.10

Impaired Network Stability

n/a

n/a

n/a

5.11

Fabric Services

n/a

n/a

n/a

5.12

Switch Device Reboot

pass

pass

pass

5.13

DUT Device Reboot

pass

pass

pass

5.14

Extended Duration Test

pass

pass

pass

5.15

Vendor Unique Features

n/a

n/a

n/a

5.16

Application Testing

n/a

n/a

n/a

5.x

Additional Testing

n/a

n/a

n/a

Additional Notes:
System Configuration:
Two separate 65 km links used to verify trunking. The DCXs Directors were equipped with
850 nm Brocade branded SFPs and connected the 11QPA4 cards client side with multi
mode fiber cables. The ALU card uses 10G XFPs which can be optioned to run either at
8G or 10G rate. The tested configuration is a point to point system which does not utilized
the used of DWDM devices on the line side. Protection Switching (PS) on the DCX were
not verified as no ALU PS cards were available. Trunking is not supportedat 10G on the
Brocade DCX.
Port Configuration:
The following settings were used to configure the DCX ports at 8G:
a.

Portcfgspeed port number, hard set speed at 8G

b.

Portcfggport port number

c.

Portcfgfillword port number, fillword = 3

d.

Portcfglongdistance port number LS 1 65

Compatibility Test Report: SAN Extension

Page 14

Brocade Confidential

Brocade Data Center Ready

The following settings were used to configure the DCX FC10-6 port at 10G
a.

Portcfglongdistance 3/0 LS 1 65

Port settings below is not supported at 10G rate:

b.

Portcfgspeed 3/0 , not applicable at 10G

c.

Portcfgfillword 3/0, not supported

d.

Portcfggport 3/0, not supported

1. WAN side HA failover: not tested on Brocade DCX- ALU had completed self-test
on Brocade 5100.
Attached are the isl & trunkshow information for the ports tested @ 8G. Trunking does not apply to
10G for the Brocade DCX.
DCR-S12-DCX22:admin> islshow
1: 17-> 1 10:00:00:05:1e:44:10:00 3 DCR-S10-DCX40 sp: 8.000G bw: 16.000G TRUNK
CR_RECOV
DCR-S12-DCX22:admin> trunkshow
1: 17-> 1 10:00:00:05:1e:44:10:00 3 deskew 18 MASTER
16-> 0 10:00:00:05:1e:44:10:00 3 deskew 15

Compatibility Test Report: SAN Extension

Page 15