US20060013248A1 - Switching device interfaces - Google Patents
Switching device interfacesDownload PDFInfo
- Publication number
- US20060013248A1 US20060013248A1US11/084,217US8421705AUS2006013248A1US 20060013248 A1US20060013248 A1US 20060013248A1US 8421705 AUS8421705 AUS 8421705AUS 2006013248 A1US2006013248 A1US 2006013248A1
- Authority
- US
- United States
- Prior art keywords
- physical interface
- interface
- physical
- interfaces
- switching
- 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
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0025—Provisions for signalling
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/55—Prevention, detection or correction of errors
- H04L49/552—Prevention, detection or correction of errors by ensuring the integrity of packets received through redundant connections
- 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
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5625—Operations, administration and maintenance [OAM]
- H04L2012/5627—Fault tolerance and recovery
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
- H04L49/3009—Header conversion, routing tables or routing tags
Definitions
- This inventionrelates generally to interfaces on a network device.
- Network deviceshave physical interfaces that are subject to failure. When such an interface fails, a network device can be cut-off from the network. This is particularly problematic in the case of a router, where failure of a single physical interface can make a whole branch of the network inaccessible to other devices.
- a deviceis switched from a first physical interface on the device (for example, a failed interface) to a second physical interface on the device based on information in an interface redundancy group.
- the information in the interface redundancy groupidentifies the first physical interface as a primary interface for the device and the second physical interface as a secondary interface for the device.
- the interface redundancy groupmay include information defining the primary interface for the device and one or more secondary interfaces for the device.
- An eventmay be detected at the first physical interface, and switching may be performed in response to the event.
- the eventmay comprise a failure of the first physical interface.
- the first physical interfacemay be associated with a driver and a signaling stack, and the failure of the first physical interface may comprise a failure of the driver and/or the signaling stack.
- the driver and the signaling stackmay be monitored in order to detect failures therein.
- the eventmay comprise receipt of a slot failure at the first physical interface.
- the second physical interfacePrior to switching, the second physical interface may operate in a passive mode during which the second physical interface is dormant. Prior to switching, the second physical interface may operate in an active mode during which the second physical interface is communicating over a network.
- the first physical interfacemay support one or more network layer interfaces. Following switching, the second physical interface may support the one or more network layer interfaces formerly supported by the first physical interface.
- the first and second physical interfacesmay comprise asynchronous transfer mode (“ATM”) physical interfaces.
- ATMsynchronous transfer mode
- the first and second physical interfacesmay be resident on a single network router.
- the second physical-interfacemay assume responsibilities of the first physical interface. These responsibilities may include routing and/or bridging functions. Following switching, the second physical interface may be configured in a same manner as the first physical interface was configured prior to switching.
- the devicemay include a third physical interface, and the interface redundancy group may identify the third physical interface as a tertiary interface. The device may be switched from the second physical interface to the third physical interface in response to an event. Following switching, the third physical interface may assume responsibilities of the first and second physical interfaces. These responsibilities may include routing and/or bridging functions.
- physical interfaces on a single deviceare switched by designating a physical interface on the device as a high priority physical interface, and determining if the high priority physical interface is available. The device is switched from a lower priority physical interface to the high priority physical interface when the high priority physical interface is available.
- Switchingmay be performed automatically in response to the high priority interface being available.
- the high priority physical interfacemay be monitored to determine if the high priority physical interface is available.
- a deviceis switched from a first ATM physical interface on the device to a second ATM physical interface on the device based on information in an interface redundancy group.
- the information in the interface redundancy groupidentifies the first ATM physical interface as a primary interface for the device and the second ATM physical interface as a secondary interface for the device.
- ATM network layer interfacesare established over the second physical interface that correspond to ATM network layer interfaces that were established over the first ATM physical interface prior to switching.
- FIG. 1shows a network system, which includes a router having switchable physical interfaces.
- FIG. 2shows virtual circuits supported by the physical interfaces on the router.
- FIG. 3is a flow diagram showing a process for switching a physical interface on the router in “passive” mode.
- FIG. 4shows an alternative connection of the virtual circuits to the physical interfaces on the router.
- FIG. 5is a flow diagram showing a process for switching a physical interface on the router in “active” mode.
- FIG. 6shows the configuration of the virtual circuits after the switching performed in FIG. 5 .
- FIG. 7is a flow diagram showing a process for switching a physical interface on the router based on priority.
- FIG. 8shows a router having three physical interfaces and redundancy groups therefor.
- Network system 10includes router 12 , switches 14 and 16 , workstations 18 , 20 and 22 , and network 24 .
- Network 24is an asynchronous transfer mode (“ATM”) wide area network (“WAN”).
- ATMis a connection-oriented protocol, meaning that connections are established between devices before data and/or communications can be transmitted between the devices.
- the network layer interfacecomprises virtual circuits, over which data packets (in ATM parlance, “cells”) are transmitted among devices coupled to network 24 , such as router 12 and switches 14 and 16 .
- Virtual circuitscan be established by protocols such as ELANs (Emulated Local Area Networks) on network 24 .
- Switches 14 and 16interface workstations 20 and 22 , respectively, to network 24 .
- Each switch 14 and 16is an electronic device that routes cells between network 24 and a corresponding workstation.
- Workstations 18 , 20 and 22are personal computers (“PCs”) or other devices that are capable of receiving cells from network 24 , processing cells, and transmitting cells to network 24 .
- PCspersonal computers
- Router 12is a computer or other device that transmits packets/cells among workstations 18 , 20 and 22 via network 24 .
- router 12receives cells/packets from workstation 18 and, based on information in those cells/packets, routes the cells/packets to either workstation 20 or 22 (through an intervening switch and other hardware on network 24 ).
- ATM physical interfaces 26 a and 26 bare ports provided on router 12 for interfacing to network 24 . Although only two such interfaces are shown, any number may be provided. In system 10 of FIG. 1 , one of the interfaces (e.g., 26 a ) is designated as the primary interface for router 12 and the other (e.g., 26 b ) is designated as the secondary (or backup) interface. When the primary physical interface 26 a fails, the secondary physical interface. 26 b is switched in to take its place. A process to accomplish this is described below.
- Physical interfaces 26 a and 26 bare comprised of wires terminating in connectors, such as an OC-3/OC-12 connector, which mate to corresponding receptacles on router 12 .
- One or more network layer interfacesare established by router 12 over each physical interface 26 a and 26 b for communication to, and over, network 24 .
- ATM line drivers 30 a and 30 btransmit cells over corresponding physical interfaces 26 a and 26 b.
- router 12includes a processor 34 and a memory 36 connected by bus 38 (see view 40 ).
- Memory 36stores routing engines 42 a and 42 b , interface switching code 44 , and signaling stacks 46 a and 46 b .
- Processor 34executes instructions in this code to cause router 12 to perform the functions described below.
- Memory 36also stores interface redundancy group information 48 (described below).
- Signaling stacks 46 a and 46 bare blocks of code, associated with corresponding physical interfaces 26 a and 26 b , for establishing virtual connections for the network layer interfaces over the physical interfaces. As noted, one or more network layer interfaces may be configured over a single ATM physical interface 26 a and 26 b.
- Routing engine 42 aroutes cells over physical interface 26 a and routing engine 42 b routes cells over physical interface 26 b .
- Routing engines 42 a and 42 bexamine destination information in the cells and route the cells over appropriate interfaces. Examples of routing engines that may be used are “ARE” (ATM Routing Engine) and the 5782 Centillion Multiprotocol Engine.
- Interface redundancy group information 48defines which physical interface is the primary interface (e.g., 26 a ) and which is the secondary interface (e.g., 26 b ). This information may be input manually at router 12 via configuration software such as Site Managers or Bay Command Consoles (“BCC”). This software is used by network administrators to configure network devices. Alternatively, interface redundancy group information 48 may be downloaded from a remote location such as network 24 or workstation 18 or set via interface switching code 44 .
- configuration softwaresuch as Site Managers or Bay Command Consoles (“BCC”). This software is used by network administrators to configure network devices.
- interface redundancy group information 48may be downloaded from a remote location such as network 24 or workstation 18 or set via interface switching code 44 .
- Interface redundancy group information 48includes user-defined redundancy groups. These redundancy groups assign priority to the interfaces. In the case of a two-interface router, such as router 12 , there are two possible groups. For example, physical interface 26 a is configured as the primary interface and physical interface 26 b is configured as the secondary interface. The routing engine for each interface is configured to know the role of the interface in each redundancy group. Representative code to configure routing engines is provided in the Appendix.
- Table 1shows an example of redundancy groups for a router having four physical interfaces “Interface 1”, “Interface 2”, “Interface 3” and “Interface 4” (not shown).
- TABLE 1 Redundancy Primary Secondary Tertiary Group Interface Interface Interface 1 Interface 1 Interface 2 Interface 3 2 Interface 2 Interface 1 Interface 3 3 Interface 4 Interface 3For example, in redundancy group “1”, “Interface 1” acts as the primary interface; “Interface 2” acts as the secondary (first backup) interface and is used if. “Interface 1” fails; and “Interface 3” acts as the tertiary (or second backup) interface and is used if both “Interfaces 1” and “Interface 2” fail.
- interface switching code 44Detecting physical interface failure and switching from a primary to a secondary physical interface (or from a secondary to a tertiary physical interface, etc.) is performed by interface switching code 44 .
- the operation of interface switching code 44differs depending upon whether the secondary interface is in passive mode or active mode.
- Passive modeprior to switching, the secondary interface is dormant. That is, the secondary interface is not driving/receiving signals to/from network 24 .
- Passive modemay be set as the default mode of router 12 using Site Manager® or BCC®.
- FIG. 2a graphical representation of passive mode is shown.
- physical interface 26 ais configured as the primary interface and physical interface 26 b is configured as the secondary interface in passive mode. This configuration is set in interface redundancy group information 48 .
- lines 54 a to 54 hrepresent connections maintained by primary physical interface 26 a and lines 56 a to 56 h represent connections that are maintained by secondary physical interface 26 b after secondary interface 26 b -takes over the role of primary interface 26 b.
- Interface switching process 56is performed by interface switching code 44 to switch from primary physical interface 26 a to secondary physical interface 26 b .
- Process 56monitors 58 primary physical interface 26 a , including both driver 30 a and signaling stack 46 a , for specific “events”. These events can include, but are not limited to, receipt of a slot reset at primary physical interface 26 a and/or a failure of primary physical interface 26 a , such as a failure of driver 30 a and/or signaling stack 46 a.
- process 56switches 62 from primary physical interface 26 a to secondary physical interface 26 b (in accordance with interface redundancy group information 48 ).
- Switching 62is performed by enabling driver 30 b for secondary physical interface 26 b .
- secondary interface 26 bestablishes 63 the network layer interfaces to network 24 (in this example, ELANs 52 a to 52 h ), and assumes the responsibilities (including routing and bridging services) of primary interface 26 b . Switching between interfaces is performed as quickly as possible, e.g., within thirty seconds of failure or reset.
- signaling stack 46 btransmits cells over secondary physical interface 26 b to ELANs 52 a to 52 h .
- Primary physical interface 26 acan be repaired while secondary physical interface 26 b performs its functions.
- the secondary physical interface 26 bIn active mode, prior to switching, the secondary physical interface 26 b is already communicating over the network. Following failure of the primary physical interface 26 a , the secondary interface 26 b assumes the responsibilities of the primary interface 26 a . In particular, upon switching, code in the signaling stack establishes the network layer interfaces (e.g., over ELANs) of the primary interface 26 a , and assumes the routing and bridging functions of the primary interface 26 a.
- the network layer interfacese.g., over ELANs
- FIG. 4a graphical representation of active mode is shown.
- physical interface 26 ais the primary interface and physical interface 26 b is the secondary interface in active mode. This configuration is set in interface redundancy group information 48 . Since secondary physical interface 26 b is in active mode, prior to switching, it is providing network layer services over virtual circuits for ELANs 52 e to 52 h .
- Primary physical interface 26 ais supporting ELANs 52 a to 52 d.
- an interface switching process 66is shown, that is performed by interface switching code 44 to switch from primary physical interface 26 a to secondary physical interface 26 b .
- Interface switching process 66monitors 68 primary physical interface 26 a , including both driver 30 a and signaling stack 46 a , for specific events. These events are the same as those noted above for passive mode.
- process 66switches 72 from primary physical interface 26 a to secondary physical interface 26 b . Switching is performed in the manner described above; that is, enabling and disabling the drivers for the appropriate network interfaces.
- Interface switching process 66establishes 74 , over secondary physical interface 26 b , the network layer interfaces (in this case, ELANs 52 a to 52 d ) of primary physical interface 26 a .
- Secondary physical interface 26 bcontinues to perform its original routing and bridging functions over ELANs 52 e to 52 h . Now, however, secondary physical interface 26 b also performs the routing and bridging functions formerly performed by primary physical interface 26 a over ELANs 52 a to 52 d.
- signaling stack 46 btransmits cells over secondary physical interface 26 b to all of ELANs 52 a to 52 h . This is shown in FIG. 6 . Primary physical interface 26 a no longer transmits (hence no lines are shown between this interface and the ELANs in FIG. 6 ).
- ATM physical interfacesmay also be assigned relative priorities and switched on that basis.
- An option in router. 12may be set, e.g., by a user, to trigger automatic switching based on priority.
- the priority information upon which switching is basedmay be included in interface redundancy group information 48 , for example.
- a process 78is shown that is performed by interface switching code 44 to switch interfaces based on priority.
- Process 78designates 80 any number of physical interfaces on a sliding priority scale, from highest priority to lowest priority. In router 12 ( FIG. 2 ), only two physical interfaces are shown. For the sake of illustration, therefore, physical interface 26 a is designated 80 as high priority and physical interface 26 b is designated 80 as low priority.
- Process 78monitors 82 high priority physical interface 26 a to determine if it is up and running. If high priority physical interface 26 a is available 84 (i.e., it is not “down”), process 78 switches 86 from low priority physical interface 26 b to high priority physical interface 26 a . As a result, the “best available” interface on router 12 is used to provide network layer connections over network 24 . Process 60 may be incorporated into processes 56 and 66 to provide further enhanced switching capabilities.
- router 90has three physical interfaces 92 a , 92 b and 92 c organized into two interface redundancy groups 94 and 96 .
- Interfaces 92 a and 92 care in group 94 and interfaces 92 b and 92 c are in group 96 .
- interface 92 cis a backup for interfaces 92 a and 92 b . If either of interfaces 92 a and 92 b fail, then interface 92 c will assume the configuration of either (or both of) failed interfaces 92 a and 92 b.
- Switching in the case of more than two interfacesis performed in the same way as described in processes 56 , 66 and 78 , except that a decision must be made regarding which (lower priority) interface to switch for the primary interface. This decision is made based on interface availability and the priority of the various interfaces.
- the inventionis not limited to the specific hardware and software configurations described herein.
- the inventioncan be used outside the context of ATM WANs, and with network devices other than routers.
- network devicesother than routers.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- This invention relates generally to interfaces on a network device.
- Network devices have physical interfaces that are subject to failure. When such an interface fails, a network device can be cut-off from the network. This is particularly problematic in the case of a router, where failure of a single physical interface can make a whole branch of the network inaccessible to other devices.
- In one aspect of the invention, a device is switched from a first physical interface on the device (for example, a failed interface) to a second physical interface on the device based on information in an interface redundancy group. The information in the interface redundancy group identifies the first physical interface as a primary interface for the device and the second physical interface as a secondary interface for the device.
- The foregoing aspect of the invention may include one or more of the following features/functions.
- The interface redundancy group may include information defining the primary interface for the device and one or more secondary interfaces for the device. An event may be detected at the first physical interface, and switching may be performed in response to the event. The event may comprise a failure of the first physical interface. The first physical interface may be associated with a driver and a signaling stack, and the failure of the first physical interface may comprise a failure of the driver and/or the signaling stack. The driver and the signaling stack may be monitored in order to detect failures therein. The event may comprise receipt of a slot failure at the first physical interface.
- Prior to switching, the second physical interface may operate in a passive mode during which the second physical interface is dormant. Prior to switching, the second physical interface may operate in an active mode during which the second physical interface is communicating over a network. The first physical interface may support one or more network layer interfaces. Following switching, the second physical interface may support the one or more network layer interfaces formerly supported by the first physical interface. The first and second physical interfaces may comprise asynchronous transfer mode (“ATM”) physical interfaces. The first and second physical interfaces may be resident on a single network router.
- Following switching, the second physical-interface may assume responsibilities of the first physical interface. These responsibilities may include routing and/or bridging functions. Following switching, the second physical interface may be configured in a same manner as the first physical interface was configured prior to switching. The device may include a third physical interface, and the interface redundancy group may identify the third physical interface as a tertiary interface. The device may be switched from the second physical interface to the third physical interface in response to an event. Following switching, the third physical interface may assume responsibilities of the first and second physical interfaces. These responsibilities may include routing and/or bridging functions.
- In another aspect, physical interfaces on a single device are switched by designating a physical interface on the device as a high priority physical interface, and determining if the high priority physical interface is available. The device is switched from a lower priority physical interface to the high priority physical interface when the high priority physical interface is available.
- The foregoing aspect of the invention may include one or more of the following features/functions. Switching may be performed automatically in response to the high priority interface being available. The high priority physical interface may be monitored to determine if the high priority physical interface is available.
- In another aspect, a device is switched from a first ATM physical interface on the device to a second ATM physical interface on the device based on information in an interface redundancy group. The information in the interface redundancy group identifies the first ATM physical interface as a primary interface for the device and the second ATM physical interface as a secondary interface for the device. ATM network layer interfaces are established over the second physical interface that correspond to ATM network layer interfaces that were established over the first ATM physical interface prior to switching.
- This brief summary has been provided so that the nature of the invention can be understood quickly. A detailed description of illustrative embodiments of the invention is set forth below.
FIG. 1 shows a network system, which includes a router having switchable physical interfaces.FIG. 2 shows virtual circuits supported by the physical interfaces on the router.FIG. 3 is a flow diagram showing a process for switching a physical interface on the router in “passive” mode.FIG. 4 shows an alternative connection of the virtual circuits to the physical interfaces on the router.FIG. 5 is a flow diagram showing a process for switching a physical interface on the router in “active” mode.FIG. 6 shows the configuration of the virtual circuits after the switching performed inFIG. 5 .FIG. 7 is a flow diagram showing a process for switching a physical interface on the router based on priority.FIG. 8 shows a router having three physical interfaces and redundancy groups therefor.- Referring to
FIG. 1 , anetwork system 10 is shown.Network system 10 includesrouter 12,switches workstations network 24. - Network24 is an asynchronous transfer mode (“ATM”) wide area network (“WAN”). ATM is a connection-oriented protocol, meaning that connections are established between devices before data and/or communications can be transmitted between the devices. The network layer interface comprises virtual circuits, over which data packets (in ATM parlance, “cells”) are transmitted among devices coupled to
network 24, such asrouter 12 andswitches network 24. - Switches14 and16
interface workstations network 24. Eachswitch network 24 and a corresponding workstation.Workstations network 24, processing cells, and transmitting cells tonetwork 24. Router 12 is a computer or other device that transmits packets/cells amongworkstations network 24. For example,router 12 receives cells/packets fromworkstation 18 and, based on information in those cells/packets, routes the cells/packets to eitherworkstation 20 or22 (through an intervening switch and other hardware on network24).- ATM
physical interfaces router 12 for interfacing tonetwork 24. Although only two such interfaces are shown, any number may be provided. Insystem 10 ofFIG. 1 , one of the interfaces (e.g.,26a) is designated as the primary interface forrouter 12 and the other (e.g.,26b) is designated as the secondary (or backup) interface. When the primaryphysical interface 26afails, the secondary physical interface.26bis switched in to take its place. A process to accomplish this is described below. Physical interfaces router 12. One or more network layer interfaces are established byrouter 12 over eachphysical interface network 24.ATM line drivers physical interfaces - Included in
router 12 are aprocessor 34 and amemory 36 connected by bus38 (see view40).Memory 36stores routing engines interface switching code 44, and signalingstacks Processor 34 executes instructions in this code to causerouter 12 to perform the functions described below.Memory 36 also stores interface redundancy group information48 (described below). - Signaling stacks46aand46bare blocks of code, associated with corresponding
physical interfaces physical interface - Routing
engine 42aroutes cells overphysical interface 26aandrouting engine 42broutes cells overphysical interface 26b. Routingengines - Interface
redundancy group information 48 defines which physical interface is the primary interface (e.g.,26a) and which is the secondary interface (e.g.,26b). This information may be input manually atrouter 12 via configuration software such as Site Managers or Bay Command Consoles (“BCC”). This software is used by network administrators to configure network devices. Alternatively, interfaceredundancy group information 48 may be downloaded from a remote location such asnetwork 24 orworkstation 18 or set viainterface switching code 44. - Interface
redundancy group information 48 includes user-defined redundancy groups. These redundancy groups assign priority to the interfaces. In the case of a two-interface router, such asrouter 12, there are two possible groups. For example,physical interface 26ais configured as the primary interface andphysical interface 26bis configured as the secondary interface. The routing engine for each interface is configured to know the role of the interface in each redundancy group. Representative code to configure routing engines is provided in the Appendix. - In routers with more than two physical interfaces, interface redundancy groups become more complicated. Table 1 shows an example of redundancy groups for a router having four physical interfaces “
Interface 1”, “Interface 2”, “Interface 3” and “Interface 4” (not shown).TABLE 1 Redundancy Primary Secondary Tertiary Group Interface Interface Interface 1 Interface 1Interface 2Interface 32 Interface 2Interface 1Interface 33 Interface 4Interface 3—
For example, in redundancy group “1”, “Interface 1” acts as the primary interface; “Interface 2” acts as the secondary (first backup) interface and is used if. “Interface 1” fails; and “Interface 3” acts as the tertiary (or second backup) interface and is used if both “Interfaces 1” and “Interface 2” fail. - Detecting physical interface failure and switching from a primary to a secondary physical interface (or from a secondary to a tertiary physical interface, etc.) is performed by
interface switching code 44. The operation ofinterface switching code 44 differs depending upon whether the secondary interface is in passive mode or active mode. - Passive Mode
- In passive mode, prior to switching, the secondary interface is dormant. That is, the secondary interface is not driving/receiving signals to/from
network 24. Passive mode may be set as the default mode ofrouter 12 using Site Manager® or BCC®. - Referring to
FIG. 2 , a graphical representation of passive mode is shown. InFIG. 2 ,physical interface 26ais configured as the primary interface andphysical interface 26bis configured as the secondary interface in passive mode. This configuration is set in interfaceredundancy group information 48. InFIG. 2 ,lines 54ato54hrepresent connections maintained by primaryphysical interface 26aand lines56ato56hrepresent connections that are maintained by secondaryphysical interface 26baftersecondary interface 26b-takes over the role ofprimary interface 26b. - Referring to
FIG. 3 , aninterface switching process 56 is shown.Interface switching process 56 is performed byinterface switching code 44 to switch from primaryphysical interface 26ato secondaryphysical interface 26b.Process 56 monitors58 primaryphysical interface 26a, including bothdriver 30aand signaling stack46a, for specific “events”. These events can include, but are not limited to, receipt of a slot reset at primaryphysical interface 26aand/or a failure of primaryphysical interface 26a, such as a failure ofdriver 30aand/or signalingstack 46a. - In response to detecting60 one of the foregoing events,
process 56switches 62 from primaryphysical interface 26ato secondaryphysical interface 26b(in accordance with interface redundancy group information48).Switching 62 is performed by enablingdriver 30bfor secondaryphysical interface 26b. Following switching,secondary interface 26bestablishes63 the network layer interfaces to network24 (in this example,ELANs 52ato52h), and assumes the responsibilities (including routing and bridging services) ofprimary interface 26b. Switching between interfaces is performed as quickly as possible, e.g., within thirty seconds of failure or reset. - With
driver 30benabled, in64, signalingstack 46btransmits cells over secondaryphysical interface 26bto ELANs52ato52h. Primaryphysical interface 26acan be repaired while secondaryphysical interface 26bperforms its functions. - Active Mode
- In active mode, prior to switching, the secondary
physical interface 26bis already communicating over the network. Following failure of the primaryphysical interface 26a, thesecondary interface 26bassumes the responsibilities of theprimary interface 26a. In particular, upon switching, code in the signaling stack establishes the network layer interfaces (e.g., over ELANs) of theprimary interface 26a, and assumes the routing and bridging functions of theprimary interface 26a. - Referring to
FIG. 4 , a graphical representation of active mode is shown. InFIG. 4 ,physical interface 26ais the primary interface andphysical interface 26bis the secondary interface in active mode. This configuration is set in interfaceredundancy group information 48. Since secondaryphysical interface 26bis in active mode, prior to switching, it is providing network layer services over virtual circuits forELANs 52eto52h. Primaryphysical interface 26ais supporting ELANs52ato52d. - Referring to
FIG. 5 , aninterface switching process 66 is shown, that is performed byinterface switching code 44 to switch from primaryphysical interface 26ato secondaryphysical interface 26b.Interface switching process 66 monitors68 primaryphysical interface 26a, including bothdriver 30aand signaling stack46a, for specific events. These events are the same as those noted above for passive mode. - In response to detecting70 one of the foregoing events,
process 66switches 72 from primaryphysical interface 26ato secondaryphysical interface 26b. Switching is performed in the manner described above; that is, enabling and disabling the drivers for the appropriate network interfaces. Interface switching process 66 establishes74, over secondaryphysical interface 26b, the network layer interfaces (in this case,ELANs 52ato52d) of primaryphysical interface 26a. Secondaryphysical interface 26bcontinues to perform its original routing and bridging functions over ELANs52eto52h. Now, however, secondaryphysical interface 26balso performs the routing and bridging functions formerly performed by primaryphysical interface 26aover ELANs52ato52d.- With
driver 30benabled, and secondaryphysical interface 26bswitched, in76, signalingstack 46btransmits cells over secondaryphysical interface 26bto all of ELANs52ato52h. This is shown inFIG. 6 . Primaryphysical interface 26ano longer transmits (hence no lines are shown between this interface and the ELANs inFIG. 6 ). - Switching Based on Priority
- ATM physical interfaces may also be assigned relative priorities and switched on that basis. An option in router.12 may be set, e.g., by a user, to trigger automatic switching based on priority. The priority information upon which switching is based may be included in interface
redundancy group information 48, for example. - Referring to
FIG. 7 , aprocess 78 is shown that is performed byinterface switching code 44 to switch interfaces based on priority.Process 78 designates80 any number of physical interfaces on a sliding priority scale, from highest priority to lowest priority. In router12 (FIG. 2 ), only two physical interfaces are shown. For the sake of illustration, therefore,physical interface 26ais designated80 as high priority andphysical interface 26bis designated80 as low priority. - Once
physical interfaces Process 78 monitors82 high priorityphysical interface 26ato determine if it is up and running. If high priorityphysical interface 26ais available84 (i.e., it is not “down”),process 78switches 86 from low priorityphysical interface 26bto high priorityphysical interface 26a. As a result, the “best available” interface onrouter 12 is used to provide network layer connections overnetwork 24.Process 60 may be incorporated intoprocesses - As noted above, the invention may be used on routers having more than two physical interfaces. For example, in
FIG. 8 ,router 90 has threephysical interfaces interface redundancy groups Interfaces group 94 andinterfaces group 96. In this example,interface 92cis a backup forinterfaces interfaces interfaces - Switching in the case of more than two interfaces is performed in the same way as described in
processes - The invention is not limited to the specific hardware and software configurations described herein. For example, the invention can be used outside the context of ATM WANs, and with network devices other than routers. In this regard, it is to be understood that while the invention has been described in conjunction with the detailed description thereof, the foregoing description is intended to illustrate, and not to limit, the scope of the invention. Other aspects, advantages, and modifications are within the scope of the following claims.
Claims (19)
1-94. (canceled)
95. A method of switching between physical interfaces on a device, the method comprising the steps of:
detecting an event at a first physical interface on the device;
switching, in response to the event, from the first physical interface to a second physical interface on the device based on information in an interface redundancy group;
wherein the information in the interface redundancy group identifies the first physical interface as a primary interface for the device and the second physical interface as a secondary interface for the device.
96. The method ofclaim 95 , wherein the event comprises a failure of the first physical interface.
97. The method ofclaim 96 , wherein the first physical interface is associated with a driver and a signaling stack, and the failure of the first physical interface comprises a failure of one of the driver or the signaling stack.
98. The method ofclaim 97 , further comprising monitoring the driver and the signaling stack in order to detect a failure of one of the driver or the signaling stack.
99. The method ofclaim 95 , wherein the event comprises receipt of a slot failure at the first physical interface.
100. The method ofclaim 95 , wherein the first and second physical interfaces comprise asynchronous transfer mode (ATM) physical interfaces.
101. The method ofclaim 95 , further comprising the steps of:
monitoring availability of the first physical interface; and
switching from the second physical interface to the first physical interface once the first physical interface becomes available.
102. The method ofclaim 101 , wherein the switching is performed automatically in response to the first physical interface becoming available.
103. A method of preferentially switching between prioritized physical interfaces on a single device, the method comprising the steps of:
designating a first physical interface on the device as a high priority physical interface;
monitoring availability of the high priority physical interface; and
switching from a second physical interface on the device to the high priority physical interface once the high priority physical interface becomes available.
104. The method ofclaim 103 , wherein the switching is performed automatically in response to the high priority physical interface becoming available.
105. The method ofclaim 103 , further comprising the steps of:
designating a the second physical interface on the device as a moderate priority physical interface;
monitoring availability of the moderate priority physical interface; and
switching from a third physical interface on the device to either the high priority physical interface once the high priority physical interface becomes available or the moderate priority physical interface once the moderate priority physical interface becomes available.
106. The method ofclaim 103 , wherein the first and second physical interfaces comprise asynchronous transfer mode (ATM) physical interfaces.
107. The method ofclaim 103 , wherein the first physical interface is defined as the primary interface for the device.
108. An apparatus which preferentially switches between prioritized physical interfaces, the apparatus comprising:
plural physical interfaces; and
a processor which executes instructions to:
designate a first physical interface on the apparatus as a high priority physical interface;
monitor availability of the high priority physical interface; and
switch from a second physical interface on the device to the high priority physical interface once the high priority physical interface becomes available.
109. The apparatus ofclaim 108 , wherein the switch is performed automatically in response to the high priority physical interface becoming available.
110. The apparatus ofclaim 108 , wherein the processor further executes instructions to:
designate the second physical interface on the device as a moderate priority physical interface;
monitor availability of the moderate priority physical interface; and
switch from a third physical interface on the device to either the high priority physical interface once the high priority physical interface becomes available or the moderate priority physical interface once the moderate priority physical interface becomes available.
111. The apparatus ofclaim 108 , wherein the first and second physical interfaces comprise asynchronous transfer mode (ATM) physical interfaces.
112. The apparatus ofclaim 108 , wherein the first physical interface is defined as the primary interface for the device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US11/084,217US20060013248A1 (en) | 1999-08-13 | 2005-03-18 | Switching device interfaces |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US09/374,460US6906998B1 (en) | 1999-08-13 | 1999-08-13 | Switching device interfaces |
| US11/084,217US20060013248A1 (en) | 1999-08-13 | 2005-03-18 | Switching device interfaces |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US09/374,460ContinuationUS6906998B1 (en) | 1999-08-13 | 1999-08-13 | Switching device interfaces |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| US20060013248A1true US20060013248A1 (en) | 2006-01-19 |
Family
ID=34632696
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US09/374,460Expired - LifetimeUS6906998B1 (en) | 1999-08-13 | 1999-08-13 | Switching device interfaces |
| US11/084,217AbandonedUS20060013248A1 (en) | 1999-08-13 | 2005-03-18 | Switching device interfaces |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US09/374,460Expired - LifetimeUS6906998B1 (en) | 1999-08-13 | 1999-08-13 | Switching device interfaces |
Country Status (1)
| Country | Link |
|---|---|
| US (2) | US6906998B1 (en) |
Cited By (42)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050013258A1 (en)* | 2003-07-16 | 2005-01-20 | Fike John M. | Method and apparatus for detecting and removing orphaned primitives in a fibre channel network |
| US20050015518A1 (en)* | 2003-07-16 | 2005-01-20 | Wen William J. | Method and system for non-disruptive data capture in networks |
| US20050013318A1 (en)* | 2003-07-16 | 2005-01-20 | Fike John M. | Method and system for fibre channel arbitrated loop acceleration |
| US20050013609A1 (en)* | 2003-07-16 | 2005-01-20 | Fike John M. | Method and system for minimizing disruption in common-access networks |
| US20050018676A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Programmable pseudo virtual lanes for fibre channel systems |
| US20050018649A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for improving bandwidth and reducing idles in fibre channel switches |
| US20050018680A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for programmable data dependant network routing |
| US20050018701A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for routing fibre channel frames |
| US20050018673A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for using extended fabric features with fibre channel switch elements |
| US20050018672A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Lun based hard zoning in fibre channel switches |
| US20050018674A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for buffer-to-buffer credit recovery in fibre channel systems using virtual and/or pseudo virtual lanes |
| US20050018650A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for configuring fibre channel ports |
| US20050018621A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for selecting virtual lanes in fibre channel switches |
| US20050018675A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Multi-speed cut through operation in fibre channel |
| US20050018606A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for congestion control based on optimum bandwidth allocation in a fibre channel switch |
| US20050027877A1 (en)* | 2003-07-16 | 2005-02-03 | Fike Melanie A. | Method and apparatus for accelerating receive-modify-send frames in a fibre channel network |
| US20050025193A1 (en)* | 2003-07-16 | 2005-02-03 | Fike John M. | Method and apparatus for test pattern generation |
| US20050025060A1 (en)* | 2003-07-16 | 2005-02-03 | Fike John M. | Method and apparatus for testing loop pathway integrity in a fibre channel arbitrated loop |
| US20050030978A1 (en)* | 2003-07-21 | 2005-02-10 | Dropps Frank R. | Method and system for managing traffic in fibre channel systems |
| US20050030893A1 (en)* | 2003-07-21 | 2005-02-10 | Dropps Frank R. | Method and system for detecting congestion and over subscription in a fibre channel network |
| US20050044267A1 (en)* | 2003-07-21 | 2005-02-24 | Dropps Frank R. | Method and system for routing and filtering network data packets in fibre channel systems |
| US20050135251A1 (en)* | 2002-10-07 | 2005-06-23 | Kunz James A. | Method and system for reducing congestion in computer networks |
| US20050174936A1 (en)* | 2004-02-05 | 2005-08-11 | Betker Steven M. | Method and system for preventing deadlock in fibre channel fabrics using frame priorities |
| US20050174942A1 (en)* | 2004-02-05 | 2005-08-11 | Betker Steven M. | Method and system for reducing deadlock in fibre channel fabrics using virtual lanes |
| US20060020725A1 (en)* | 2004-07-20 | 2006-01-26 | Dropps Frank R | Integrated fibre channel fabric controller |
| US20060072616A1 (en)* | 2004-10-01 | 2006-04-06 | Dropps Frank R | Method and system for LUN remapping in fibre channel networks |
| US20060072473A1 (en)* | 2004-10-01 | 2006-04-06 | Dropps Frank R | High speed fibre channel switch element |
| US20060072580A1 (en)* | 2004-10-01 | 2006-04-06 | Dropps Frank R | Method and system for transferring data drectly between storage devices in a storage area network |
| US20060159081A1 (en)* | 2005-01-18 | 2006-07-20 | Dropps Frank R | Address translation in fibre channel switches |
| US20070081527A1 (en)* | 2002-07-22 | 2007-04-12 | Betker Steven M | Method and system for primary blade selection in a multi-module fibre channel switch |
| US20070201457A1 (en)* | 2002-07-22 | 2007-08-30 | Betker Steven M | Method and system for dynamically assigning domain identification in a multi-module fibre channel switch |
| US7352701B1 (en) | 2003-09-19 | 2008-04-01 | Qlogic, Corporation | Buffer to buffer credit recovery for in-line fibre channel credit extension devices |
| US7362717B1 (en) | 2002-10-03 | 2008-04-22 | Qlogic, Corporation | Method and system for using distributed name servers in multi-module fibre channel switches |
| US7397768B1 (en)* | 2002-09-11 | 2008-07-08 | Qlogic, Corporation | Zone management in a multi-module fibre channel switch |
| US7420982B2 (en) | 2003-07-21 | 2008-09-02 | Qlogic, Corporation | Method and system for keeping a fibre channel arbitrated loop open during frame gaps |
| US7477655B2 (en) | 2003-07-21 | 2009-01-13 | Qlogic, Corporation | Method and system for power control of fibre channel switches |
| US7522522B2 (en) | 2003-07-21 | 2009-04-21 | Qlogic, Corporation | Method and system for reducing latency and congestion in fibre channel switches |
| US7542676B2 (en) | 2004-04-23 | 2009-06-02 | Qlogic, Corporation | Fibre channel transparent switch for mixed switch fabrics |
| US7646767B2 (en) | 2003-07-21 | 2010-01-12 | Qlogic, Corporation | Method and system for programmable data dependant network routing |
| US7894348B2 (en) | 2003-07-21 | 2011-02-22 | Qlogic, Corporation | Method and system for congestion control in a fibre channel switch |
| US7930377B2 (en) | 2004-04-23 | 2011-04-19 | Qlogic, Corporation | Method and system for using boot servers in networks |
| US20140003358A1 (en)* | 2012-07-02 | 2014-01-02 | Brent J. Elliott | Application continuity with reroute and reset in a wireless communication network |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7502366B1 (en)* | 2000-05-23 | 2009-03-10 | Advanced Micro Devices, Inc. | Arrangement in a network switch for prioritizing data frames based on user-defined frame attributes |
| US8532127B2 (en) | 2001-10-19 | 2013-09-10 | Juniper Networks, Inc. | Network routing using indirect next hop data |
| US7184437B1 (en) | 2002-07-17 | 2007-02-27 | Juniper Networks, Inc. | Scalable route resolution |
| US7447149B1 (en)* | 2004-07-13 | 2008-11-04 | Juniper Networks, Inc. | Virtual interface with active and backup physical interfaces |
| US7583590B2 (en)* | 2005-07-15 | 2009-09-01 | Telefonaktiebolaget L M Ericsson (Publ) | Router and method for protocol process migration |
| US9049148B1 (en) | 2012-09-28 | 2015-06-02 | Juniper Networks, Inc. | Dynamic forwarding plane reconfiguration in a network device |
| US9860081B2 (en)* | 2013-06-18 | 2018-01-02 | Extreme Networks, Inc. | General user network interface (UNI) multi-homing techniques for shortest path bridging (SPB) networks |
| US10025905B2 (en) | 2013-09-03 | 2018-07-17 | Qualcomm Incorporated | Communication device resource allocation based on medical data criticality and resource status |
| DE112016007007T5 (en) | 2016-06-22 | 2019-03-07 | Intel Corporation | COMMUNICATION DEVICE AND METHOD FOR FULL DUPLEX DISPOSITION |
| US10909676B2 (en)* | 2017-07-12 | 2021-02-02 | Siemens Healthcare Gmbh | Method and system for clinical decision support with local and remote analytics |
Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5436893A (en)* | 1992-12-05 | 1995-07-25 | Netcom Limited | ATM cell switch suitable for multicast switching |
| US5461609A (en)* | 1993-10-13 | 1995-10-24 | General Datacomm Advanced Research Centre Ltd. | Packet data network switch having internal fault detection and correction |
| US5848227A (en)* | 1992-10-13 | 1998-12-08 | International Business Machines Corporation | Method of providing fault tolerance and switch-over distribution in a bridge/router |
| US5862338A (en)* | 1996-12-30 | 1999-01-19 | Compaq Computer Corporation | Polling system that determines the status of network ports and that stores values indicative thereof |
| US5889778A (en)* | 1995-07-17 | 1999-03-30 | Pmc-Sierra Ltd. | ATM layer device |
| US5903544A (en)* | 1996-04-05 | 1999-05-11 | Hitachi, Ltd. | Packet handler |
| US6072806A (en)* | 1997-05-02 | 2000-06-06 | Aspect Telecommunications Corporation | Message-based communication system |
| US6075767A (en)* | 1996-03-19 | 2000-06-13 | Hitachi, Ltd. | Asynchronous transmission mode (ATM) handler |
| US6098109A (en)* | 1996-12-30 | 2000-08-01 | Compaq Computer Corporation | Programmable arbitration system for determining priority of the ports of a network switch |
| US6167025A (en)* | 1996-09-11 | 2000-12-26 | Telcordia Technologies, Inc. | Methods and apparatus for restoring connections in an ATM network |
| US6208616B1 (en)* | 1997-05-13 | 2001-03-27 | 3Com Corporation | System for detecting errors in a network |
| US6226261B1 (en)* | 1998-03-06 | 2001-05-01 | Nokia Networks Oy | Redundant switching arrangement |
| US6246665B1 (en)* | 1995-12-27 | 2001-06-12 | Fujitsu Limited | Method for attending occurrence of failure in an exchange system that exchanges cells having fixed-length, and interface unit and concentrator equipped in the exchange system using the method |
| US6269149B1 (en)* | 1996-12-30 | 2001-07-31 | Paradyne Corporation | System and method for enhancing a communication link |
| US6311288B1 (en)* | 1998-03-13 | 2001-10-30 | Paradyne Corporation | System and method for virtual circuit backup in a communication network |
| US6359858B1 (en)* | 1999-06-03 | 2002-03-19 | Fujitsu Network Communications, Inc. | Switching redundancy control |
| US6392990B1 (en)* | 1999-07-23 | 2002-05-21 | Glenayre Electronics, Inc. | Method for implementing interface redundancy in a computer network |
| US6513092B1 (en)* | 2000-04-18 | 2003-01-28 | Nec Eluminant Technologies, Inc. | 1:N protection switching architecture for common processing units |
| US6542934B1 (en)* | 1997-05-30 | 2003-04-01 | International Business Machines Corporation | Non-disruptively rerouting network communications from a secondary network path to a primary path |
| US6643254B1 (en)* | 1998-08-06 | 2003-11-04 | Fujitsu Limited | Rerouting method for a PVC route on an ATM network and a network management system using the rerouting method |
- 1999
- 1999-08-13USUS09/374,460patent/US6906998B1/ennot_activeExpired - Lifetime
- 2005
- 2005-03-18USUS11/084,217patent/US20060013248A1/ennot_activeAbandoned
Patent Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5848227A (en)* | 1992-10-13 | 1998-12-08 | International Business Machines Corporation | Method of providing fault tolerance and switch-over distribution in a bridge/router |
| US5436893A (en)* | 1992-12-05 | 1995-07-25 | Netcom Limited | ATM cell switch suitable for multicast switching |
| US5461609A (en)* | 1993-10-13 | 1995-10-24 | General Datacomm Advanced Research Centre Ltd. | Packet data network switch having internal fault detection and correction |
| US5889778A (en)* | 1995-07-17 | 1999-03-30 | Pmc-Sierra Ltd. | ATM layer device |
| US6246665B1 (en)* | 1995-12-27 | 2001-06-12 | Fujitsu Limited | Method for attending occurrence of failure in an exchange system that exchanges cells having fixed-length, and interface unit and concentrator equipped in the exchange system using the method |
| US6075767A (en)* | 1996-03-19 | 2000-06-13 | Hitachi, Ltd. | Asynchronous transmission mode (ATM) handler |
| US5903544A (en)* | 1996-04-05 | 1999-05-11 | Hitachi, Ltd. | Packet handler |
| US6167025A (en)* | 1996-09-11 | 2000-12-26 | Telcordia Technologies, Inc. | Methods and apparatus for restoring connections in an ATM network |
| US5862338A (en)* | 1996-12-30 | 1999-01-19 | Compaq Computer Corporation | Polling system that determines the status of network ports and that stores values indicative thereof |
| US6098109A (en)* | 1996-12-30 | 2000-08-01 | Compaq Computer Corporation | Programmable arbitration system for determining priority of the ports of a network switch |
| US6269149B1 (en)* | 1996-12-30 | 2001-07-31 | Paradyne Corporation | System and method for enhancing a communication link |
| US6072806A (en)* | 1997-05-02 | 2000-06-06 | Aspect Telecommunications Corporation | Message-based communication system |
| US6208616B1 (en)* | 1997-05-13 | 2001-03-27 | 3Com Corporation | System for detecting errors in a network |
| US6542934B1 (en)* | 1997-05-30 | 2003-04-01 | International Business Machines Corporation | Non-disruptively rerouting network communications from a secondary network path to a primary path |
| US6226261B1 (en)* | 1998-03-06 | 2001-05-01 | Nokia Networks Oy | Redundant switching arrangement |
| US6311288B1 (en)* | 1998-03-13 | 2001-10-30 | Paradyne Corporation | System and method for virtual circuit backup in a communication network |
| US6643254B1 (en)* | 1998-08-06 | 2003-11-04 | Fujitsu Limited | Rerouting method for a PVC route on an ATM network and a network management system using the rerouting method |
| US6359858B1 (en)* | 1999-06-03 | 2002-03-19 | Fujitsu Network Communications, Inc. | Switching redundancy control |
| US6392990B1 (en)* | 1999-07-23 | 2002-05-21 | Glenayre Electronics, Inc. | Method for implementing interface redundancy in a computer network |
| US6513092B1 (en)* | 2000-04-18 | 2003-01-28 | Nec Eluminant Technologies, Inc. | 1:N protection switching architecture for common processing units |
Cited By (73)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070081527A1 (en)* | 2002-07-22 | 2007-04-12 | Betker Steven M | Method and system for primary blade selection in a multi-module fibre channel switch |
| US20070201457A1 (en)* | 2002-07-22 | 2007-08-30 | Betker Steven M | Method and system for dynamically assigning domain identification in a multi-module fibre channel switch |
| US7388861B2 (en) | 2002-07-22 | 2008-06-17 | Qlogic, Corporation | Method and system for primary blade selection in a multi-module fibre channel switch |
| US7397768B1 (en)* | 2002-09-11 | 2008-07-08 | Qlogic, Corporation | Zone management in a multi-module fibre channel switch |
| US7729288B1 (en) | 2002-09-11 | 2010-06-01 | Qlogic, Corporation | Zone management in a multi-module fibre channel switch |
| US7362717B1 (en) | 2002-10-03 | 2008-04-22 | Qlogic, Corporation | Method and system for using distributed name servers in multi-module fibre channel switches |
| US20050135251A1 (en)* | 2002-10-07 | 2005-06-23 | Kunz James A. | Method and system for reducing congestion in computer networks |
| US7620059B2 (en) | 2003-07-16 | 2009-11-17 | Qlogic, Corporation | Method and apparatus for accelerating receive-modify-send frames in a fibre channel network |
| US7355966B2 (en) | 2003-07-16 | 2008-04-08 | Qlogic, Corporation | Method and system for minimizing disruption in common-access networks |
| US7453802B2 (en) | 2003-07-16 | 2008-11-18 | Qlogic, Corporation | Method and apparatus for detecting and removing orphaned primitives in a fibre channel network |
| US7471635B2 (en) | 2003-07-16 | 2008-12-30 | Qlogic, Corporation | Method and apparatus for test pattern generation |
| US7388843B2 (en) | 2003-07-16 | 2008-06-17 | Qlogic, Corporation | Method and apparatus for testing loop pathway integrity in a fibre channel arbitrated loop |
| US7525910B2 (en) | 2003-07-16 | 2009-04-28 | Qlogic, Corporation | Method and system for non-disruptive data capture in networks |
| US20050013609A1 (en)* | 2003-07-16 | 2005-01-20 | Fike John M. | Method and system for minimizing disruption in common-access networks |
| US7463646B2 (en) | 2003-07-16 | 2008-12-09 | Qlogic Corporation | Method and system for fibre channel arbitrated loop acceleration |
| US20050027877A1 (en)* | 2003-07-16 | 2005-02-03 | Fike Melanie A. | Method and apparatus for accelerating receive-modify-send frames in a fibre channel network |
| US20050025193A1 (en)* | 2003-07-16 | 2005-02-03 | Fike John M. | Method and apparatus for test pattern generation |
| US20050025060A1 (en)* | 2003-07-16 | 2005-02-03 | Fike John M. | Method and apparatus for testing loop pathway integrity in a fibre channel arbitrated loop |
| US20050013258A1 (en)* | 2003-07-16 | 2005-01-20 | Fike John M. | Method and apparatus for detecting and removing orphaned primitives in a fibre channel network |
| US20050013318A1 (en)* | 2003-07-16 | 2005-01-20 | Fike John M. | Method and system for fibre channel arbitrated loop acceleration |
| US20050015518A1 (en)* | 2003-07-16 | 2005-01-20 | Wen William J. | Method and system for non-disruptive data capture in networks |
| US20050030978A1 (en)* | 2003-07-21 | 2005-02-10 | Dropps Frank R. | Method and system for managing traffic in fibre channel systems |
| US20050018701A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for routing fibre channel frames |
| US7894348B2 (en) | 2003-07-21 | 2011-02-22 | Qlogic, Corporation | Method and system for congestion control in a fibre channel switch |
| US7792115B2 (en) | 2003-07-21 | 2010-09-07 | Qlogic, Corporation | Method and system for routing and filtering network data packets in fibre channel systems |
| US20050018676A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Programmable pseudo virtual lanes for fibre channel systems |
| US7684401B2 (en) | 2003-07-21 | 2010-03-23 | Qlogic, Corporation | Method and system for using extended fabric features with fibre channel switch elements |
| US7646767B2 (en) | 2003-07-21 | 2010-01-12 | Qlogic, Corporation | Method and system for programmable data dependant network routing |
| US7630384B2 (en) | 2003-07-21 | 2009-12-08 | Qlogic, Corporation | Method and system for distributing credit in fibre channel systems |
| US20050044267A1 (en)* | 2003-07-21 | 2005-02-24 | Dropps Frank R. | Method and system for routing and filtering network data packets in fibre channel systems |
| US20050030893A1 (en)* | 2003-07-21 | 2005-02-10 | Dropps Frank R. | Method and system for detecting congestion and over subscription in a fibre channel network |
| US20050018649A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for improving bandwidth and reducing idles in fibre channel switches |
| US20050018606A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for congestion control based on optimum bandwidth allocation in a fibre channel switch |
| US20050018675A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Multi-speed cut through operation in fibre channel |
| US20050018621A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for selecting virtual lanes in fibre channel switches |
| US20050018650A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for configuring fibre channel ports |
| US20050018674A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for buffer-to-buffer credit recovery in fibre channel systems using virtual and/or pseudo virtual lanes |
| US7583597B2 (en) | 2003-07-21 | 2009-09-01 | Qlogic Corporation | Method and system for improving bandwidth and reducing idles in fibre channel switches |
| US7406092B2 (en) | 2003-07-21 | 2008-07-29 | Qlogic, Corporation | Programmable pseudo virtual lanes for fibre channel systems |
| US7580354B2 (en) | 2003-07-21 | 2009-08-25 | Qlogic, Corporation | Multi-speed cut through operation in fibre channel switches |
| US7420982B2 (en) | 2003-07-21 | 2008-09-02 | Qlogic, Corporation | Method and system for keeping a fibre channel arbitrated loop open during frame gaps |
| US7430175B2 (en) | 2003-07-21 | 2008-09-30 | Qlogic, Corporation | Method and system for managing traffic in fibre channel systems |
| US7447224B2 (en) | 2003-07-21 | 2008-11-04 | Qlogic, Corporation | Method and system for routing fibre channel frames |
| US20050018672A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Lun based hard zoning in fibre channel switches |
| US20050018673A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for using extended fabric features with fibre channel switch elements |
| US7466700B2 (en) | 2003-07-21 | 2008-12-16 | Qlogic, Corporation | LUN based hard zoning in fibre channel switches |
| US7573909B2 (en) | 2003-07-21 | 2009-08-11 | Qlogic, Corporation | Method and system for programmable data dependant network routing |
| US7477655B2 (en) | 2003-07-21 | 2009-01-13 | Qlogic, Corporation | Method and system for power control of fibre channel switches |
| US7558281B2 (en) | 2003-07-21 | 2009-07-07 | Qlogic, Corporation | Method and system for configuring fibre channel ports |
| US7512067B2 (en) | 2003-07-21 | 2009-03-31 | Qlogic, Corporation | Method and system for congestion control based on optimum bandwidth allocation in a fibre channel switch |
| US7525983B2 (en) | 2003-07-21 | 2009-04-28 | Qlogic, Corporation | Method and system for selecting virtual lanes in fibre channel switches |
| US7522529B2 (en) | 2003-07-21 | 2009-04-21 | Qlogic, Corporation | Method and system for detecting congestion and over subscription in a fibre channel network |
| US7522522B2 (en) | 2003-07-21 | 2009-04-21 | Qlogic, Corporation | Method and system for reducing latency and congestion in fibre channel switches |
| US20050018680A1 (en)* | 2003-07-21 | 2005-01-27 | Dropps Frank R. | Method and system for programmable data dependant network routing |
| US7352701B1 (en) | 2003-09-19 | 2008-04-01 | Qlogic, Corporation | Buffer to buffer credit recovery for in-line fibre channel credit extension devices |
| US20050174936A1 (en)* | 2004-02-05 | 2005-08-11 | Betker Steven M. | Method and system for preventing deadlock in fibre channel fabrics using frame priorities |
| US7564789B2 (en) | 2004-02-05 | 2009-07-21 | Qlogic, Corporation | Method and system for reducing deadlock in fibre channel fabrics using virtual lanes |
| US20050174942A1 (en)* | 2004-02-05 | 2005-08-11 | Betker Steven M. | Method and system for reducing deadlock in fibre channel fabrics using virtual lanes |
| US7480293B2 (en) | 2004-02-05 | 2009-01-20 | Qlogic, Corporation | Method and system for preventing deadlock in fibre channel fabrics using frame priorities |
| US7542676B2 (en) | 2004-04-23 | 2009-06-02 | Qlogic, Corporation | Fibre channel transparent switch for mixed switch fabrics |
| US7930377B2 (en) | 2004-04-23 | 2011-04-19 | Qlogic, Corporation | Method and system for using boot servers in networks |
| US7404020B2 (en) | 2004-07-20 | 2008-07-22 | Qlogic, Corporation | Integrated fibre channel fabric controller |
| US20060020725A1 (en)* | 2004-07-20 | 2006-01-26 | Dropps Frank R | Integrated fibre channel fabric controller |
| US7593997B2 (en) | 2004-10-01 | 2009-09-22 | Qlogic, Corporation | Method and system for LUN remapping in fibre channel networks |
| US20060072473A1 (en)* | 2004-10-01 | 2006-04-06 | Dropps Frank R | High speed fibre channel switch element |
| US20060072580A1 (en)* | 2004-10-01 | 2006-04-06 | Dropps Frank R | Method and system for transferring data drectly between storage devices in a storage area network |
| US20060072616A1 (en)* | 2004-10-01 | 2006-04-06 | Dropps Frank R | Method and system for LUN remapping in fibre channel networks |
| US7411958B2 (en) | 2004-10-01 | 2008-08-12 | Qlogic, Corporation | Method and system for transferring data directly between storage devices in a storage area network |
| US8295299B2 (en) | 2004-10-01 | 2012-10-23 | Qlogic, Corporation | High speed fibre channel switch element |
| US20060159081A1 (en)* | 2005-01-18 | 2006-07-20 | Dropps Frank R | Address translation in fibre channel switches |
| US7519058B2 (en) | 2005-01-18 | 2009-04-14 | Qlogic, Corporation | Address translation in fibre channel switches |
| US20140003358A1 (en)* | 2012-07-02 | 2014-01-02 | Brent J. Elliott | Application continuity with reroute and reset in a wireless communication network |
| US9160497B2 (en)* | 2012-07-02 | 2015-10-13 | Intel Corporation | Application continuity with reroute and reset in a wireless communication network |
Also Published As
| Publication number | Publication date |
|---|---|
| US6906998B1 (en) | 2005-06-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6906998B1 (en) | Switching device interfaces | |
| US5835696A (en) | Data router backup feature | |
| US6311288B1 (en) | System and method for virtual circuit backup in a communication network | |
| US7117241B2 (en) | Method and apparatus for centralized maintenance system within a distributed telecommunications architecture | |
| US6728780B1 (en) | High availability networking with warm standby interface failover | |
| EP1391079B1 (en) | Method and system for implementing a fast recovery process in a local area network | |
| US6763479B1 (en) | High availability networking with alternate pathing failover | |
| US6011910A (en) | Supporting authentication across multiple network access servers | |
| US8233383B2 (en) | Network relay system and control method thereof | |
| US20040165525A1 (en) | System and method for network redundancy | |
| US6885633B1 (en) | Network node and a system | |
| US6105151A (en) | System for detecting network errors | |
| US20020016874A1 (en) | Circuit multiplexing method and information relaying apparatus | |
| JPH10326261A (en) | System for reporting errors by hardware elements of a distributed computer system | |
| EP1471698A2 (en) | Network fabric access device with multiple system side interfaces | |
| US6026085A (en) | Architecture to support a single system image across multiple network access servers | |
| JPH10326260A (en) | Error reporting method using hardware element of decentralized computer system | |
| US6580688B1 (en) | Switching transmission units to an equivalent circuit for the purposes of bidirectional asynchronous cell transfer | |
| JP3811007B2 (en) | Virtual connection protection switching | |
| KR20060042394A (en) | Subscriber Unit Redundancy System and Subscriber Unit Redundancy Method | |
| US6233232B1 (en) | Supporting multilink connections across multiple network access servers | |
| US20160205046A1 (en) | Transmission device and interface device | |
| US6396808B1 (en) | ATM switching network and ATM switching system in which the transfer of inputted cells is controlled by control cells, and signal processing method in ATM switching network | |
| US6498779B1 (en) | Multiple endpoint paths | |
| Cisco | exit- |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AS | Assignment | Owner name:AVAYA HOLDINGS LIMITED,NEW JERSEY Free format text:ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:023998/0799 Effective date:20091218 Owner name:AVAYA HOLDINGS LIMITED, NEW JERSEY Free format text:ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:023998/0799 Effective date:20091218 | |
| STCB | Information on status: application discontinuation | Free format text:ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |