US20040199567A1 - System and method for integrating multiserver platforms - Google Patents
System and method for integrating multiserver platforms Download PDFInfo
- Publication number
- US20040199567A1 US20040199567A1 US10/647,963 US64796303A US2004199567A1 US 20040199567 A1 US20040199567 A1 US 20040199567A1 US 64796303 A US64796303 A US 64796303A US 2004199567 A1 US2004199567 A1 US 2004199567A1
- Authority
- US
- United States
- Prior art keywords
- blade
- multiserver
- switch
- platform
- multiserver platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
Abstract
Description
- This application makes reference to, and/or claims priority to and/or claims benefit to:
- U.S. Provisional Patent Application Serial No. 60/458,719, entitled “Method and System to Provide Inter-Chassis Blade Server Integration for Scalability” and filed on Mar. 28, 2003;
- U.S. Provisional Patent Application Serial No. 60/448,656, entitled “A Method and System to Provide External Communication Using a Multiserver Platform Having a Single Switch Backplane” and filed on Feb. 18, 2003;
- U.S. Provisional Patent Application Serial No. 60/456,831, entitled “Method and System to Provide Inter-Blade Server Communication Using a Single Switch Backplane” and filed on Mar. 21, 2003; and
- U.S. Provisional Patent Application Serial No. 60/463,014, entitled “Method and System to Selectively Steer Data Traffic to Service Blades Using a Single Switch Backplane” and filed on Apr. 15, 2003.
- The above stated applications are hereby incorporated herein by reference in their entirety.
- Certain embodiments of the invention relate to communication among servers. More specifically, certain embodiments of the invention relate to a method and system for integrating multiserver platforms.
- A server may be a computer system in a network that may be accessed by one or more users and/or other computers. The server may provide, for example, access to information such as files, and to services such as communications, printing or other types of services that may be available through a network. In some cases, a special network operating system (OS) may run on a dedicated server, for example, in a large network. A personal computer (PC) operating system may run on a non-dedicated server having, for example, peer-to-peer networking software running thereon.
- Generally, a server may have one or more advanced or more powerful central processing units (CPUs), a larger memory, a larger cache and more storage space than a typical single user workstation or personal computer. The server may include, for example, multiple processors which may be dedicated to a particular service or provide a particular function such as e-mail handling, printing or communications. The server may also include devices such as, large power supplies, backup power capabilities such as an uninterruptible power supply (UPS) and various fault tolerant or redundant features such as redundant array of independent disks (RAID) technologies.
- A single server may exist in a standalone enclosure and may interface with a network via one or more network interfaces. Multiple standalone boxes may be situated in a central computing center with each standalone box coupled to a network via a respective cable. Each server may interface to the network separately at a particular data rate such as, for example, approximately 1 gigabits/second (Gb/s) for a Gigabit Ethernet or approximately 10 Gb/s for a 10 Gigabit Ethernet.
- Thus, the single server in a standalone enclosure may inefficiently utilize large amounts of space and/or power. Furthermore, since each single server may be connected to the network directly via a respective cable, a room full of servers might be overflowing with cables possibly necessitating detailed cable maps which may be quite time-intensive and costly to produce. In addition, single servers in a standalone enclosure may not be easily replaced during failure, particularly when there may be multiple failures. Consequently, the conventional single server in a standalone box may ultimately suffer from a substantial total cost of ownership (TCO).
- Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.
- Certain embodiments of the invention provide a method and system for communicating information in a server platform. Aspects of the method for communicating information in a server platform may include receiving at least one packet from at least one of a first switch blade associated with a first multiserver platform. The method may also include determining a second server blade associated with a second multiserver platform that may receive at least a portion of the received packet. In this regard, at least a portion of the received packet may be routed to the second blade server. The packet may be received by a third switch blade and/or a central switch. In instances where the packet may be received by the central switch, at least a portion of the received packet may be communicated to the second switch blade via at least one communication link that may couple the central switch directly to the second switch blade. The routed portion of the received packet may be processed by the second blade server.
- Another embodiment of the invention may provide a machine-readable storage, having stored thereon, a computer program having at least one code section for communicating information in a server platform. The at least one code section may be executable by a machine, thereby causing the machine to perform the steps as described above for communicating information in a server platform.
- Aspects of the system for processing information in a multiserver platform may include a first multiserver platform having a network interface and/or a first switch blade. At least a second multiserver platform comprising a second switch blade may be coupled to the first switch blade of the first multiserver platform. A third multiserver platform comprising a third switch blade may be coupled to the second switch blade of the second multiserver platform and/or the first switch blade of the first multiserver platform. The first multiserver platform, the second multiserver platform and the third multiserver platform may be coupled in a daisy-chain configuration. In this regard, the first multiserver platform and the third multiserver platform may communicate via the second multiserver platform.
- In another embodiment of the invention, at least one central switch may be coupled to the first switch blade of the first multiserver platform and the second switch blade of the second multiserver platform. At least a third switch blade of a third multiserver platform may also be coupled to the central switch. The first multiserver platform, second multiserver platform and third multiserver platform may communicate via the central switch.
- These and other advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.
- FIG. 1 is a block diagram of an embodiment of a multiserver platform in accordance with an embodiment of the invention.
- FIG. 2 is a block diagram illustrating an embodiment of a communication system including a multiserver platform and an external network in accordance with various aspects of the invention.
- FIG. 3 is a block diagram illustrating an embodiment of a communication system including an external network and N multiserver platforms coupled in a daisy-chain configuration in accordance with an embodiment of the invention.
- FIG. 4 is a block diagram illustrating the coupling of two switch blades in accordance with an embodiment of the invention.
- FIG. 5 is a flowchart illustrating exemplary steps for providing communication within the daisy-chain configuration of FIG. 3 in accordance with an embodiment of the invention.
- FIG. 6 is a block diagram illustrating an exemplary central switch configuration for the multiserver platform of FIG. 1, in accordance with various aspects of the invention.
- FIG. 7 is a flowchart illustrating exemplary steps for providing communication in the central switch configuration of FIG. 6 in accordance with an embodiment of the invention.
- Certain embodiments of the invention provide a method and system for communicating information in a server platform. Aspects of the method for communicating information in a multiserver platform may include receiving at least one packet from a first switch blade associated with a first multiserver platform. Another aspect of the method may include determining a second server blade associated with a second multiserver platform that may receive at least a portion of the received packet. In this regard, at least a portion of the received packet may subsequently be routed to the second blade server and the routed portion of the received packet processed by the second blade server. In another aspect of the invention, the packet may be received by a third switch blade and/or a central switch. Accordingly, in instances where the packet may be received by the central switch, at least a portion of the received packet may be communicated to the second switch blade via one or more communication links that may be utilized to couple the central switch directly to the second switch blade.
- FIG. 1 is a block diagram of an embodiment of a
multiserver platform 100 in accordance with an embodiment of the invention. Themultiserver platform 100 may include achassis 110, abackplane 130, aswitch blade 140,blade server interfaces 150, and a plurality of blade servers No. 1, No. 2, . . . , No. n, collectively referenced as 120. - The
chassis 110 may include thebackplane 130. However, although only onebackplane 130 is shown, the invention is not so limited and a plurality of backplanes may be provided within thechassis 110. In this regard, one or more backplanes may be coupled together. In a case where thechassis 110 may include a single backplane, the backplane may be regarded as a common backplane, which may provide connectivity for theblade servers 120. Thechassis 110 may be part of a single installation enclosure that includes a plurality of blade server slots which may be adapted for receiving one or more of theblade servers 120. - The
backplane 130 may include, for example, one or more blade server interfaces collectively referenced as 150, which may be referred to as blade server interconnects. In this regard, thechassis 110 may include a plurality of blade server slots that may be adapted to facilitate connection between the blade servers and the blade server interfaces 150. In other words, the blade server slots may provide a conduit for coupling theblade servers 120 to the blade server interfaces 150. Thebackplane 130 may also include one or more interfaces such as anetwork interface 160. Thenetwork interface 160 may be referred to as network interconnect. - The
switch blade 140 may be part of thebackplane 130. In this regard, theswitch blade 140 may be integrated within thebackplane 130 or it may be a plug-in card that may be plugged into thebackplane 130. - The
blade servers 120 may be coupled to thebackplane 130 via the blade server interfaces 150. Each of theblade servers 120 may therefore be coupled to a corresponding one of the server interfaces 150. For example, each of theblade servers 120 may be plugged into or removably mounted in a corresponding blade server slot in thechassis 110 so that it interfaces with a corresponding one of the server interfaces. In this regard, theblade servers 120 may be coupled to thebackplane 130. - Once the
blade servers 120 are mounted or plugged into thechassis 110, theblade servers 120 may be coupled to theswitch blade 140 of thebackplane 130 via the blade server interfaces 150. Thebackplane 130 may be adapted to provide connectivity, for example, between two or more of theblade servers 120. Furthermore, thebackplane 130 and/or theswitch blades 140 may provide connectivity between the one or more of theblade servers 120 and thenetwork 170. - The
network interface 160 facilitates connectivity between thebackplane 130 and thenetwork 170. In this regard, thenetwork interface 160 may couplebackplane 130 and/or one or more of the plurality ofswitch blades 140 to thenetwork 170. - FIG. 2 is a block diagram illustrating an embodiment of a
communication system 200 including amultiserver platform 201 and anexternal network 206, in accordance with various aspects of the invention. Themultiserver platform 201 may include a chassis having acommon backplane 211, a common switch-blade 202 and a plurality of blade servers including, ablade server # 1 203, ablade server # 2 204, . . . , bladeserver #N 205, where N may be any integer number. - Each of the
blade servers # 1, #2, . . . , #N may be a server that has been integrated on a single plug-in card or blade that may be plugged into a blade server slot of the chassis with thecommon backplane 211. The chassis with acommon backplane 211 may provide a single installation enclosure for the multipleblade servers # 1, #2, . . . , #N. - The chassis with the
common backplane 211 may also serve a common interface between eachblade server common switch blade 202. For example,common backplane 211 may provide acommon backplane interface 208 betweenblade server # 1 203 and thecommon switch blade 202.Common backplane 211 may also provide acommon backplane interface 209 betweenblade server # 2 204 and thecommon switch blade 202. Finally,common backplane 211 may provide acommon backplane interface 210 between bladeserver #N 205 and thecommon switch blade 202. In this regard, thecommon backplane interfaces common backplane 211. - The
common switch blade 202 may include N+1 interfaces and at least a portion of these interfaces may be adapted to perform packet switching of data frames between the N blade servers and theexternal network 206, in accordance with an embodiment of the invention. The common switch-blade may include intelligence that may manage and distribute data traffic to the relevant blade servers includingblade server # 1, #2, . . . , #N. The common switch-blade 202 may interface with each of the N blade servers via thecommon backplane 211. The common switch-blade 202 may also interface with theexternal network 206, thereby resulting in N+1 interfaces. - In accordance with an embodiment of the invention, the
external network 206 may include a 10 Gigabit Ethernet network connection and interface. Theexternal interface 207 between thecommon switch blade 202 and theexternal network 206 may include a 10 Gigabit Ethernet (GbE) interface, operating at a data rate of 10 Gb/s. In this regard, bi-directional network communication capability may be provided between theexternal network 206 and thecommon switch blade 202. In order to facilitate Gigabit Ethernet communication, thecommon backplane 211 may include a plurality of Gigabit Ethernet (GbE) interfaces. Theswitch blade 202 may communicate with each of the N blade servers independently over thecommon backplane 211 at a data rate of 1 Gb/s. For example, theblade server # 1 203 may communicate in a bi-directional manner with the common switch-blade 202 via thecommon backplane interface 208. Theblade server # 2 204 may also communicate in a bi-directional manner with thecommon switch blade 202 via thecommon backplane interface 209. Finally, the blade server #N 105 may communicate in a bi-directional manner with thecommon switch blade 202 via thecommon backplane interface 210. - In accordance with an embodiment of the invention, the
common switch blade 202 may have the capability to handle communication with themultiple blade servers common blade server 202 may facilitate the simultaneous transfer of information between any of theblade servers - FIG. 3 is a block diagram illustrating an embodiment of a
communication system 300 including anexternal network 301 and N multiserver platforms coupled in a daisy-chain configuration in accordance with an embodiment of the invention. The daisy-chain configuration includes N multiserver platforms referenced as 303, 304, . . . , 305 and labeled asmultiserver platform # 1,multiserver platform # 2, . . . , multiserver platform #N, respectively. Referring to FIG. 3, themultiserver platform # 1 303 may include acommon switch blade 306. Themultiserver platform # 2 304 may include acommon switch blade 307 and the multiserverplatform #N 305 includes acommon switch blade 308. - The
external network 301 may interface with theswitch blade 306 of themultiserver platform # 1 303 via, for example, a highspeed communication link 309. Themultiserver platform # 1,multiserver platform # 2, . . . , multiserver platforms #N referenced as 303, 305, . . . , 305 may be coupled together in a daisy-chained arrangement via, for example, high speed communication links. For example, theswitch blade 306 of themultiserver platform # 1 303 may interface with theswitch blade 307 of the multiserver platform #3 via a highspeed communication link 310. Theswitch blade 307 of themultiserver platform # 2 304 may also interface with the switch blade of another multiserver platform via a highspeed communication link 311. Theswitch blade 308 of the multiserverplatform #N 305 may also interface with the switch blade of some other multiserver platform via a highspeed communication link 312. - The high
speed communication links switch blades switch blade 306 may be adapted to communicate with theexternal network 301 and theswitch blade 307 at the same time over the highspeed communication links switch blades multiserver platforms multiserver platforms - FIG. 4 is a block diagram illustrating the coupling of two switch blades in accordance with an embodiment of the invention. Referring to FIG. 4, there is shown a
first multiserver platform 402 coupled to asecond multiserver platform 422. In this regard,reference 402 may include an enclosure or chassis of thefirst multiserver platform 402 andreference 422 may include an enclosure or chassis of themultiserver platform 422. Notwithstanding, thefirst multiserver platform 402 may include abackplane 404, a plurality of n blade servers collectively referred to as 406, aswitch blade 408 and abus 411. Also shown arebus transceivers controller 418. Each of thebus transceivers bus 411 within thebackplane 404. Each of thebus transceivers bus 411 within thebackplane 404. Thebus 411 may be a time division multiplexed (TDM) bus, a frequency division multiplexed (FDM) bus, or any other suitable type of bus. Accordingly, thebus transceivers communication link 440 may couple thefirst multiserver platform 402 to thesecond multiserver platform 422. Thecommunication link 440 may be similar to the communication links that couple themultiserver platform # 1,multiserver platform # 2, . . . , multiserver platform #N referenced as 303, 304, . . . , 305 in the daisy-chain arrangement of FIG. 3. - Each of the
blade servers 406 and theswitch blade 408 of thefirst multiserver platform 402 may include a bus transceiver that may be coupled to thebus 411. In this regard, blade server No. 1 includes abus transceiver 410, server blade No. 2 includes abus transceiver 412, and server blade No. n includes abus transceiver 414. Theswitch blade 408 may also include abus transceiver 416 and abus controller 418. Although thebus controller 418 is illustrated as a separate entity within theswitch blade 408, the invention is not so limited. Accordingly, one or more functions provided by thebus controller 418 may be provided by theswitch blade 408. In a case where all of the functions offered by the bus controller may be provided by the switch blade, this may eliminate a need for an additional bus processing entity such as thebus controller 418. - Notwithstanding, the
bus controller 418 and/or theswitch blade 408 of thefirst multiserver platform 402 may be adapted to control the transfer of messages between theblade servers 406 and theswitch blade 408. In this regard, thebus controller 418 may handle functions such as bus access and bus arbitration. Thebus controller 418 and/or theswitch blade 408 may also provide a switching function that may permit messages to be transferred among theblade servers 406 via the switch blade and from an external source such as the network 170 (FIG. 1) to any one or more of theblade servers 406. For example, one or more messages received from thenetwork 170 may be steered by theswitch blade 408 to one or more of theblade servers 406 based on a message type and a function provided by one or more of theblade servers 406. U.S. patent application Ser. No. ______ (Attorney Docket No. 14221US02) filed Aug. 26, 2003, discloses a method and system for selective steering of data traffic of various data types to functionally dedicated blade servers which application is incorporated herein by reference in its entirety. - The
bus controller 418 and/or theswitch blade 408 of thefirst multiserver platform 402 may include suitable hardware and/or software that may be adapted to control, for example, bus access, bus arbitration and/or switching among theblade servers 406 and theswitch blade 408. The hardware and/or software may therefore control the manner in which messages may be received from a first blade server and transferred, routed or switched to a second blade server via theswitch blade 408. - The
second multiserver platform 422 may include abackplane 424, a plurality of n blade servers collectively referred to as 426, aswitch blade 428 and abus 431. Also shown arebus transceivers controller 438. Each of thebus transceivers bus 431 within thebackplane 424. Each of thebus transceivers bus 431 within thebackplane 424. Thebus 431 may be a time division multiplexed (TDM) bus, a frequency division multiplexed (FDM) bus, or any other suitable type of bus. Accordingly, thebus transceivers - Each of the
blade servers 426 and theswitch blade 428 of thesecond multiserver platform 422 may include a bus transceiver that may be coupled to thebus 431. In this regard, blade server No. 1 includes abus transceiver 430, server blade No. 2 includes abus transceiver 432, and server blade No. n includes abus transceiver 434. Theswitch blade 428 may also include abus transceiver 436 and abus controller 438. Although thebus controller 438 is illustrated as a separate entity within theswitch blade 438, the invention is not so limited. Accordingly, one or more functions provided by thebus controller 438 may provided by theswitch blade 428. In a case where all of the functions offered by the bus controller may be provided by the switch blade, this may eliminate a need for an additional bus processing entity such as thebus controller 438. - Notwithstanding, the
bus controller 438 and/or theswitch blade 428 of thesecond multiserver platform 422 may be adapted to control the transfer of messages between theblade servers 426 and theswitch blade 428. In this regard, thebus controller 438 may handle functions such as bus access and bus arbitration. Thebus controller 438 and/or theswitch blade 428 may also provide a switching function that may permit messages to be transferred among theblade servers 426 via the switch blade and from an external source such as the network 170 (FIG. 1) to any one or more of theblade servers 426. For example, one or more messages received from thenetwork 170 may be steered by theswitch blade 428 to one or more of theblade servers 426 based on a message type and a function provided by one or more of theblade servers 426. - The
bus controller 438 and/or theswitch blade 428 of thesecond multiserver platform 422 may include suitable hardware and/or software that may be adapted to control, for example, bus access, bus arbitration and/or switching among theblade servers 426 and theswitch blade 428. The hardware and/or software may therefore control the manner in which messages may be received from a first blade server and transferred, routed or switched to a second blade server via theswitch blade 428. - FIG. 5 is a
flowchart 500 illustrating exemplary steps for providing communication within the daisy-chain configuration 302 of FIG. 3 in accordance with an embodiment of the invention. Referring to FIG. 5, instep 501, a first multiserver platform may transmit a first packet of information to a second multiserver platform via a first high speed communication link. Instep 502, the second multiserver platform may process the first packet and transmit a second packet of information to a third multiserver platform via a second high speed communication link. Instep 503, the third multiserver platform may process the second packet and transmit a third packet of information to the second multiserver platform via the second high speed communication link. Instep 504, the second multiserver platform may process the third packet and transmit a fourth packet of information to the first multiserver platform via the first high speed communication link. Instep 505, the first multiserver platform may process the fourth packet and transmit a fifth packet of information over an external network via a third high speed communication link. - FIG. 6 is a block diagram600 illustrating an exemplary
central switch configuration 602 for the multiserver platform of FIG. 1, in accordance with various aspects of the invention. Thecentral switch configuration 602 may include a central switch, a switching element or aswitch 603, amultiserver platform # 1 604, amultiserver platform # 2 605, up to and including a multiserverplatform #N 606. Themultiserver platform # 1 604 may include a common switch blade orswitch blade 607. Themultiserver platform # 2 605 may include aswitch blade 608 and the multiserverplatform #N 606 may include aswitch blade 609. - The
external network 601 may interface with theswitch blade 607 of themultiserver platform # 1 604 via a highspeed communication link 610. Themultiserver platform # 1 404 may be coupled to thecentral switch 603 via a highspeed communication link 611. Themultiserver platform # 2 605 may be coupled to thecentral switch 603 via thehigh speed link 612 and in a similar manner, the multiserverplatform #N 606 may be coupled to thecentral switch 603 via the highspeed communication link 613. In this regard, theswitch blade 607 of themultiserver platform # 1 404 may interface with thecentral switch 603 via the highspeed communication link 611. Theswitch blade 608 of themultiserver platform # 2 605 may connect with thecentral switch 603 via the highspeed communication link 612. In a similar manner, theswitch blade 609 of the multiserverplatform #N 606 may connect to thecentral switch 603 via the highspeed communication link 613. - In operation, the central switch may coordinate the high speed switching or routing of packets among the various
multiserver platforms multiserver platform central switch 603, to any other multiserver platform. In the daisy-chain configuration or arrangement, a packet of data may have to be passed through a plurality of intermediate multiserver platforms in order to be transferred to from a source platform to a destination platform. - The high
speed communication links switch blades multiserver platforms central switch 603 via the highspeed communication links switch blade 607 may also have the capability to communicate with theexternal network 601 and thecentral switch 603 at the same time over the highspeed communication links multiserver platforms - FIG. 7 is a
flowchart 700 illustrating exemplary steps for providing communication in the central switch configuration of FIG. 6 in accordance with an embodiment of the invention. Referring to FIG. 7, instep 701, a first multiserver platform may transmit a first packet of information to a central switch via a first high speed communication link. Instep 702, the central switch may transmit the first packet to a second multiserver platform via a second high speed communication link. Instep 703, the second multiserver platform may process the first packet and may transmit a second packet of information to the central switch via the second high speed communication link. Instep 704, the central switch may transmit the second packet to the first multiserver platform via the first high speed communication link. Instep 705, the first multiserver platform may process the second packet and may transmit a third packet of information over an external network via a third high speed communication link. - In accordance with various embodiments of the invention, the multiserver platforms may communicate data and/or control information among each other via one or more high speed communication links that may be coupled to the switch blades of the multiserver platforms and/or the central switch where present. The control information may include pertinent information related the multiserver platforms. For example, some control information may indicate the blade server associated with a particular multiserver platform from which a particular packet may have originated. Other exemplary information may include synchronization information, security information, and provisioning and security.
- In accordance with another embodiment of the invention, any one or more of the multiserver platforms may each provide a plurality of server functions. Alternatively, each of the multiserver platforms may be dedicated to providing a different, specific server function. Notwithstanding, the configurations of FIG. 3 and FIG. 6 may provide blade server scalability by utilizing at least two multiserver platforms to increase server performance and/or system capacity, for example. In this regard, multiserver platforms may be added or removed to facilitate increased and decreased traffic, respectively.
- Aspects of the invention provide a method and system for inter-platform blade server integration using a plurality of multiserver platforms. The configurations of FIG. 3 and FIG. 6, for example, may provide blade server scalability using a plurality of multiserver platforms to increase server performance and/or system capacity. In this regard, by integrating a plurality of multiserver platforms, a larger virtual server platform is effectively created.
- In particular, for example, aspects of the system for processing information in a server platform may include a first multiserver platform303 (FIG. 3) having at least one
network interface 309 and/or afirst switch blade 306. At least asecond multiserver platform 304 comprising asecond switch blade 307 may be coupled to thefirst switch blade 306 of thefirst multiserver platform 303. Athird multiserver platform 305 comprising athird switch blade 308 may be coupled to thesecond switch blade 304 of thesecond multiserver platform 307 and/or thefirst switch blade 306 of thefirst multiserver platform 303. Thefirst multiserver platform 303, thesecond multiserver platform 304 and thethird multiserver platform 305 may be coupled in a daisy-chain configuration. In this regard, thefirst multiserver platform 303 and thethird multiserver platform 305 may communicate via thesecond multiserver platform 304. - In another embodiment of the invention, for example, at least one central switch603 (FIG. 6) may be coupled to the
first switch blade 607 of thefirst multiserver platform 604 and thesecond switch blade 608 of thesecond multiserver platform 605. At least athird switch blade 609 of athird multiserver platform 606 may also be coupled to thecentral switch 603. Thefirst multiserver platform 604,second multiserver platform 605 and thirdmultiserver platform 606 may communicate via thecentral switch 603. - Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
- The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
- While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.
Claims (15)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/647,963 US20040199567A1 (en) | 2003-02-18 | 2003-08-26 | System and method for integrating multiserver platforms |
US14/153,179 US20140129732A1 (en) | 2003-02-18 | 2014-01-13 | Integrated Multiserver Platforms |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US44865603P | 2003-02-18 | 2003-02-18 | |
US45683103P | 2003-03-21 | 2003-03-21 | |
US45871903P | 2003-03-28 | 2003-03-28 | |
US46301403P | 2003-04-15 | 2003-04-15 | |
US10/647,963 US20040199567A1 (en) | 2003-02-18 | 2003-08-26 | System and method for integrating multiserver platforms |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/153,179 Continuation US20140129732A1 (en) | 2003-02-18 | 2014-01-13 | Integrated Multiserver Platforms |
Publications (1)
Publication Number | Publication Date |
---|---|
US20040199567A1 true US20040199567A1 (en) | 2004-10-07 |
Family
ID=32738907
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/648,573 Abandoned US20040199569A1 (en) | 2003-02-18 | 2003-08-26 | Method and system for handling traffic for server systems |
US10/647,962 Expired - Fee Related US7519057B2 (en) | 2003-02-18 | 2003-08-26 | System and method for communicating using a multiserver platform |
US10/648,004 Expired - Fee Related US7966422B2 (en) | 2003-02-18 | 2003-08-26 | System and method for communicating between servers using a multi-server platform |
US10/647,963 Abandoned US20040199567A1 (en) | 2003-02-18 | 2003-08-26 | System and method for integrating multiserver platforms |
US12/423,333 Expired - Fee Related US8089899B2 (en) | 2003-02-18 | 2009-04-14 | System and method for communicating using a multiserver platform |
US14/153,179 Abandoned US20140129732A1 (en) | 2003-02-18 | 2014-01-13 | Integrated Multiserver Platforms |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/648,573 Abandoned US20040199569A1 (en) | 2003-02-18 | 2003-08-26 | Method and system for handling traffic for server systems |
US10/647,962 Expired - Fee Related US7519057B2 (en) | 2003-02-18 | 2003-08-26 | System and method for communicating using a multiserver platform |
US10/648,004 Expired - Fee Related US7966422B2 (en) | 2003-02-18 | 2003-08-26 | System and method for communicating between servers using a multi-server platform |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/423,333 Expired - Fee Related US8089899B2 (en) | 2003-02-18 | 2009-04-14 | System and method for communicating using a multiserver platform |
US14/153,179 Abandoned US20140129732A1 (en) | 2003-02-18 | 2014-01-13 | Integrated Multiserver Platforms |
Country Status (3)
Country | Link |
---|---|
US (6) | US20040199569A1 (en) |
EP (3) | EP1450537B1 (en) |
DE (2) | DE602004012633T2 (en) |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030223418A1 (en) * | 2002-06-04 | 2003-12-04 | Sachin Desai | Network packet steering |
US20040202182A1 (en) * | 2003-02-12 | 2004-10-14 | Martin Lund | Method and system to provide blade server load balancing using spare link bandwidth |
US20070083528A1 (en) * | 2000-09-13 | 2007-04-12 | Fortinet, Inc. | Switch management system and method |
EP1854250A2 (en) * | 2005-02-28 | 2007-11-14 | Blade Network Technologies, Inc. | Blade server system with at least one rack-switch having multiple switches interconnected and configured for management and operation as a single virtual switch |
US20070280239A1 (en) * | 2006-05-30 | 2007-12-06 | Martin Lund | Method and system for power control based on application awareness in a packet network switch |
US20070291755A1 (en) * | 2002-11-18 | 2007-12-20 | Fortinet, Inc. | Hardware-accelerated packet multicasting in a virtual routing system |
US20080320553A1 (en) * | 2004-11-18 | 2008-12-25 | Fortinet, Inc. | Managing hierarchically organized subscriber profiles |
US20090046728A1 (en) * | 2000-09-13 | 2009-02-19 | Fortinet, Inc. | System and method for delivering security services |
US20090091555A1 (en) * | 2007-10-07 | 2009-04-09 | International Business Machines Corporation | Non-Intrusive Capture And Display Of Objects Based On Contact Locality |
US20090225754A1 (en) * | 2004-09-24 | 2009-09-10 | Fortinet, Inc. | Scalable ip-services enabled multicast forwarding with efficient resource utilization |
US7720053B2 (en) | 2002-06-04 | 2010-05-18 | Fortinet, Inc. | Service processing switch |
US7761743B2 (en) | 2002-08-29 | 2010-07-20 | Fortinet, Inc. | Fault tolerant routing in a non-hot-standby configuration of a network routing system |
US7818452B2 (en) | 2000-09-13 | 2010-10-19 | Fortinet, Inc. | Distributed virtual system to support managed, network-based services |
US7885207B2 (en) | 2000-09-13 | 2011-02-08 | Fortinet, Inc. | Managing and provisioning virtual routers |
US7890663B2 (en) | 2001-06-28 | 2011-02-15 | Fortinet, Inc. | Identifying nodes in a ring network |
US7912936B2 (en) | 2000-09-13 | 2011-03-22 | Nara Rajagopalan | Managing interworking communications protocols |
US8111690B2 (en) | 2002-06-04 | 2012-02-07 | Google Inc. | Routing traffic through a virtual router-based network switch |
US8250357B2 (en) | 2000-09-13 | 2012-08-21 | Fortinet, Inc. | Tunnel interface for securing traffic over a network |
US8260918B2 (en) | 2000-09-13 | 2012-09-04 | Fortinet, Inc. | Packet routing system and method |
US20130100967A1 (en) * | 2011-09-22 | 2013-04-25 | Aviat U.S. Inc. | Systems and Methods for Synchronization of Clock Signals |
US8848718B2 (en) | 2002-06-04 | 2014-09-30 | Google Inc. | Hierarchical metering in a virtual router-based network switch |
US9509638B2 (en) | 2003-08-27 | 2016-11-29 | Fortinet, Inc. | Heterogeneous media packet bridging |
Families Citing this family (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7124171B1 (en) * | 2002-05-23 | 2006-10-17 | Emc Corporation | In a networked computing cluster storage system and plurality of servers sharing files, in the event of server unavailability, transferring a floating IP network address from first server to second server to access area of data |
US20040199569A1 (en) * | 2003-02-18 | 2004-10-07 | Mohan Kalkunte | Method and system for handling traffic for server systems |
US20040181601A1 (en) * | 2003-03-14 | 2004-09-16 | Palsamy Sakthikumar | Peripheral device sharing |
US7738242B2 (en) * | 2004-01-08 | 2010-06-15 | Hewlett-Packard Development Company, L.P. | System and method for displaying chassis component information |
US20060048163A1 (en) * | 2004-08-27 | 2006-03-02 | Thierry Bessis | Method for routing messages between servers located on the same board |
US7519693B2 (en) * | 2004-11-18 | 2009-04-14 | International Business Machines Corporation | Apparatus, system, and method for integrating an enclosure |
US7899057B2 (en) | 2006-04-28 | 2011-03-01 | Jds Uniphase Corporation | Systems for ordering network packets |
US20060264178A1 (en) * | 2005-05-20 | 2006-11-23 | Noble Gayle L | Wireless diagnostic systems |
US8107822B2 (en) * | 2005-05-20 | 2012-01-31 | Finisar Corporation | Protocols for out-of-band communication |
US7822127B1 (en) * | 2006-05-15 | 2010-10-26 | Super Micro Computer, Inc. | Method and apparatus for minimizing signal loss in transit |
US8213333B2 (en) * | 2006-07-12 | 2012-07-03 | Chip Greel | Identifying and resolving problems in wireless device configurations |
US7584325B2 (en) * | 2006-07-26 | 2009-09-01 | International Business Machines Corporation | Apparatus, system, and method for providing a RAID storage system in a processor blade enclosure |
CN101227355B (en) * | 2006-08-16 | 2010-06-09 | 环达电脑(上海)有限公司 | Clustering system and system management architecture thereof |
US8526821B2 (en) | 2006-12-29 | 2013-09-03 | Finisar Corporation | Transceivers for testing networks and adapting to device changes |
CN101669380B (en) * | 2007-04-02 | 2013-11-27 | 艾利森电话股份有限公司 | Scalability and redundancy in MSC-server blade cluster |
US8625592B2 (en) * | 2008-02-26 | 2014-01-07 | Cisco Technology, Inc. | Blade switch with scalable interfaces |
US8151273B2 (en) * | 2008-08-28 | 2012-04-03 | Microsoft Corporation | Environment wide configuration system |
CN101853185B (en) | 2009-03-30 | 2015-07-08 | 华为技术有限公司 | Blade server and service dispatching method thereof |
US8139492B1 (en) | 2009-06-09 | 2012-03-20 | Juniper Networks, Inc. | Local forwarding bias in a multi-chassis router |
US8429316B1 (en) * | 2009-07-31 | 2013-04-23 | Marvell International Ltd. | Switch low power state in a blade server system |
US8817614B1 (en) * | 2010-09-16 | 2014-08-26 | Vasona Networks Inc. | Policy enforcer having load balancing capabilities |
JP5687959B2 (en) * | 2011-06-20 | 2015-03-25 | 株式会社日立製作所 | I / O device sharing method and apparatus |
CN103186409A (en) * | 2011-12-30 | 2013-07-03 | 英业达集团(天津)电子技术有限公司 | Virtual machine deployment system |
DE102012200042A1 (en) * | 2012-01-03 | 2013-07-04 | Airbus Operations Gmbh | SERVER SYSTEM, AIR OR ROOM VEHICLE AND METHOD |
CN103685382B (en) * | 2012-09-12 | 2017-01-25 | 中兴通讯股份有限公司 | Calling method and system of inter-clerk cross-blade server |
US9591015B1 (en) * | 2014-03-28 | 2017-03-07 | Fireeye, Inc. | System and method for offloading packet processing and static analysis operations |
US10805340B1 (en) | 2014-06-26 | 2020-10-13 | Fireeye, Inc. | Infection vector and malware tracking with an interactive user display |
US9690933B1 (en) | 2014-12-22 | 2017-06-27 | Fireeye, Inc. | Framework for classifying an object as malicious with machine learning for deploying updated predictive models |
US9838417B1 (en) | 2014-12-30 | 2017-12-05 | Fireeye, Inc. | Intelligent context aware user interaction for malware detection |
US10148693B2 (en) | 2015-03-25 | 2018-12-04 | Fireeye, Inc. | Exploit detection system |
WO2017052648A1 (en) * | 2015-09-25 | 2017-03-30 | Intel Corporation | Microelectronic Package with Wireless Interconnect |
US10496291B2 (en) | 2015-12-18 | 2019-12-03 | Sap Se | Maintaining data integrity during data migration |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020188718A1 (en) * | 2001-05-04 | 2002-12-12 | Rlx Technologies, Inc. | Console information storage system and method |
US20030030988A1 (en) * | 2001-08-10 | 2003-02-13 | Garnett Paul J. | Computer systems |
US20030061382A1 (en) * | 2001-09-21 | 2003-03-27 | Dell Products L.P. | System and method for naming hosts in a distributed data processing system |
US20030231625A1 (en) * | 2002-06-13 | 2003-12-18 | International Business Machines Corporation | Selective header field dispatch in a network processing system |
US20040030766A1 (en) * | 2002-08-12 | 2004-02-12 | Michael Witkowski | Method and apparatus for switch fabric configuration |
US7085961B2 (en) * | 2002-11-25 | 2006-08-01 | Quanta Computer Inc. | Redundant management board blade server management system |
US7188209B2 (en) * | 2003-04-18 | 2007-03-06 | Nextio, Inc. | Apparatus and method for sharing I/O endpoints within a load store fabric by encapsulation of domain information in transaction layer packets |
Family Cites Families (46)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5920566A (en) * | 1997-06-30 | 1999-07-06 | Sun Microsystems, Inc. | Routing in a multi-layer distributed network element |
US6188571B1 (en) * | 1997-11-03 | 2001-02-13 | Aiwa Raid Technology, Inc. | High density RAID subsystem with highly integrated controller |
US6266335B1 (en) * | 1997-12-19 | 2001-07-24 | Cyberiq Systems | Cross-platform server clustering using a network flow switch |
US8516055B2 (en) * | 1998-05-29 | 2013-08-20 | Research In Motion Limited | System and method for pushing information from a host system to a mobile data communication device in a wireless data network |
US6510164B1 (en) * | 1998-11-16 | 2003-01-21 | Sun Microsystems, Inc. | User-level dedicated interface for IP applications in a data packet switching and load balancing system |
US6208647B1 (en) * | 1999-04-14 | 2001-03-27 | Verizon Laboratories Inc. | Multicast extension to data link layer protocols |
US6597693B1 (en) * | 1999-05-21 | 2003-07-22 | Advanced Micro Devices, Inc. | Common scalable queuing and dequeuing architecture and method relative to network switch data rate |
US6650641B1 (en) * | 1999-07-02 | 2003-11-18 | Cisco Technology, Inc. | Network address translation using a forwarding agent |
US6735169B1 (en) * | 1999-07-02 | 2004-05-11 | Cisco Technology, Inc. | Cascading multiple services on a forwarding agent |
US6574240B1 (en) * | 2000-01-19 | 2003-06-03 | Advanced Micro Devices, Inc. | Apparatus and method for implementing distributed layer 3 learning in a network switch |
BR0108899A (en) * | 2000-03-03 | 2005-10-18 | Qualcomm Inc | Method and apparatus for participating in group communication services in an existing communication system |
US8380854B2 (en) * | 2000-03-21 | 2013-02-19 | F5 Networks, Inc. | Simplified method for processing multiple connections from the same client |
US7111076B2 (en) * | 2000-04-13 | 2006-09-19 | Intel Corporation | System using transform template and XML document type definition for transforming message and its reply |
US7079537B1 (en) * | 2000-04-25 | 2006-07-18 | Advanced Micro Devices, Inc. | Layer 3 switching logic architecture in an integrated network switch |
US6816905B1 (en) * | 2000-11-10 | 2004-11-09 | Galactic Computing Corporation Bvi/Bc | Method and system for providing dynamic hosted service management across disparate accounts/sites |
US20020107971A1 (en) * | 2000-11-07 | 2002-08-08 | Bailey Brian W. | Network transport accelerator |
US7236490B2 (en) * | 2000-11-17 | 2007-06-26 | Foundry Networks, Inc. | Backplane interface adapter |
US20020085567A1 (en) * | 2000-12-28 | 2002-07-04 | Maple Optical Systems, Inc. | Metro switch and method for transporting data configured according to multiple different formats |
US7984147B2 (en) * | 2000-12-29 | 2011-07-19 | Hewlett-Packard Development Company, L.P. | Apparatus and method for identifying a requested level of service for a transaction |
US7339786B2 (en) | 2001-03-05 | 2008-03-04 | Intel Corporation | Modular server architecture with Ethernet routed across a backplane utilizing an integrated Ethernet switch module |
US7133869B2 (en) * | 2001-03-06 | 2006-11-07 | Knowledge Vector, Inc. | Methods and systems for and defining and distributing information alerts |
AU2002306749A1 (en) * | 2001-03-13 | 2002-09-24 | Shiv Balakrishnan | An architecture and protocol for a wireless communication network to provide scalable web services to mobile access devices |
WO2002091688A1 (en) * | 2001-05-07 | 2002-11-14 | Vitesse Semiconductor Corporation | A data switching system |
US7102996B1 (en) * | 2001-05-24 | 2006-09-05 | F5 Networks, Inc. | Method and system for scaling network traffic managers |
US8004971B1 (en) * | 2001-05-24 | 2011-08-23 | F5 Networks, Inc. | Method and system for scaling network traffic managers using connection keys |
US6950895B2 (en) * | 2001-06-13 | 2005-09-27 | Intel Corporation | Modular server architecture |
US7003563B2 (en) * | 2001-11-02 | 2006-02-21 | Hewlett-Packard Development Company, L.P. | Remote management system for multiple servers |
US6904482B2 (en) * | 2001-11-20 | 2005-06-07 | Intel Corporation | Common boot environment for a modular server system |
JP4153201B2 (en) * | 2001-12-19 | 2008-09-24 | 富士通株式会社 | Communication control method, communication system, and computer program |
US6983303B2 (en) * | 2002-01-31 | 2006-01-03 | Hewlett-Packard Development Company, Lp. | Storage aggregator for enhancing virtualization in data storage networks |
US7321926B1 (en) * | 2002-02-11 | 2008-01-22 | Extreme Networks | Method of and system for allocating resources to resource requests |
US7584262B1 (en) * | 2002-02-11 | 2009-09-01 | Extreme Networks | Method of and system for allocating resources to resource requests based on application of persistence policies |
US7194619B2 (en) * | 2002-03-26 | 2007-03-20 | International Business Machines Corporation | Remotely booting devices in a dense server environment without manually installing authentication parameters on the devices to be booted |
US7127058B2 (en) * | 2002-03-27 | 2006-10-24 | Nortel Networks Limited | Managing communications in a call center |
US6931568B2 (en) * | 2002-03-29 | 2005-08-16 | International Business Machines Corporation | Fail-over control in a computer system having redundant service processors |
US6848034B2 (en) * | 2002-04-04 | 2005-01-25 | International Business Machines Corporation | Dense server environment that shares an IDE drive |
US7171479B2 (en) * | 2002-04-26 | 2007-01-30 | International Business Machines Corporation | Efficient delivery of boot code images from a network server |
US7490162B1 (en) * | 2002-05-15 | 2009-02-10 | F5 Networks, Inc. | Method and system for forwarding messages received at a traffic manager |
US7124163B2 (en) * | 2002-05-24 | 2006-10-17 | Convedia Corporation | Data server |
JP4406604B2 (en) * | 2002-06-11 | 2010-02-03 | アシシュ エイ パンドヤ | High performance IP processor for TCP / IP, RDMA, and IP storage applications |
US7139381B2 (en) * | 2002-06-25 | 2006-11-21 | Nortel Networks Limited | Method and apparatus for initiating telephony contact |
US7225247B2 (en) * | 2002-10-17 | 2007-05-29 | Intel Corporation | Serial port redirection using a management controller |
AU2002348946A1 (en) * | 2002-10-18 | 2003-06-10 | Nokia Corporation | Selectively recalling sent messages |
US6931475B2 (en) * | 2002-11-18 | 2005-08-16 | Quanta Computer Inc. | Blade server system with KVM switches |
US20040199569A1 (en) | 2003-02-18 | 2004-10-07 | Mohan Kalkunte | Method and system for handling traffic for server systems |
US8565088B1 (en) * | 2006-02-01 | 2013-10-22 | F5 Networks, Inc. | Selectively enabling packet concatenation based on a transaction boundary |
-
2003
- 2003-08-26 US US10/648,573 patent/US20040199569A1/en not_active Abandoned
- 2003-08-26 US US10/647,962 patent/US7519057B2/en not_active Expired - Fee Related
- 2003-08-26 US US10/648,004 patent/US7966422B2/en not_active Expired - Fee Related
- 2003-08-26 US US10/647,963 patent/US20040199567A1/en not_active Abandoned
-
2004
- 2004-01-28 DE DE602004012633T patent/DE602004012633T2/en not_active Expired - Lifetime
- 2004-01-28 DE DE602004011413T patent/DE602004011413T2/en not_active Expired - Lifetime
- 2004-01-28 EP EP04001857A patent/EP1450537B1/en not_active Expired - Fee Related
- 2004-01-28 EP EP04001858A patent/EP1450538B1/en not_active Expired - Fee Related
- 2004-01-28 EP EP04001859A patent/EP1450539B1/en not_active Expired - Fee Related
-
2009
- 2009-04-14 US US12/423,333 patent/US8089899B2/en not_active Expired - Fee Related
-
2014
- 2014-01-13 US US14/153,179 patent/US20140129732A1/en not_active Abandoned
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020188718A1 (en) * | 2001-05-04 | 2002-12-12 | Rlx Technologies, Inc. | Console information storage system and method |
US20030030988A1 (en) * | 2001-08-10 | 2003-02-13 | Garnett Paul J. | Computer systems |
US20030061382A1 (en) * | 2001-09-21 | 2003-03-27 | Dell Products L.P. | System and method for naming hosts in a distributed data processing system |
US20030231625A1 (en) * | 2002-06-13 | 2003-12-18 | International Business Machines Corporation | Selective header field dispatch in a network processing system |
US20040030766A1 (en) * | 2002-08-12 | 2004-02-12 | Michael Witkowski | Method and apparatus for switch fabric configuration |
US7085961B2 (en) * | 2002-11-25 | 2006-08-01 | Quanta Computer Inc. | Redundant management board blade server management system |
US7188209B2 (en) * | 2003-04-18 | 2007-03-06 | Nextio, Inc. | Apparatus and method for sharing I/O endpoints within a load store fabric by encapsulation of domain information in transaction layer packets |
Cited By (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090046728A1 (en) * | 2000-09-13 | 2009-02-19 | Fortinet, Inc. | System and method for delivering security services |
US9853948B2 (en) | 2000-09-13 | 2017-12-26 | Fortinet, Inc. | Tunnel interface for securing traffic over a network |
US9667604B2 (en) | 2000-09-13 | 2017-05-30 | Fortinet, Inc. | Tunnel interface for securing traffic over a network |
US20070083528A1 (en) * | 2000-09-13 | 2007-04-12 | Fortinet, Inc. | Switch management system and method |
US9391964B2 (en) | 2000-09-13 | 2016-07-12 | Fortinet, Inc. | Tunnel interface for securing traffic over a network |
US8320279B2 (en) | 2000-09-13 | 2012-11-27 | Fortinet, Inc. | Managing and provisioning virtual routers |
US8260918B2 (en) | 2000-09-13 | 2012-09-04 | Fortinet, Inc. | Packet routing system and method |
US8250357B2 (en) | 2000-09-13 | 2012-08-21 | Fortinet, Inc. | Tunnel interface for securing traffic over a network |
US8069233B2 (en) | 2000-09-13 | 2011-11-29 | Fortinet, Inc. | Switch management system and method |
US7912936B2 (en) | 2000-09-13 | 2011-03-22 | Nara Rajagopalan | Managing interworking communications protocols |
US7885207B2 (en) | 2000-09-13 | 2011-02-08 | Fortinet, Inc. | Managing and provisioning virtual routers |
US7818452B2 (en) | 2000-09-13 | 2010-10-19 | Fortinet, Inc. | Distributed virtual system to support managed, network-based services |
US7890663B2 (en) | 2001-06-28 | 2011-02-15 | Fortinet, Inc. | Identifying nodes in a ring network |
US20070147368A1 (en) * | 2002-06-04 | 2007-06-28 | Fortinet, Inc. | Network packet steering via configurable association of processing resources and netmods or line interface ports |
US9967200B2 (en) | 2002-06-04 | 2018-05-08 | Fortinet, Inc. | Service processing switch |
US8306040B2 (en) | 2002-06-04 | 2012-11-06 | Fortinet, Inc. | Network packet steering via configurable association of processing resources and network interfaces |
US7720053B2 (en) | 2002-06-04 | 2010-05-18 | Fortinet, Inc. | Service processing switch |
US20030223418A1 (en) * | 2002-06-04 | 2003-12-04 | Sachin Desai | Network packet steering |
US8111690B2 (en) | 2002-06-04 | 2012-02-07 | Google Inc. | Routing traffic through a virtual router-based network switch |
US8848718B2 (en) | 2002-06-04 | 2014-09-30 | Google Inc. | Hierarchical metering in a virtual router-based network switch |
US8068503B2 (en) * | 2002-06-04 | 2011-11-29 | Fortinet, Inc. | Network packet steering via configurable association of processing resources and netmods or line interface ports |
US7203192B2 (en) * | 2002-06-04 | 2007-04-10 | Fortinet, Inc. | Network packet steering |
US8412982B2 (en) | 2002-08-29 | 2013-04-02 | Google Inc. | Fault tolerant routing in a non-hot-standby configuration of a network routing system |
US8819486B2 (en) | 2002-08-29 | 2014-08-26 | Google Inc. | Fault tolerant routing in a non-hot-standby configuration of a network routing system |
US7761743B2 (en) | 2002-08-29 | 2010-07-20 | Fortinet, Inc. | Fault tolerant routing in a non-hot-standby configuration of a network routing system |
US7933269B2 (en) | 2002-11-18 | 2011-04-26 | Fortinet, Inc. | Hardware-accelerated packet multicasting in a virtual routing system |
US20070291755A1 (en) * | 2002-11-18 | 2007-12-20 | Fortinet, Inc. | Hardware-accelerated packet multicasting in a virtual routing system |
US20040202182A1 (en) * | 2003-02-12 | 2004-10-14 | Martin Lund | Method and system to provide blade server load balancing using spare link bandwidth |
US20110066729A1 (en) * | 2003-02-12 | 2011-03-17 | Martin Lund | Method and system to provide blade server load balancing using spare link bandwidth |
US7835363B2 (en) * | 2003-02-12 | 2010-11-16 | Broadcom Corporation | Method and system to provide blade server load balancing using spare link bandwidth |
US8102874B2 (en) | 2003-02-12 | 2012-01-24 | Broadcom Corporation | Method and system to provide blade server load balancing using spare link bandwidth |
US9509638B2 (en) | 2003-08-27 | 2016-11-29 | Fortinet, Inc. | Heterogeneous media packet bridging |
US9853917B2 (en) | 2003-08-27 | 2017-12-26 | Fortinet, Inc. | Heterogeneous media packet bridging |
US7881244B2 (en) | 2004-09-24 | 2011-02-01 | Fortinet, Inc. | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US8369258B2 (en) | 2004-09-24 | 2013-02-05 | Fortinet, Inc. | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US20090225754A1 (en) * | 2004-09-24 | 2009-09-10 | Fortinet, Inc. | Scalable ip-services enabled multicast forwarding with efficient resource utilization |
US8213347B2 (en) | 2004-09-24 | 2012-07-03 | Fortinet, Inc. | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US7876683B2 (en) | 2004-11-18 | 2011-01-25 | Fortinet, Inc. | Managing hierarchically organized subscriber profiles |
US20080317231A1 (en) * | 2004-11-18 | 2008-12-25 | Fortinet, Inc. | Managing hierarchically organized subscriber profiles |
US20080317040A1 (en) * | 2004-11-18 | 2008-12-25 | Fortinet, Inc. | Managing hierarchically organized subscriber profiles |
US7843813B2 (en) | 2004-11-18 | 2010-11-30 | Fortinet, Inc. | Managing hierarchically organized subscriber profiles |
US7869361B2 (en) | 2004-11-18 | 2011-01-11 | Fortinet, Inc. | Managing hierarchically organized subscriber profiles |
US7961615B2 (en) | 2004-11-18 | 2011-06-14 | Fortinet, Inc. | Managing hierarchically organized subscriber profiles |
US20090007228A1 (en) * | 2004-11-18 | 2009-01-01 | Fortinet, Inc. | Managing hierarchically organized subscriber profiles |
US20080320553A1 (en) * | 2004-11-18 | 2008-12-25 | Fortinet, Inc. | Managing hierarchically organized subscriber profiles |
US20080275975A1 (en) * | 2005-02-28 | 2008-11-06 | Blade Network Technologies, Inc. | Blade Server System with at Least One Rack-Switch Having Multiple Switches Interconnected and Configured for Management and Operation as a Single Virtual Switch |
EP1854250A2 (en) * | 2005-02-28 | 2007-11-14 | Blade Network Technologies, Inc. | Blade server system with at least one rack-switch having multiple switches interconnected and configured for management and operation as a single virtual switch |
US8194534B2 (en) | 2005-02-28 | 2012-06-05 | International Business Machines Corporation | Blade server system with at least one rack-switch having multiple switches interconnected and configured for management and operation as a single virtual switch |
EP1854250A4 (en) * | 2005-02-28 | 2010-10-06 | Blade Network Technologies Inc | Blade server system with at least one rack-switch having multiple switches interconnected and configured for management and operation as a single virtual switch |
US8437352B2 (en) * | 2006-05-30 | 2013-05-07 | Broadcom Corporation | Method and system for power control based on application awareness in a packet network switch |
US20070280239A1 (en) * | 2006-05-30 | 2007-12-06 | Martin Lund | Method and system for power control based on application awareness in a packet network switch |
US20090091555A1 (en) * | 2007-10-07 | 2009-04-09 | International Business Machines Corporation | Non-Intrusive Capture And Display Of Objects Based On Contact Locality |
US9014215B2 (en) * | 2011-09-22 | 2015-04-21 | Aviat U.S., Inc. | Systems and methods for synchronization of clock signals |
US20130100967A1 (en) * | 2011-09-22 | 2013-04-25 | Aviat U.S. Inc. | Systems and Methods for Synchronization of Clock Signals |
US9608754B2 (en) | 2011-09-22 | 2017-03-28 | Aviat U.S., Inc. | Systems and methods for synchronization of clock signals |
Also Published As
Publication number | Publication date |
---|---|
US7966422B2 (en) | 2011-06-21 |
US20040160900A1 (en) | 2004-08-19 |
EP1450539A2 (en) | 2004-08-25 |
US20140129732A1 (en) | 2014-05-08 |
EP1450538A3 (en) | 2005-03-23 |
DE602004011413D1 (en) | 2008-03-13 |
EP1450537B1 (en) | 2008-03-26 |
DE602004012633T2 (en) | 2009-05-14 |
DE602004012633D1 (en) | 2008-05-08 |
EP1450537A2 (en) | 2004-08-25 |
EP1450539A3 (en) | 2005-03-23 |
EP1450538A2 (en) | 2004-08-25 |
EP1450537A3 (en) | 2005-03-23 |
US20090201927A1 (en) | 2009-08-13 |
EP1450539B1 (en) | 2013-03-13 |
EP1450538B1 (en) | 2008-01-23 |
US7519057B2 (en) | 2009-04-14 |
US8089899B2 (en) | 2012-01-03 |
DE602004011413T2 (en) | 2009-01-29 |
US20040199568A1 (en) | 2004-10-07 |
US20040199569A1 (en) | 2004-10-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1450537B1 (en) | System and method for integrating multiserver platforms | |
EP1484888B1 (en) | Method and system to provide blade server load balancing using spare link bandwidth | |
EP1981206B1 (en) | An exchange system and method for increasing exchange bandwidth | |
US6662254B1 (en) | System architecture | |
US8046465B2 (en) | Flow scheduling for network application apparatus | |
EP1665652B1 (en) | Virtual switch for providing a single point of management | |
CN101150413B (en) | A multi-frame cascading system and method for ATCA knife server | |
US8135806B2 (en) | Virtual system configuration | |
WO2007022238A2 (en) | High-availability networking with intelligent failover | |
RU2513918C1 (en) | Cluster router and cluster routing method | |
CN1937782B (en) | Frame device and its message transmitting method | |
WO2011047373A1 (en) | Method and apparatus for increasing overall aggregate capacity of a network | |
US5982744A (en) | High density unit shelf and method | |
US6608812B1 (en) | Trunk arrangement in a computer network with intra trunk switch connections | |
KR100560929B1 (en) | The Ethernet Switching Board System And Method For Duplexing That Board | |
JPS61196643A (en) | Data communication circuit network | |
US7716498B1 (en) | Power control in a data storage system | |
KR100912819B1 (en) | Protection apparatus and method of MSxP at ATCA platform based Optical Transport HierarchyOTH | |
US20230188193A1 (en) | Improved Interface in Series-Connected Radios | |
KR100596384B1 (en) | Interface module for implementing single high speed interface by aggregating plurality of low speed interfaces and communication device including the same | |
CN115134215A (en) | Server BMC dynamic network linkage management method and management system | |
CN116938693A (en) | User migration method, device, system and storage medium | |
EP1460819A2 (en) | Method and system for handling traffic for server systems | |
CN103248585A (en) | High efficient server relay interchanging chip |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LUND, MARTIN;REEL/FRAME:014187/0157 Effective date: 20020805 |
|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: RE-RECORD TO CORRECT THE EXECUTION DATE, PREVIOUSLY RECORDED ON REEL 014187 FRAME 0157, ASSIGNOR CONFIRMS THE ASSIGNMENT OF THE ENTIRE INTEREST.;ASSIGNOR:LUND, MARTIN;REEL/FRAME:014447/0015 Effective date: 20030805 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001 Effective date: 20160201 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001 Effective date: 20160201 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD., SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 |
|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041712/0001 Effective date: 20170119 |