AR/DAT(Autonomous Regions with Domain Address Translation)

Native FC Solution

LightSand Communications

Why thinking AR?• It Resolves

– Scalability Issue• Number of switches in the fabric

• Number of devices in the fabric

• Recourses: NS, Zoning database size

– Traffic disruption• Fabric reconfiguration

• Node join / leave

– SAN over WAN? • Latency, bandwidth and more

• AR are already in standard, just needs to be more precisely defined

• Utilizes existing routing mechanisms and services

• Absolutely backward compatible

• Brings the same functionality as other approaches

Media Independent Backbone

BB: FSPF, NS, …

FC-PH .

FC Emulation .

Physical media

AR0 - Backbone

AR1 AR2

BSW1 – Boarder Switch1

BSW2 – Boarder Switch2

• AR1,AR2 – are Fabrics absolutely compliant with FC-SWx, FC-GSx

• The main functionality absorbed by BSW and optional for implementation

Who cares – what’s outside?

FC Switch

Director

FC Switch

Server

Storage

Server

BSW

0xFFFFVirtual devices

In xx Domain Space

E-Port

ARx

DID = xx

BSW – Termination Point

ARx AR0Backbone

DID = x DID = yFabric Services

BBServices

FSPFAR

FSPFBB

Address Mapper (DAT)

Zoning

NS BB NS

Local and Remote Topologies

WAN

AR2Department 2

AR1Department 1

AR0BB

AR3Backup Facility

AR/DAT Advantages• Native FC Architecture based on current standards

• No changes in FC-PH or FC-FS

• AR are independent full function FC Fabrics

• 100% backward compatibility

• BSW takes care of all inter-AR communications

• BSW is optional functionality

• Virtually endless scalability

• Improved security, manageability and performance