Interfabric routing header for use with a backbone fabric

• US 8,532,119 B2
• Filed: 07/30/2004
• Issued: 09/10/2013
• Est. Priority Date: 07/30/2004
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Brocade Communications Systems, Inc. (Broadcom, Inc.)
• Inventors: Snively, Robert Norman, Wilson, Steven L., McClanahan, Edward D., Makishima, Dennis Hideo, Chung, Daniel Ji Yong Park
• Primary Examiner(s): Sheikh, Ayaz
• Assistant Examiner(s): AGA, SORI A
• Application Number:
  US10/903,899
• Publication Number:
  US 20060023708A1
• Time in Patent Office: 3,329 Days
• Field of Search: None
• US Class Current: 370/401
• CPC Class Codes: H04L 2212/00 Encapsulation of packets
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00

Abstract

A Fiber Channel router used to join fabrics. EX_ports are used to connect to the fabrics. The EX_port joins the fabric but the router will not merge into the fabric. Ports in the Fiber Channel router can be in a fabric, but other ports can be connected to other fabrics. Fiber Channel routers can be interconnected using a backbone fabric. Global, interfabric and encapsulation headers are developed to allow routing by conventional Fiber Channel switch devices in the backbone fabric and simplify Fiber Channel router routing. Phantom domains and devices must be developed for each of the fabrics being interconnected. Front phantom domains are present at each port directly connected to a fabric. Each of these is then connected to at least one translate phantom domain. Zoning is accomplished by use of a special LSAN zoning naming convention. This allows each administrator to independently define devices are accessible.

Claims

1. A switching device comprising:

a first ingress module configured to be connected to a first network and further configured to;

receive a first packet from a first device in the first network,

change a destination address of the received first packet from a first phantom address corresponding to a second device in the first network, the phantom address being valid only in the first network, to an identifier of the second device valid only in a second network, wherein the second device is located in the second network and wherein the second network is coupled to the first network by a backbone network, and

encapsulate the received first packet within an encapsulation packet such that the payload of the encapsulation packet comprises the received first packet, wherein the encapsulation packet is of the same protocol as the received first packet;

a first egress module configured to be connected to the backbone network and further configured to;

receive the encapsulation packet from the ingress module, and

pass the encapsulation packet to the backbone network;

a second ingress module configured to be connected to the backbone network and further configured to;

receive from the backbone network a second encapsulation packet having as a payload a second packet, wherein the second encapsulation packet is of the same protocol as the second packet,

recover the second packet from the encapsulation packet, and

change a source identifier of the recovered second packet from an identifier of the second device in the second network, wherein the identifier of the second device in the second network is valid only in the second network to a phantom address in the first network of the second device, wherein the phantom address is valid only in the first network; and

a second egress module configured to be connected to the first network and configured to receive the recovered second packet from the ingress module and pass the recovered second packet to the first device.

2. The switching device of claim 1 wherein the first ingress module and the second egress module are coupled to a first common physical port of the switching device and wherein the second ingress module and the first egress module are coupled to a second common physical port of the switching device.

3. The switching device of claim 1 wherein:

the first, second, and backbone networks are Fibre Channel fabrics,

the packets are Fibre Channel packets, and

the first ingress module encapsulates the first received Fibre Channel packet within an encapsulation packet at least by adding an encapsulation header to the first received Fibre Channel packet.

4. The switching device of claim 3 wherein the first ingress module encapsulates the first received Fibre Channel packet within an encapsulation packet by further adding a fabric routing header to the first received Fibre Channel packet.

5. The switching device of claim 1 wherein:

the first, second, and backbone networks are Fibre Channel fabrics,

the packets are Fibre Channel packets, and

the switching device recovers the second Fibre Channel packet from the encapsulation packet at least by stripping an encapsulation header from the encapsulation packet.

6. The switching device of claim 5 wherein the switching device recovers the second Fibre Channel packet from the encapsulation packet by further stripping a fabric routing header from the encapsulation packet.

7. The switching device of claim 6 wherein the phantom address in the second fabric of the first device is derived at least in part from information contained in the fabric routing header.

8. A method comprising:

receiving a first packet from a first device in the first network,

changing a destination address of the received first packet from a first phantom address corresponding to a second device in the first network, the phantom address being valid only in the first network, to an identifier of the second device valid only in a second network, wherein the second device is located in the second network and wherein the second network is coupled to the first network by a backbone network,

encapsulating the received first packet within an encapsulation packet such that the payload of the encapsulation packet comprises the received first packet, wherein the encapsulation packet is of the same protocol as the received first packet, and

passing the encapsulation packet to the backbone network; and

receiving from the backbone network a second encapsulation packet having as a payload a second packet, wherein the second encapsulation packet is of the same protocol as the second packet,

recovering the second packet from the encapsulation packet, and

changing a source identifier of the recovered second packet from an identifier of the second device in the second network, wherein the identifier of the second device in the second network is valid only in the second network to a phantom address in the first network of the second device, wherein the phantom address is valid only in the first network; and

passing the recovered second packet to the second device.

9. The method of claim 8 wherein:

the first, second, and backbone networks are Fibre Channel fabrics,

the packets are Fibre Channel packets, and

encapsulating the received first Fibre Channel packet comprises adding an encapsulation header and a fabric routing header to the received first Fibre Channel packet.

10. The method of claim 8 wherein:

the first, second, and backbone networks are Fibre Channel fabrics,

the packets are Fibre Channel packets, and

recovering the second Fibre Channel packet from the second encapsulation packet comprises stripping an encapsulation header and a fabric routing header from the second encapsulation packet; and

changing the source identifier of the recovered second Fibre Channel packet further comprises deriving the phantom address from information contained in the fabric routing header.