Method and system for supporting distance extension in networks having Y-cable protection

Description

BACKGROUND OF THE INVENTION

The present invention relates generally to data networking and, more specifically, to Y-cable protection enhancement in supporting Fibre Channel distance extension.

SONET/SDH and optical fiber have emerged as significant technologies for building large scale, high speed, Internet Protocol (IP) based networks. SONET, an acronym for Synchronous Optical Network, and SDH, an acronym for Synchronous Digital Hierarchy, are a set of related standards for synchronous data transmission over fiber optic networks. SONET/SDH is currently used in wide area networks (WAN) and metropolitan area networks (MAN). A SONET system consists of switches, multiplexers, and repeaters, all connected by fiber. The connection between a source and destination is called a path.

One network architecture for the network interconnection of computer devices is Fibre Channel, the core standard of which is described in ANSI (American National Standards Institute) X3.230-1994. The Fibre-Channel standard defines a bi-directional link protocol, used to connect computers to disk drives and other peripherals. Arising out of data storage requirements, Fibre Channel currently provides for bi-directional gigabit-per-second transport over communication networks in Fibre Channel frames that consist of standardized sets of bits used to carry data over the network system. Fibre Channel links are limited to no more than 10 kilometers.

New standards and protocols have emerged to combine the advantages of the SONET/SDH and Fibre Channel technologies. For example, it is sometimes desirable to link two SANs (Storage Area Networks), which operate with Fibre Channel protocol, over a MAN (Metropolitan Area Network), or even a WAN (Wide Area Network), which typically operates under SONET or SDH standards. The advent of high data rate metropolitan optical networks including such networks based on the use of dense wave division multiplexing (DWDM) and/or SONET/SDH transport systems makes it possible to extend so-called storage area networks (SANs) that carry multiple Fibre-Channel links over distances much longer than 10 kilometers. This extension of Fibre Channel from 100 kilometers to over several hundred, or even thousand, kilometers, is made by mapping Fibre Channel ports to a SONET/SDH path for transport across a SONET/SDH network.

Y-cable protection scheme in Fibre Channel is designed as one way traffic protection. Near End (NE) equipment and Far End (FE) equipment within a network can provision Y-cable differently and can act independently. This means that NE and FE equipment may be in different configurations and in different states (e.g., Manual Switch/Forced Switch/Reverse Request, Active/Standby State, Working/Protect, etc.). Due to the nature of Fibre Channel, when Fibre Channel Distance Extension (DE) is enabled, DE control state machine has to be working only with bi-directional traffic. This requires the NE trunk to communicate with the FE trunk over a SONET path and both receive and transmit Fibre Channel traffic have to go through the same path (trunk).

There is, therefore, a need for a method and system that allows Distance Extension, or other features requiring bi-directional traffic, to function properly in networks configured for one-way traffic protection such as Y-cable protection.

SUMMARY OF THE INVENTION

A method and system for communicating state information between a local device and a remote device across a transport network are disclosed. Each of the devices operate independently from one another and at least one of the devices is configured for one-way traffic protection. The method includes receiving a protection message comprising K-bytes from one of the local and remote devices at the other of the local and remote devices and determining, based on the received K-bytes, if there is a change in state at one of the devices. If a change in state is detected, a message is sent indicating the change in state from one of the local and remote devices to the other of the local and remote devices.

In another aspect of the invention, a computer program product for communicating between a local device and a remote device across a transport network generally comprises: code that receives a protection message comprising K-bytes from one of the local and remote devices at the other of the local and remote devices; code that determines if there is a change in state at one of the devices; if a change in state is detected, code that sends a message indicating the change in state from one of local and remote devices to the other of local and remote devices; and a computer-readable storage medium that stores the codes.

Further understanding of the nature and advantages of the inventions herein may be realized by reference to the remaining portions of the specification and the attached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts a network architecture to which embodiments of the present invention may be applied.

FIG. 1B is a block diagram illustrating details of a line card of one of the nodes of the network shown in FIG. 1A.

FIG. 2 is a flowchart illustrating a process of the present invention for passing state information between NE and FE equipment in Distance Extension enabled mode.

FIG. 3 is illustrates details of K-byte compression according to one embodiment of the present invention.

FIG. 4 is block diagram of a computer system that can be utilized to execute software of an embodiment of the present invention.

Corresponding reference characters indicate corresponding parts throughout the several views of the drawings.

DESCRIPTION OF SPECIFIC EMBODIMENTS

The following description is presented to enable one of ordinary skill in the art to make and use the invention. Descriptions of specific embodiments and applications are provided only as examples and various modifications will be readily apparent to those skilled in the art. The general principles described herein may be applied to other embodiments and applications without departing from the scope of the invention. Thus, the present invention is not to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features described herein. For purpose of clarity, details relating to technical material that is known in the technical fields related to the invention have not been described in detail.

A method and system of the present invention allow Distance Extension to function properly in networks configured for Y-cable protection. As previously discussed, NE (Near End) and FE (Far End) equipment can provision Y-cable protection differently and act independent from one another, resulting in the equipment having different configurations or protection states. This may cause problems when Fibre Channel Distance Extension (DE) is enabled since a DE control state machine works only with bi-directional traffic. It is to be understood that Fibre Channel Distance Extension is only one example and that the invention may be used with other features that require NE and FE equipment, which may be operating in different configurations or states (due to Y-cable protection or other one-way traffic protection schemes), to communicate with bi-directional traffic going through the same path.

As described in detail below, the present invention passes information between the NE and FE equipment so that they can communicate with each other and determine whether they need to change protection states or take other action, such as initiate an alarm. In one embodiment, a SONET protection K-byte scheme, as described in GR-253 “Generic Requirements for Synchronous Optical Network (SONET) Transport Systems”, is used to allow NE and FE equipment to communicate with each other and make state change decisions accordingly or raise alarms in DE enabled mode. The invention may be implemented, for example, in a Muxponder 2.5 G card over a SONET/SDH network.

Referring now to the drawings, and first to FIG. 1A, an exemplary network is shown with Fibre Channel ports connected over a SONET/SDH transport network. In the present example, the ports operate under Fibre Channel protocol. It is to be understood, however, that the ports may also operate under other frame-based protocols, such as gigabit Ethernet, in accordance with the present invention.

A bi-directional link 10 interconnects Fibre-Channel ports coupled to Near End equipment (local device) 16 and Far End equipment (remote device) 18, carrying Fibre-Channel frames encapsulated within packets. It is to be understood that either device may be referred to as a local device with the other device referred to as a remote device. The link 10 can be either an actual physical link or a tunnel through a network cloud (e.g., SONET/SDH network 14). The SONET/SDH network 14 provides a transport path to connect the NE equipment 16 to the FE equipment 18. Optical transport platforms such as ONS 15454 (available from Cisco Systems, Inc. of San Jose, Calif.), may be used to provide the interface between the Fibre Channel and SONET/SDH networks.

Transport network interfaces interface Fibre-Channel ports at equipment 16, 18 to bi-directional link 10. The Fibre Channel ports are associated with elements which are interconnected by Fibre Channel. These elements include data storage elements, including disk drive arrays, RAIDs, disk farms, or possibly Fibre Channel network elements, such as routers, switches, or other Fibre Channel network elements.

GFP (Generic Framing Protocol) may be used as the framing protocol for such a network for encapsulating the Fibre Channel payloads at one end of the SONET/SDH network 14 to be transmitted across the SONET/SDH network and for decapsulating the Fibre Channel data at the other end. In one embodiment, data is transferred through GFP messages, as described in U.S. Patent Application Publication No. 20050002338 (Devdas et al., filed Jan. 6, 2005), which is incorporated herein by reference in its entirety. It is to be understood that GFP is only one example of a protocol that may be used to transfer the K-bytes and that other protocols may be used without departing from the scope of the invention.

FIG. 1B illustrates detail of one embodiment of a line card 30 (e.g Input/Output (I/O) card) located at the NE and FE equipment 16, 18 and configured to implement the present invention. The line card 30 includes a protection mechanism 32 and a distance extension mechanism 34. The protection mechanism 32 includes a switch agent which sends control commands to a driver. The distance extension mechanism comprises a Buffer to Buffer (B2B) state machine which operates to receive K-bytes from the driver and create messages identifying the state of the equipment coupled to the line card. As described below, software in NE and FE equipment 16, 18 uses these K-bytes to communicate with each other to determine whether there is need to do a protection switch or raise alarms.

FIG. 2 is a flowchart illustrating a process of the present invention for passing information between NE and FE equipment 16, 18 for Y-cable protection in Distance Extension enabled mode. At step 40, the protection mechanism 32 sends control commands to the driver to give K-bytes to transmit when needed. The driver sends these K-bytes through a state machine message exchange in the distance extension mechanism 34 (step 42). The protection mechanism polls the messages at set intervals (e.g., every 5 ms) to see if there are any changes in K-bytes from the protection mechanism's message (step 44). If there is a change in state, an alarm may be set, a message may be sent back to the other device, or both actions may occur (steps 46 and 48). For example, when one of the devices 16, 18 receives a K-byte message and identifies a state change, the device may raise alarms and send an updated K-byte message back. The protection mechanisms 32 at the NE and FE equipment 16, 18 then communicate to determine which device should change its state or configuration or other action to be taken, such as raise an alarm.

Examples of an internal User Defect Alarm that may be used to inform the switch agent of K-byte changes are as follows:

USER_K1_BYTE_CHANGE

USER_K2_BYTE_CHANGE

In one embodiment, a 16 bit message is used to pass information between the FE and NE equipment card. In one example, 4 bits are reserved for future state machine use and 12 bits are used for K-byte handling.

K-byte compression is preferably implemented as shown in FIG. 3. The compression is based on the following:

• • K1, bits 5-8 indicate the requesting channel.
  • K2, bits 1-4 indicate the current channel.
  • K2, bit 5 chooses between 1+1 and 1:n.
  • K2, bits 6-8 indicate the operating mode.
    In one example, two channels are used so only one bit is needed for bits 5-8 of K1 and 1-4 of K2. If only 1+1 protection is used, zero bits are needed for bit 5 of K2. If only two codes are defined for the operating mode (e.g., unidirectional and bi-directional), only one bit is needed for bits 6-8 of K2.

FIG. 4 shows a system block diagram of computer system 60 that may be used to execute software of an embodiment of the invention. The computer system 60 includes memory 62 which can be utilized to store and retrieve software programs incorporating computer code that implements aspects of the invention, data for use with the invention, and the like. Exemplary computer readable storage media include CD-ROM, floppy disk, tape, flash memory, system memory, and hard drive. Computer system 60 further includes subsystems such as a central processor 61, fixed storage 64 (e.g., hard drive), removable storage 66 (e.g., CD-ROM drive), and one or more network interfaces 67. Other computer systems suitable for use with the invention may include additional or fewer subsystems. For example, computer system 60 may include more than one processor 61 (i.e., a multi-processor system) or a cache memory.

The system bus architecture of computer system 60 is represented by arrows 68 in FIG. 4. However, these arrows are only illustrative of one possible interconnection scheme serving to link the subsystems. For example, a local bus may be utilized to connect the central processor 61 to the system memory 62. Computer system 60 shown in FIG. 4 is only one example of a computer system suitable for use with the invention. Other computer architectures having different configurations of subsystems may also be utilized. Communication between computers within the network is made possible with the use of communication protocols, which govern how computers exchange information over a network.

It is understood that the examples and embodiments that are described herein are for illustrative purposes only and that various modifications and changes in light thereof will be suggested to persons skilled in the art and are to be included within the spirit and purview of this application and scope of the appended claims and their full scope of equivalents.