|Publication number||US6597663 B1|
|Application number||US 09/360,711|
|Publication date||22 Jul 2003|
|Filing date||26 Jul 1999|
|Priority date||3 Mar 1997|
|Also published as||US5964841|
|Publication number||09360711, 360711, US 6597663 B1, US 6597663B1, US-B1-6597663, US6597663 B1, US6597663B1|
|Original Assignee||Cisco Technology, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (14), Non-Patent Citations (4), Referenced by (56), Classifications (13), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This is a continuation of Ser. No. 08/810,083 U.S. Pat. No. 5,964,841, filed Mar. 3, 1997, issued on Oct. 12, 1999.
This invention relates generally to computer networks and, more particularly, to the detection of routing transients in a computer network.
Communication in a computer network involves the exchange of data between two or more entities interconnected by communication links and subnetworks. These entities are typically software programs executing on hardware computer platforms, such as end stations and intermediate stations. An example of an intermediate station may be a switch or router which interconnects the communication links and subnetworks to enable transmission of data between the end stations. The stations typically communicate by exchanging discrete packets or frames of data according to predefined protocols. In this context, a protocol consists of a set of rules defining how the stations interact with each other.
Most networks are typically organized as a series of hardware and software levels or “layers” within each station. These layers interact to format data for transfer between, e.g., a source station and a destination station communicating over the network. Specifically, predetermined services are performed on the data as it passes through each layer and the layers communicate with each other by means of the predefined protocols. This layered design permits each layer to offer selected services to other layers using a standardized interface that shields those layers from the details of actual implementation of the services.
Modern communications architectures are organized as such layered designs. The Internet communications architecture is an example of a layered architecture represented by four layers which are termed, in ascending interfacing order, the network interface, internetwork, transport and application layers. These layers are arranged to form a protocol stack in each communicating node of the network. FIG. 1 illustrates a schematic block diagram of prior art Internet protocol stacks 125 and 175 used to transmit data between a source station 110 and a destination station 150, respectively, of a network 100. As can be seen, the stacks 125 and 175 are physically connected through a communications channel 180 at the network interface layers 120 and 160. For ease of description, the protocol stack 125 will be described.
In general, the lower layers of the communications stack provide internetworking services and the upper layers, which are the users of these services, collectively provide common network application services. The transport layer 114 serves as the boundary between the network-specific elements and the application-specific elements. The transport layer's fundamental service is to move a user's data from its source to its destination over a communication path using the internetwork subsystem. The application layer 112 provides services suitable for the different types of applications using the network.
The lower network interface layer 120 of the Internet architecture addresses protocols that occupy physical and datalink sublayers of layer 120. The physical layer 126 is concerned with the actual transmission of signals across the communication channel and the datalink layer is responsible for transmission of data from one station to another. The primary network layer protocol of the Internet architecture is the Internet protocol (IP) contained within the internetwork layer 116. IP is primarily a connectionless network protocol that relies on transport protocols for end-to-end reliability. An example of such a reliable transport mechanism is the transmission control protocol (TCP) contained within the transport layer 114.
Data transmission over the network 100 therefore consists of generating data in, e.g., sending process 104 executing on the source station 110, passing that data to the application layer 112 and down through the layers of the protocol stack 125, where the data are sequentially formatted as a frame for delivery onto the channel 180 as bits. Those frame bits are then transmitted over an established connection of channel 180 to the protocol stack 175 of the destination station 150 where they are passed up that stack to a receiving process 174. Data flow is schematically illustrated by solid arrows.
Although actual data transmission occurs vertically through the stacks, each layer is programmed as though such transmission were horizontal. That is, each layer in the source station 110 is programmed to transmit data to its corresponding layer in the destination station 150, as schematically shown by dotted arrows. To achieve this effect, each layer of the protocol stack 125 in the source station 110 typically adds information (in the form of a header field) to the data frame generated by the sending process as the frame descends the stack. At the destination station 150, the various encapsulated headers are stripped off one-by-one as the frame propagates up the layers of the stack 175 until it arrives at the receiving process.
As noted, each layer of the protocol stack offers selected services to other layers; one such service is a connectionless service. This network service is generally implemented by a network layer protocol, an aspect of which involves the routing of packets from the source station to the destination station. In particular, this aspect of the internetwork layer concerns the algorithms and protocols used by routers when cooperating to calculate paths through a network topology. A routing algorithm is that portion of the network layer software responsible for determining an output communication link (i.e., an egress) over which an incoming packet should be transmitted. An example of a conventional routing algorithm is the Dijkstra algorithm and an example of a conventional network layer routing protocol is a link state routing protocol.
According to this latter protocol, each router constructs a link state packet (LSP) comprising information, such as a list of neighboring nodes adjacent to the router, sufficient to generate a complete map of the topology of the network. As defined herein, the term “neighbor” denotes a neighboring router. The LSP is then forwarded to all other routers of the network over, e.g., a plurality of interconnected local area networks (LANs). Each of these other routers stores only the most recently received LSP from the forwarding router in its LSP database. Armed with updated maps, the routers may compute shortest paths to destination stations using a conventional routing algorithm; the computed paths are then stored in forwarding tables of the routers. Examples of link state routing protocols are the intermediate system to intermediate system (IS-IS) protocol defined by the International Standards Organization (ISO), the open shortest path first (OSPF) protocol defined by the Internet protocol (IP) community and the NetWare link services protocol (NLSP) defined by Novell, Inc.
Use of link state routing in conjunction with hop-by-hop forwarding may result in formation of transient (i.e., temporary) forwarding loops. Routing transients typically arise when there is a change in the topology of a network. For example in response to a network topology change, each router updates its routing information and re-calculates shortest paths between the router and a destination station. This newly updated information is then transmitted to the other routers in the network. While the other routers propagate the updated information throughout the network and re-calculate their forwarding tables, there is a possibility that routers possessing inconsistent routing information may forward packets back to a previous sender of the packets, thus creating forwarding loops. The present invention is directed to an approach that enables detection of the occurrence of forwarding loops.
Conventional link state routing protocols, such as OSPF and IS-IS, generally do not provide mechanisms for suppressing such forwarding loops during routing transients. In order to limit the amount of network resources consumed by such transient forwarding loops, each packet may carry hop-count (e.g., time-to-live) information in a conventional network layer header of the packet. When a router forwards the packet, it decrements the hop-count information and when a router receives the packet with the hop-count information equal to zero, it discards the packet.
An approach that enables limiting of the amount of networking resources consumed by transient forwarding loops without relying on each router to decrement hop-count information is described in an Internet-Draft publication titled ARIS: Aggregate Route-Based IP Switching by Richard Woundy et al. of International Business Machines Corp, November 1996. This publication discloses a mechanism which uses conventional link state routing protocols as the basis for switching IP datagrams by the addition of the ARIS protocol that establishes switched paths through a network. The ARIS protocol guarantees that asynchronous transfer mode (ATM) virtual circuit (VC) loops are prevented even in the presence of transient IP routing loops by using an integrated switch router (ISR) identification (“ISR ID”) list.
Specifically, each ISR in a VC establishment path appends its own unique ISR ID to each establishment message it forwards. In this way, an ISR is able to determine the path a message has traversed and can ensure that no loops are formed. Further, if an ISR modifies or deletes an egress due to an IP route change, the ISR must unsplice any established upstream VC from the downstream VC. Such unsplicing forces inbound traffic to be forwarded at the IP network layer so that transient IP routing loops cannot produce VC loops.
Another approach directed to solving the problem of suppressing forwarding loops during routing transients is described in U.S. Pat. No. 5,265,092, titled Synchronization Mechanism for Link State Packet Routing by Stuart R. Soloway et al. This patent discloses a method of providing loop free and shortest path routing of data packets in a network of switches through modifications to known LSP routing protocols.
Specifically, a switch uses a received LSP to compute a forwarding table and informs neighboring switches of a routing change. The switch discards subsequent packets whose path would be affected by the routing change. Discarding of packets continues until the switch receives notification from each adjacent switch affected by the routing change that all affected routing paths have been re-calculated and the forwarding table of each affected switch has been updated. While adjacent switches may temporarily contain inconsistent LSP databases and possibly inconsistent forwarding tables, looping of data packets is prevented. Thus, the objective of Soloway is to essentially synchronize LSP databases across the network and data packets are discarded until that objective is achieved.
The mechanism in Soloway by which a switch informs the neighboring switches of the routing change, and by which the switch receives notification of those switches' affected by the routing change, is a Ready Announcement. The Ready Announcement is substantially a LSP that is modified to include an announcement bit which, when asserted true, indicates to all receivers that the Ready Announcement has been used to re-compute a forwarding table of the sending switch. Distribution of a modified LSP over the network results in relatively “slow” convergence of the patent's objective; that is, processing of the Ready Announcement consumes substantial time and overhead to determine inconsistencies of LSP databases.
The invention comprises a technique for efficiently detecting inconsistencies in forwarding databases of a router and its neighbor during routing transients in a computer network. Specifically, the technique enables is the router to detect when its view of a computed path to a destination station is inconsistent (in a way that may indicate potential transient forwarding loops) with the view of its neighbor along that path. Upon detecting such an inconsistent state, the router invokes one of a plurality of forwarding mechanisms with respect to a packet intended for the destination station to either suppress forwarding loops that may arise during the transients or to limit the amount of network resources such loops may consume.
In the illustrative embodiment, the novel detection technique comprises a control component and a forwarding component. During execution of the control component, each of the router and neighbor compute a shortest path and hop-count parameter to the destination, and store the computed path and parameter in their respective augmented forwarding information databases (FIB′). Upon detecting a change in the hop-count parameter stored in the FIB′, the neighbor sends an update message to all of its neighbors, including the router that views the neighbor as its next-hop (NH) neighbor with respect to the destination. In accordance with an aspect of the present invention, the update message contains a tuple comprising an address prefix associated with the computed path to the destination station and the hop-count parameter associated with that path to the destination. Notably, the hop-count parameter contained in the update message is a value representing the number of routers between the router originating the message and the last router within the same routing hierarchy (e.g., OSPF area) as the originating router along the computed path to the destination station (where the path is determined by the originating router).
In response to receiving the update message from its NH neighbor, the router (i) either discards all packets intended for the destination that are queued for transmission to the NH neighbor, or decrements a time-to-live or lifetime entry of an conventional network layer header of each packet and (ii) returns an acknowledgement message comprising the same tuple contained in the update message. The router then compares the NH view of the computed path, i.e., the hop-count value contained in the update message received from the NH neighbor, with its own view, i.e., the hop-count value contained in its FIB′. In accordance with another aspect of the invention, if the hop-count value in the update message is less than the FIB′ hop-count value, the router's view of the path is consistent with the NH neighbor's view and the packet may be sent to the destination station.
On the other hand, if the update message hop-count value is not less than the FIB′ hop-count value, the router's view of the computed path is inconsistent with its NH neighbor's view. As a result, the forwarding component of the detection technique is invoked. According to this aspect of the invention, the packet may be discarded by the router or, alternatively, forwarded along the path but only after decrementing the time-to-live or lifetime entry of the conventional network layer header of the packet. These alternatives are invoked by the router for as long as the database inconsistency persists, thus avoiding persistent looping during the transients.
Advantageously, the inventive technique either completely eliminates or contains the amount of looping that occurs during routing transients. In addition, the invention may operate in an environment where decrementing time-to-live (hop-count) on every packet may be undesirable or infeasible.
The above and further advantages of the invention may be better understood by referring to the following description in conjunction with the accompanying drawings in which like reference numbers indicate identical or functionally similar elements:
FIG. 1 is a schematic block diagram of prior art protocol stacks used to transmit data between stations of a computer network;
FIG. 2 is a block diagram of a network system including a collection of computer networks connected to a plurality of stations;
FIG. 3 is a flowchart illustrating a control sequence of a novel detection technique in accordance with the invention;
FIG. 4 is a schematic diagram of an update message in accordance with the invention;
FIG. 5 is a schematic diagram of an acknowledgement message in accordance with the invention;
FIG. 6 is a flowchart illustrating a forwarding sequence of the novel detection technique according to the invention; and
FIGS. 7A and 7B are schematic block diagrams of conventional network layer headers that may operate advantageously with the present invention.
FIG. 2 is a block diagram of a network system 200 comprising a collection of computer networks connected to a plurality of stations. The stations are typically computers comprising source station 202, destination station 204 and intermediate stations 206-210, which are preferably routers (R). The computer networks included within system 200 are preferably local area networks (LANs) interconnected by the routers, although the networks may comprise other communication links, such as wide area networks. Communication among the stations coupled to the LANs is typically effected by exchanging discrete data “packets” among the stations. The routers facilitate the flow of these data packets throughout the system by routing the packets to the proper receiving stations.
Each router typically comprises a plurality of interconnected elements, such as a processor 212, a memory 214 and an input/output (I/O) adapter 216. The memory 214 may comprise storage locations addressable by the processor and adapter for storing software programs and data structures associated with the inventive detection technique. The memory may be farther organized as a forwarding information database (FIB) 220 for storing routing information and computed parameters described herein although, in an alternate embodiment, a disk (not shown) may be coupled to the I/O adapter and configured to function as the database.
The processor may further comprise processing elements or logic for executing the software programs and manipulating the data structures and packets according to the techniques described herein. An operating system, portions of which are typically resident in memory and executed by the processor, functionally organizes the router by, inter alia, invoking network operations in support of software processes executing on the router. It will be apparent to those skilled in the art that other processor and memory means, including various computer readable media, may be used for storing and executing program instructions pertaining to the described techniques.
In general, when source station 202 transmits a packet over a LAN, such as LAN 205, the packet is sent to all stations on that LAN. If the intended recipient of the packet is connected to LAN 215, the packet is routed through routers 206-210 onto LAN 215. Typically, the packet contains two destination addresses: the address of the final destination station 204 and the address of the next station along the route. The final destination address remains constant as the packet traverses the networks, while the next destination address changes as the packet moves from station to station along the route through the networks.
A key function of a router is determining the next station to which the packet is sent; this routing function is preferably performed by network layer (such as internetwork layer 116 of FIG. 1) of a protocol stack within each station. This aspect of the network layer concerns the algorithms and protocols used by routers when cooperating to calculate paths through a network topology. The routers typically execute routing algorithms to decide over which communication links incoming packets should be transmitted.
A type of network layer routing protocol commonly employed by routers is a link state routing protocol. However, conventional link state routing algorithms in conjunction with hop-by-hop forwarding do not generally prevent the creation of temporary forwarding loops during routing transients in a network. In particular, there is a possibility that routers possessing inconsistent routing information in their forwarding databases may forward packets back to a previous sender of the packets during routing transients, thus creating forwarding loops.
In accordance with the present invention, a technique is provided for detecting inconsistencies in FIBs of a router (such router 210) and its neighbor 206 during routing transients in a computer network. As described herein, the neighbor 206 is preferably a next-hop (NH) neighbor as viewed by the router 210 with respect to a particular destination, such as destination station 204. The inventive technique enables the router 210 to detect when its view of a computed path to destination station 204 is inconsistent with the view of its NH neighbor 206 along that path. Upon detecting such an inconsistent state, the router invokes one of a plurality of forwarding mechanisms with respect to a packet intended for the destination station in an attempt to either suppress forwarding loops that may arise during the transients or limit the amount of resources such loops consume.
FIGS. 3 and 6 are flowcharts illustrating the sequence of steps comprising the novel detection technique. In the illustrative embodiment, the technique is embodied as a network layer protocol comprising a control mechanism component 300 and a forwarding mechanism component 600. The control mechanism is based on the ability of each router to compute the shortest path and/or number of hops to a destination station when executing a link state algorithm.
Referring to FIG. 3, the control mechanism sequence 300 starts at Step 302 and proceeds to Step 304 where each router computes a shortest path (route) to the destination 204 by executing a routing algorithm, such as the conventional Dijkstra algorithm. By-products of the Dijkstra algorithm include determinations of parameters such as the next hop, i.e., intermediate router, and the hop-count to the destination, i.e., hop-count (D). In Step 306, the routers install the computed path, together with these parameters, in their FIBs 220.
Each router then constructs an “augmented” FIB (denoted FIB′ 230 in FIG. 2) by manipulating the contents of the FIB 220 to include the next-hop and hop-count (D) parameters (Step 308); these parameters are preferably stored in the FIB′ at a location referenced by an address prefix associated with the path to the destination. The address prefix is that portion of the destination address typically used by network layer protocols performing routing functions (at the same routing level of a network) to make next-hop determinations. The routing information exchanged by (peer) routers typically includes this destination address prefix, although other encoding methods for a set of reachable destinations could be used as well (e.g., explicit enumeration or ranges).
In Step 310, each router checks the FIB′ to determine whether there is a change that affects the hop-count (D) parameter. Although the hop-count typically changes as a result of a change in network topology, not all changes in topology result in a change in hop-count. If there is no change affecting the hop-count (D), each router waits for a change in Step 312 and the sequence loops-back to Step 310; otherwise, if there is a change to the parameter, that router, e.g., NH neighbor 206, generates an update message in Step 314 and transmits that message to all-of its neighbors, including router 210.
FIG. 4 is a schematic diagram of the format of the update message 400 comprising a type field 402 identifying the type of message, an address field 404 of the destination station and a hop-count field 406. Specifically, the latter two fields contain a tuple comprising an address prefix of the destination station (in field 404) and a hop-count (D) [UPDATE] value (in field 406). The hop-count (D) [UPDATE] value in field 406 of the update message 400 represents the number of routers between the router originating the message and the last router within the same routing hierarchy (e.g., OSPF area) as the originating router along the computed path to the destination station (where the path is determined by the originating router).
Upon receiving the update message 400 from the NH neighbor 206, the router 210 (i) either discards all packets intended for the destination that are queued for transmission to the NH neighbor 206, or decrements a time-to-live or lifetime entry of an conventional network layer header of each packet and (ii) acknowledges receipt of the update message by returning an acknowledgement message to the NH neighbor 206 in Step 316. It should be noted that the protocol for exchanging update and acknowledgement messages described herein is built upon a reliable transport mechanism, such as TCP, to ensure reliable exchanges between the router and its neighbor.
FIG. 5 is a schematic block diagram of the format of the acknowledgement message 500 which is substantially similar to the update message 400. That is, the acknowledgement message 500 comprises a type field 502 identifying the type of message, an address field 504 containing the address prefix of the destination station and a hop-count field 506. The contents of the hop-count field 506 comprise a hop-count (D) [ACK] value that is identical to the hop-count (D) [UPDATE] value stored in field 406.
The router 210 then compares the NH view of the computed path, i.e., the hop-count (D) [UPDATE] value contained in the NH neighbor's update message, with its own view, i.e., the hop-count (D) [FIB′] value contained in its FIB′, in Step 318. In accordance with another aspect of the invention, a determination is made as to whether the hop-count (D) [UPDATE] value is less than the hop-count (D) [FIB′] value in Step 320. If so, the router's view of the path is consistent with the NH neighbor's view and the packet may be sent over the path to the destination station in Step 322; the sequence then ends in Step 324. On the other hand, if the update hop-count value (D) is not less than the FIB′ hop-count (D) value (Step 320), the router's view of the computed path is inconsistent with its NH neighbor's view (Step 326) and the forwarding component sequence of the detection technique is invoked.
Referring to FIG. 6, the forwarding sequence 600 starts at Step 602 and proceeds to Step 604 where a forwarding mechanism is selected. Specifically, the packet may be discarded by the router in Step 606; this forces the sender to retransmit the packet because of the underlying reliable transport mechanism. Alternatively, the packet may be forwarded over the path to the destination in Step 610 but only after decrementing a time-to-live or lifetime entry of a conventional network layer header of the packet (Step 608). In either case, the sequence then ends in Step 612. These alternative forwarding mechanisms are preferably invoked by the router for as long as the database inconsistency persists, thus avoiding persistent looping during the transients.
FIGS. 7A-7B are schematic block diagrams of conventional network layer headers that may operate advantageously with the present invention. Specifically, FIG. 7A is a diagram of the Internet protocol (IP) network layer header 700 having a time-to-live field 702 and FIG. 7B is a diagram of the connectionless network layer protocol (CLNP) header 750 having a lifetime field 752. In yet another alternate embodiment, the network layer header may comprise the Internet Packet Exchange (IPX) protocol header having a field similar to the time-to-live field 702. The contents of the fields 702 and 752 are modifiable by the routers; in particular, the contents of these fields are typically set to some initial value by the source station and are thereafter decremented by the routers until they reach zero (0), at which point the packet is discarded. Thus if the packet is caught in a forwarding loop encompassing the routers, the packet will eventually be discarded to suppress the loop.
It should be noted that the router 210 is considered in a transient state (from the point of view of the NH neighbor 206 and destination 204) from the moment at which the NH neighbor 206 installs a new path to the destination in its FIB until the NH neighbor 206 receives and processes an acknowledgement from the router 210 indicating that the update message was received and processed. If the NH neighbor 206 changes its path to the destination station 204, the neighbor discards all packets destined to the destination or decrements a time-to-live or lifetime entry of a network layer header if the packets were received from the router 210 when in a transient state.
When implementing the novel technique it is assumed that there is no re-ordering of packets at the datalink layer of the protocol stack. Moreover, the inventive technique does not ensure that packets do not traverse through a non-shortest path route; the technique only constrains the length (hop-count) of such a route.
An advantage of the inventive technique is that it enables limiting of the amount of resources that could be consumed during routing transients without requiring decrementing time-to-live (hop-count) on every packet. The invention may further operate in an environment where decrementing time-to-live (hop-count) may be undesirable or infeasible.
While there has been shown and described an illustrative embodiment for efficiently detecting inconsistencies in forwarding databases of a router and its NH neighbor during routing transients in a computer network, it is to be understood that various other adaptations and modifications may be made within the spirit and scope of the invention. For-example in an alternate embodiment of the invention, the hop-count parameter contained in the novel update and acknowledgement messages may be substituted with an entire path parameter. Here, the entire path parameter, i.e., path (D), is also a by-product of the Dijkstra algorithm and includes identification (ID) of all routers in the computed path between the either the router and destination or the neighbor and destination.
Furthermore, the comparison operation of Step 318 (FIG. 3) for this alternate embodiment comprises the router 210 comparing the path (D) contents contained in the update message with the path (D) contents contained in its FIB′. A determination is then made as to whether the path (D) of the FIB′ is equal to the path (D) of the update message minus the NH neighbor's ID in Step 320. If so, the router's view of the path is consistent with the NH neighbor's view and the packet may be sent to the destination station in Step 322. Otherwise, the views are inconsistent (Step 324) and the forwarding component sequence 600 (FIG. 6) is invoked.
The foregoing description has been directed to specific embodiments of this invention. It will be apparent, however, that other variations and modifications may be made to the described embodiments, with the attainment of some or all of their advantages. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5088032||29 Jan 1988||11 Feb 1992||Cisco Systems, Inc.||Method and apparatus for routing communications among computer networks|
|US5265092 *||18 Mar 1992||23 Nov 1993||Digital Equipment Corporation||Synchronization mechanism for link state packet routing|
|US5517620||19 May 1994||14 May 1996||Nec Corporation||Dynamic updating of routing information for routing packets between LAN's connected to a plurality of routers via a public network|
|US5557745||20 Mar 1995||17 Sep 1996||Digital Equipment Corporation||Method for supporting foreign protocols across backbone network by combining and transmitting list of destinations that support second protocol in first and second areas to the third area|
|US5600794||4 Aug 1995||4 Feb 1997||Bay Networks, Inc.||Method and apparatus for managing exchange of metrics in a computer network by exchanging only metrics used by a node in the network|
|US5754790||1 May 1996||19 May 1998||3Com Corporation||Apparatus and method for selecting improved routing paths in an autonomous system of computer networks|
|US5781534 *||31 Oct 1995||14 Jul 1998||Novell, Inc.||Method and apparatus for determining characteristics of a path|
|US5790808||6 Jul 1995||4 Aug 1998||3 Com||Active topology maintenance in reconfiguring bridged local area networks with state transition with forgetting interval|
|US5805593 *||26 Sep 1995||8 Sep 1998||At&T Corp||Routing method for setting up a service between an origination node and a destination node in a connection-communications network|
|US5964841 *||3 Mar 1997||12 Oct 1999||Cisco Technology, Inc.||Technique for handling forwarding transients with link state routing protocol|
|US6044075 *||15 Dec 1994||28 Mar 2000||International Business Machines Corporation||Apparatus and method for routing a communication in a network|
|US6055561 *||30 Sep 1997||25 Apr 2000||International Business Machines Corporation||Mapping of routing traffic to switching networks|
|US6069889 *||30 Sep 1997||30 May 2000||International Business Machines Corporation||Aggregation of data flows on switched network paths|
|EP0447725A2||28 Dec 1990||25 Sep 1991||Digital Equipment Corporation||Updating link state information in networks|
|1||Garcia-Luna-Aceves, et al., A Unified Approach to Loop-Free Routing Using Distance Vectors or Link States, Copyright 1989, pp. 212-223.|
|2||Radia Perlman, "Interconnections Bridges and Routers", Addison-Wesley Professional Computing Series, Copyright 1992, pp. 205-231.|
|3||Richard Woundy, et al., ARIS: Internet Draft "Aggregate Route-Based IP Switching", Nov., 1996, 31 pages.|
|4||William Stallings, "Data and Computer Communications", 4th ed., Copyright 1994, pp. 296-312, 488-509.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6731639 *||30 Mar 2000||4 May 2004||Nortel Networks Limited||Multi protocol label switching for multiple access segments|
|US6820134 *||28 Dec 2000||16 Nov 2004||Cisco Technology, Inc.||Optimizing flooding of information in link-state routing protocol|
|US6850524 *||31 Jul 2000||1 Feb 2005||Gregory Donald Troxel||Systems and methods for predictive routing|
|US7006441 *||16 Nov 2000||28 Feb 2006||At&T Corp.||Link state network having weighted control message processing|
|US7013347 *||16 Oct 2001||14 Mar 2006||Cisco Technology, Inc.||Distance vector extension to the address resolution protocol|
|US7406034 *||1 Apr 2002||29 Jul 2008||Cisco Technology, Inc.||Methods and apparatus for fibre channel frame delivery|
|US7433326||5 May 2003||7 Oct 2008||Cisco Technology, Inc.||Methods and devices for exchanging peer parameters between network devices|
|US7437476||12 Oct 2004||14 Oct 2008||Cisco Technology, Inc.||Optimizing flooding of information in link-state routing protocol|
|US7499410||26 Jun 2003||3 Mar 2009||Cisco Technology, Inc.||Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain—IDs|
|US7548514 *||15 Sep 2005||16 Jun 2009||At&T Corp||Link state network having weighted control message processing|
|US7593324||25 Oct 2004||22 Sep 2009||Cisco Technology, Inc.||Graceful port shutdown protocol for fibre channel interfaces|
|US7599360||26 Dec 2001||6 Oct 2009||Cisco Technology, Inc.||Methods and apparatus for encapsulating a frame for transmission in a storage area network|
|US7616637||1 Apr 2002||10 Nov 2009||Cisco Technology, Inc.||Label switching in fibre channel networks|
|US7649844||29 Dec 2004||19 Jan 2010||Cisco Technology, Inc.||In-order fibre channel packet delivery|
|US7684350||16 Mar 2006||23 Mar 2010||Cisco Technology, Inc.||Method and apparatus for distributing labels in a label distribution protocol multicast network|
|US7830809||2 Mar 2007||9 Nov 2010||Cisco Technology, Inc.||Methods and apparatus for characterizing a route in a fibre channel fabric|
|US7831733 *||6 Jul 2001||9 Nov 2010||Avaya Holdings Limited||Policy-based forwarding in open shortest path first (OSPF) networks|
|US7876711||24 Dec 2008||25 Jan 2011||Cisco Technology, Inc.||Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain—IDs|
|US7916628||1 Nov 2004||29 Mar 2011||Cisco Technology, Inc.||Trunking for fabric ports in fibre channel switches and attached devices|
|US7986640||5 Jul 2006||26 Jul 2011||Cisco Technology, Inc.||Technique for efficiently determining acceptable link-based loop free alternates in a computer network|
|US8144595 *||23 Mar 2005||27 Mar 2012||Verizon Corporate Services Group Inc.||Variable translucency no-sight routing for AD-HOC networks|
|US8165146 *||16 Jan 2003||24 Apr 2012||Lightwaves Systems Inc.||System and method for storing/caching, searching for, and accessing data|
|US8300614 *||3 May 2010||30 Oct 2012||Avaya Inc.||Preventing packet loops in unified networks|
|US8429221 *||13 Dec 2001||23 Apr 2013||Rockstar Consortium Us Lp||Content request routing method|
|US8462790||24 Sep 2009||11 Jun 2013||Cisco Technology, Inc.||Label switching in fibre channel networks|
|US8514876 *||11 Aug 2009||20 Aug 2013||Cisco Technology, Inc.||Method and apparatus for sequencing operations for an incoming interface check in data center ethernet|
|US8542695||2 Mar 2012||24 Sep 2013||Lightwave Systems, Inc.||System and method for storing/caching, searching for, and accessing data|
|US8605624||29 Aug 2008||10 Dec 2013||Cisco Technology, Inc.||Methods and devices for exchanging peer parameters between network devices|
|US8625460||21 Dec 2010||7 Jan 2014||Cisco Technology, Inc.||Fibre channel switch that enables end devices in different fabrics to communicate with one another while retaining their unique fibre channel domain—IDs|
|US8644186||3 Oct 2008||4 Feb 2014||Cisco Technology, Inc.||System and method for detecting loops for routing in a network environment|
|US8750094||18 Feb 2011||10 Jun 2014||Cisco Technology, Inc.||Trunking for fabric ports in Fibre channel switches and attached devices|
|US8837292 *||31 Dec 2010||16 Sep 2014||Telefonaktiebolaget L M Ericsson (Publ)||Relayed CSPF computation for multiple areas and multiple autonomous systems|
|US8937967||3 Sep 2013||20 Jan 2015||Lightwaves Systems, Inc.||System and method for storing/caching, searching for, and accessing data|
|US9161290||6 Mar 2012||13 Oct 2015||Verizon Patent And Licensing Inc.||Variable translucency no-sight routing for ad-hoc networks|
|US9350653||28 May 2013||24 May 2016||Cisco Technology, Inc.||Label switching in fibre channel networks|
|US9491104||5 Dec 2014||8 Nov 2016||Lightwaves Systems, Inc.||System and method for storing/caching, searching for, and accessing data|
|US20030014540 *||6 Jul 2001||16 Jan 2003||Nortel Networks Limited||Policy-based forwarding in open shortest path first (OSPF) networks|
|US20030115283 *||13 Dec 2001||19 Jun 2003||Abdulkadev Barbir||Content request routing method|
|US20030118053 *||26 Dec 2001||26 Jun 2003||Andiamo Systems, Inc.||Methods and apparatus for encapsulating a frame for transmission in a storage area network|
|US20030218988 *||6 Sep 2002||27 Nov 2003||Min-Ho Han||Network for transferring active packet and method for employing same|
|US20040100910 *||5 May 2003||27 May 2004||Andiamo Systems, Inc.||Methods and devices for exchanging peer parameters between network devices|
|US20050036499 *||26 Jun 2003||17 Feb 2005||Andiamo Systems, Inc., A Delaware Corporation||Fibre Channel Switch that enables end devices in different fabrics to communicate with one another while retaining their unique Fibre Channel Domain_IDs|
|US20060087963 *||25 Oct 2004||27 Apr 2006||Cisco Technology, Inc.||Graceful port shutdown protocol for fibre channel interfaces|
|US20060153186 *||29 Dec 2004||13 Jul 2006||Cisco Technology, Inc.||In-order fibre channel packet delivery|
|US20070153816 *||2 Mar 2007||5 Jul 2007||Cisco Technology, Inc.||Methods and apparatus for characterizing a route in a fibre channel fabric|
|US20080008104 *||5 Jul 2006||10 Jan 2008||Previdi Stefano B||Technique for efficiently determining acceptable link-based loop free alternates in a computer network|
|US20100008375 *||24 Sep 2009||14 Jan 2010||Cisco Technology, Inc.||Label switching in fibre channel networks|
|US20100290385 *||3 May 2010||18 Nov 2010||Avaya, Inc.||Preventing packet loops in unified networks|
|US20110038257 *||11 Aug 2009||17 Feb 2011||Cisco Technology, Inc.||Method and apparatus for sequencing operations for an incoming interface check in data center ethernet|
|US20110090816 *||21 Dec 2010||21 Apr 2011||Cisco Technology, Inc.||FIBRE CHANNEL SWITCH THAT ENABLES END DEVICES IN DIFFERENT FABRICS TO COMMUNICATE WITH ONE ANOTHER WHILE RETAINING THEIR UNIQUE FIBRE CHANNEL DOMAIN_IDs|
|US20110141906 *||18 Feb 2011||16 Jun 2011||Cisco Technology, Inc.||Trunking for fabric ports in fibre channel switches and attached devices|
|US20120069740 *||31 Dec 2010||22 Mar 2012||Wenhu Lu||Relayed CSPF Computation for Multiple Areas and Multiple Autonomous Systems|
|US20120147808 *||9 Dec 2011||14 Jun 2012||Millennial Net, Inc.||Network Protocol|
|US20130218958 *||10 Apr 2013||22 Aug 2013||Rockstar Consortium Us Lp||Content request routing method|
|WO2006015007A2 *||26 Jul 2005||9 Feb 2006||Meshnetworks, Inc.||System and method for detecting transient links in multi-hop wireless networks|
|WO2006015007A3 *||26 Jul 2005||4 May 2006||Meshnetworks Inc||System and method for detecting transient links in multi-hop wireless networks|
|U.S. Classification||370/252, 370/389, 709/238, 370/238|
|Cooperative Classification||H04L45/18, H04L45/28, H04L45/02, H04L45/20|
|European Classification||H04L45/18, H04L45/02, H04L45/20, H04L45/28|
|18 Dec 2006||FPAY||Fee payment|
Year of fee payment: 4
|24 Jan 2011||FPAY||Fee payment|
Year of fee payment: 8
|22 Jan 2015||FPAY||Fee payment|
Year of fee payment: 12