WO2011072536A1 - 一种VxWorks系统下的多网卡双冗余装置及系统 - Google Patents

一种VxWorks系统下的多网卡双冗余装置及系统 Download PDF

Info

Publication number
WO2011072536A1
WO2011072536A1 PCT/CN2010/076292 CN2010076292W WO2011072536A1 WO 2011072536 A1 WO2011072536 A1 WO 2011072536A1 CN 2010076292 W CN2010076292 W CN 2010076292W WO 2011072536 A1 WO2011072536 A1 WO 2011072536A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
network card
connection state
link connection
virtual network
Prior art date
Application number
PCT/CN2010/076292
Other languages
English (en)
French (fr)
Inventor
李守轩
孔德深
柴先平
Original Assignee
研祥智能科技股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 研祥智能科技股份有限公司 filed Critical 研祥智能科技股份有限公司
Publication of WO2011072536A1 publication Critical patent/WO2011072536A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability

Definitions

  • the invention belongs to the field of computer networks, and in particular relates to a multi-network card dual redundant device and system under the VxWorks system.
  • Ethernet With the maturity of network technology, Ethernet with the advantages of low price and convenient connection has become the main medium for interface interconnection of various control systems. As a general-purpose network data communication system, it has been widely used in the field of computer networks worldwide. At the same time, with the gradual improvement of Ethernet stability, anti-interference and bandwidth issues, Ethernet is entering the industrial control field on a large scale.
  • the network used in industrial process control, communication, spacecraft and navigation systems not only requires fast information transmission, but also has strong anti-interference ability. It also requires high stability and high reliability of the network. When the network is partially damaged or damaged, The system will not expire.
  • Dual redundant design has been widely used as an effective method to improve system reliability.
  • each node uses two network interfaces, and two network interfaces are interconnected by two hubs or switches, when a normal communication network card or line
  • the node can automatically switch to the backup NIC for communication.
  • VxWorks operating system is an embedded real-time operating system designed and developed by WindRiver in the United States in 1983 (Real Time Operation System, RTOS), a key component of the embedded development environment, with good continuous development capability, high performance core, high reliability and excellent real-time performance, is widely used in communication, military, aviation, aerospace and other sophisticated In areas where technology and real-time requirements are extremely high.
  • RTOS Real Time Operation System
  • VxWorks operating system supports multiple network cards, but non-double redundant design, each network card has independent physical address and IP The address is used in a separate form for use by the system.
  • the dual redundancy design is implemented in the application layer.
  • the main method is to initiate a task in the program, and continuously judge the working state of the current working network card in a query manner. When it is determined that the currently used network card is in an abnormal state, the current deletion will be deleted.
  • the route of the NIC deletes the current host name in the host list, and unbinds the NIC from the protocol. Then configures the backup NIC to set the subnet mask and IP address for the backup NIC binding protocol.
  • the dual redundancy design is implemented in the driver layer.
  • the main method is to exchange the default network card and the backup network card handle according to the link connection status of the network card in the underlying driver of the network card to implement dual redundant switching. In the software, the underlying network card needs to be modified.
  • the driver code is more complex to implement, and the compatibility and portability are poor.
  • the method for implementing the dual redundant network card in the application layer is relatively simple and easy to implement, but the switching speed of the network card is slow, which is not conducive to the reliability and real-time performance of the network.
  • the dual-redundancy design is faster, but the underlying driver of the network card needs to be modified more, the implementation is more complicated, and the compatibility and portability are poor.
  • An object of an embodiment of the present invention is to provide a VxWorks
  • the multi-network card dual redundant device under the system makes the double-redundancy design of multiple network cards easy to implement, has fast switching speed, and has good compatibility and portability.
  • the embodiment of the present invention is implemented as a multi-network card dual redundant device in the VxWorks system, and the device includes:
  • Virtual network card configured on MUX Between the layer and the NIC driver layer, it is used to manage two mutually redundant physical NICs, and the physical NIC handles with good link connections are transmitted to the NIC driver layer, and the physical NICs with good link connections are used to send and receive data;
  • a link monitoring unit configured to monitor a link connection status of the physical network card, and output a link switching notification when the link switching condition is met;
  • a link switching unit configured to switch, according to the link switching notification, a physical network card with a link connection failure to a physical network card with a good link connection
  • the virtual network card and the two mutually redundant physical network cards managed by the virtual network card present the same MAC address and IP address.
  • Another object of the embodiments of the present invention is to provide a network data communication system, where the system includes:
  • the layer and the NIC driver layer are respectively used to manage two mutually redundant physical NICs, and the physical NIC handles with good link connections are transmitted to the NIC driver layer, and the physical NICs with good link connections are used to send and receive data;
  • a plurality of link monitoring units corresponding to each virtual network card configured to monitor a link connection state of the physical network card managed by the corresponding virtual network card, and output a link switching notification when the link switching condition is met;
  • a plurality of link switching units corresponding to each virtual network card configured to switch, according to the link switching notification, a physical network card that is connected to the link that is managed by the corresponding virtual network card to a physical network card that has a good link connection;
  • Each of the virtual network cards and the two mutually redundant physical network cards managed by the virtual network card present the same MAC address and IP address.
  • a virtual network card is configured between the layer and the network card driver layer, and two physical network cards are managed by the virtual network card to realize a dual-redundancy architecture of multiple network cards, and a dual-redundancy mechanism of multiple network cards is realized, and the design is easy to implement and the switching speed is fast; further , Can solve single IP
  • the address problem can ensure that the underlying driver is changed as little as possible, ensuring the versatility of the virtual network card and the independence of each module, compatibility and portability is better; supporting multiple types of architecture and network card, It can meet the requirements of different systems for dual redundancy.
  • Figure 1 is a hierarchical diagram of the SENS protocol stack under the VxWorks system
  • FIG. 2 is a topological structural diagram of a dual network redundancy architecture of a multiple network card according to an embodiment of the present invention
  • FIG. 3 is a structural diagram of a dual network redundant device provided by an embodiment of the present invention.
  • FIG. 4 is a structural diagram of a virtual network card according to an embodiment of the present invention.
  • FIG. 5 is a structural diagram of a link connection state machine according to an embodiment of the present invention.
  • FIG. 6 is a structural diagram of a link monitoring unit according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of implementing link connection state monitoring conversion according to an embodiment of the present invention.
  • FIG. 8 is a structural diagram of a link connection state transition module according to an embodiment of the present invention.
  • FIG. 9 is a flowchart of implementing link switching according to an embodiment of the present invention.
  • a virtual network card is configured between the MUX layer and the network card driver layer in the VxWorks system, and two physical network cards are managed by using the virtual network card to implement a dual-redundancy architecture of multiple network cards, and a dual network redundancy mechanism is implemented.
  • the network protocol stack in the VxWorks system is called the scalable enhanced network protocol stack (Scalable Enhanced).
  • SENS Scalable Enhanced
  • Network Stack, SENS the SENS protocol stack hierarchy is shown in Figure 1.
  • the basic characteristics of SENS are similar to the traditional TCP/IP network protocol stack, but it can be seen from Figure 1 that the biggest feature of SENS is that there is more MUX layer between the data link layer and the network protocol layer.
  • the driver for the network interface is called an enhanced network driver (Enhanced Network Driver, END), which is at the data link layer.
  • END enhanced Network Driver
  • the TCP/IP layer and the UDP layer are collectively referred to as the network protocol layer.
  • API Application Programming Interface
  • VxWorks systems typically use the TCP/IP protocol (which also supports other protocols), typically Ethernet (Ethernet) at the data link layer, and other physical media for data transmission, such as long-distance connections.
  • Serial line access methods such as PPP.
  • the network interface driver uses the MUX to communicate with the network protocol layer.
  • the main purpose of applying the MUX is to separate the network interface driver from the protocol layer, thus making the network interface driver and protocol layers substantially independent of each other. This independence allows a new protocol or network interface driver to be loaded, and all existing MUX-based protocols can use this new network interface driver. Similarly, if a new MUX-based protocol is to be added, existing network interface drivers can also use the MUX to communicate with the new protocol.
  • a virtual network card is configured between the MUX layer and the network card driver layer, and two physical network cards are managed by using the virtual network card, thereby forming a topology structure of the multiple network card dual redundant architecture, as shown in FIG. 2 .
  • FIG. 3 shows the structure of a multi-network card dual redundant device according to an embodiment of the present invention. For convenience of description, only parts related to the embodiment of the present invention are shown.
  • the virtual network card 31 is disposed between the MUX layer and the network card driver layer, and is configured to manage two mutually redundant physical network cards, including a MUX layer interface 311 and a network card driver layer interface 312.
  • the virtual network card 31 and the two mutually redundant physical network cards managed by the virtual network card 31 externally present the same medium access control (Media Access Control, MAC) address and IP address.
  • Media Access Control Media Access Control
  • the MUX layer interface 311 is used for data transfer between the MUX layer and the virtual network card 31.
  • the NIC driver layer interface 312 is used for the delivery of the NIC handle of the virtual NIC 31 and the physical NIC driver layer it manages.
  • the link monitoring unit 32 is configured to monitor the link connection status of the physical network card, and output a link switching notification when the link switching condition is met.
  • the link switching unit 33 switches the physical network card with the link connection failure to the physical network card with good link connection according to the link switching notification output by the link monitoring unit 32, thereby ensuring the stability and reliability of the network.
  • the structure of the dual redundant device provided by the embodiment of the present invention can solve the problem of a single IP address, and can ensure that the underlying driver is changed as little as possible, and the versatility of the virtual network card and the independence of each module are ensured and compatible. Sex and portability is better.
  • the MUX layer interface 311 is static, and the network card driver layer interface 312 is static except that the parameters passed to each other are dynamically changed.
  • the link monitoring unit 32 and the link switching unit 33 are dynamic.
  • the link monitoring unit 32 starts a timer in the process of implementing link monitoring, and detects the link connection status of the network every time. If the link connection status is abnormal, the link switching unit 33 is notified to implement the physical network card. Switch.
  • the switching of the physical network card causes the exchange of the network card handles transmitted between the two physical network card interfaces, and finally realizes the function of network redundancy, thereby ensuring the stability and reliability of the network.
  • the configuration of the virtual network card 31 is mainly the configuration of the two interfaces of the MUX layer interface 311 and the network card driver layer interface 312.
  • the virtual network card 31 is not only used for data transmission between the TCP/IP network protocol stack and the network card data link layer, but also has the characteristics of the physical network card, and has actual network nodes, MAC addresses, and IP addresses.
  • the specific design structure of the virtual network card 31 is shown in FIG. 4. As can be seen from FIG. 4, the virtual network card 31 has its own function list, which is as follows:
  • NET_FUNCS is the structure type of the NIC driver function list.
  • the design of the virtual network card 31 is transformed into the design of a specific function in the function list.
  • the virtual network card 31 provides a list of functions when the driver is loaded, the function list of the virtual network card 31 is loaded by the VnetEndLoad function, the identification handle of the virtual network card 31 is returned to the MUX layer, and the data is provided from the MUX layer to the TCP/IP network protocol stack. deal with.
  • the other functions are the driving functions of the underlying physical network card, and different types of physical network cards have their own underlying driving functions.
  • the selection of the driving function of the specific physical network card is determined by the link monitoring unit 32 and the link switching unit 33.
  • the link connection fails, the virtual network card 31 switches the corresponding physical network card handle, and transmits the physical network card handle with good link connection. Go to the NIC driver layer and send and receive data using a physical NIC with a good link.
  • each virtual network card manages two mutually redundant physical network cards. Do not interfere with each other, each virtual network card and its two mutually redundant physical network cards present a single MAC address and a single IP address, but each virtual network card implementation takes the function list of the virtual network card in Figure 4, in the system Use different device numbers to distinguish between different virtual network cards when registering.
  • the link connection state in the monitoring process of the link connection state, is divided into four states: a link good state LINK_UP, a link good to a faulty transition state LINK_FAIL, and a link failure to a good state.
  • LINK_UP and LINK_DOWN are two stable states, and LINK_FAIL and LINK_BACK are two transition states. That is, when the line state is switched between the link good state LINK_UP and the link failure state LINK_DOWN, the link connection state is stable within a certain period of time. After the conversion can be performed, the time condition must be met in order to convert the link connection state.
  • the link monitoring unit 32 includes a timing loop monitoring module 321 and a link connection state transition module 322.
  • the timing loop monitoring module 321 periodically monitors and reads the physical layer (Physical).
  • the Layer, PHY) status register cyclically monitors the link connection status of the physical network card, and the link connection status conversion module 322 switches the current link connection status to the corresponding status according to the current link connection status monitored by the timing loop monitoring module 321 .
  • the call link switching unit 33 performs link switching.
  • the timing loop monitoring module 321 periodically monitors and reads the PHY status register. If the link connection state is detected as UP, the link connection state transition module 322 connects the link connection state. Staying in the link good state LINK_UP, if the link connection state is fault DOWN, the link connection state transition module 322 converts the link connection state to the link state of the link good to failure LINK_FAIL; the timing loop monitoring module 321 then de-times Monitoring the read PHY status register, if the link is detected to be UP, the link connection state transition module 322 will link the link to a good state to the fault transition to the link good state LINK_UP, and if the link fault DOWN is detected, the link The connection state transition module 322 determines whether the link failure delay downDelay[N] has met the condition.
  • the link failure delay downDelay[N] is decremented by one, and the link connection state stays in the transition from good link to failure.
  • the status LINK_FAIL waits for the next monitoring of the timing loop monitoring module 321; if the fault delay downDelay[N] is 0, the link connection state transition module 32 2 The link connection state is changed to the link failure state LINK_DOWN. At this time, the link switching unit 33 is called to implement the link switching.
  • the timing loop monitoring module 321 periodically monitors and reads the PHY status register. If the link fault DOWN is detected, the link connection state transition module 322 stops the link connection state in the chain. If the link failure time downTime[N] is equal to 0, the link switching unit 33 is invoked to perform link switching, and if the condition is not met, the link failure time LINK_DOWN determines whether the link failure time downTime[N] satisfies the condition.
  • the link failure time downTime[N] is decremented by 1; if the timing cycle monitoring module 321 detects that the link is good UP, the link connection state transition module 322 converts the link connection state to a link failure to a good transition state LINK_BACK The timing loop monitoring module 321 then periodically monitors and reads the PHY status register. If the link fails, the link connection state transition module 322 fails the link connection state to a good transition to the link fault state LINK_DOWN, and the link is faulty. The time downTime[N] is reset; if the timing loop monitoring module 321 detects that the link is good UP, the link connection state transition module 322 determines that the link is good. Whether the lateupDelay[N] has met the condition.
  • the link good delay upDelay[N] is decremented by 1, and the link connection state is stuck in the link failure to a good transition state LINK_BACK, waiting for the timing loop monitoring module 321 Next monitoring; if the link good delay upDelay[N] is 0, the link connection status is transferred to the link good state LINK_UP.
  • Fig. 8 shows the structure of the link connection state transition module, and for convenience of explanation, only the portions related to the embodiment of the present invention are shown.
  • the link connection state machine 3221 records the change in the link connection state.
  • the link switching condition configuration module 3222 configures conditions for link switching, such as link failure delay downDelay[N], link failure time downTime[N], link good delay upDelay[N], and the like.
  • the link transition control module 3223 controls the link connection state transition according to the link connection state of the physical network card monitored by the timing loop monitoring module 321 and the link connection state recorded by the link connection state machine 3221, when the link switching condition is satisfied. At this time, a link switching notification is issued, and the link switching unit 33 is called to perform link switching.
  • each virtual network card has its own link monitoring unit to monitor the link connection status of the two physical network cards it manages, without affecting each other, and N in FIG.
  • the link switching unit 33 mainly implements the exchange between the handle of the current physical network card and the handle of the standby physical network card. The specific process is shown in FIG. 9 and is described in detail as follows:
  • step S901 it is determined whether there is a notification of link switching, if yes, step S902 is performed, otherwise step S901 is continued;
  • step S902 acquiring states of two links
  • step S903 it is determined whether both links are faulty, if yes, go back to step S901, otherwise go to step S904;
  • step S904 the handles of the current network card and the backup network card are exchanged
  • step S905 the faulty network card is set to the standby state.
  • the link switching unit 33 is in a cyclic mode waiting for the handover notification signal. If the link switching notification signal is acquired, the connection state of the two links is acquired; if the connection states of the two links are both faulty, Then, the handover is not performed. Otherwise, the network card handle of the path with good link connection status is obtained, the exchange of the two link network card handles is realized, and finally the link in the fault state is in the standby state.
  • each virtual network card has its own switching notification signal, and the implemented switching only occurs between the two physical network cards managed by each other. If there are N virtual network cards in the system, Then, N switching tasks are started to implement dual redundancy switching between two physical network cards managed by each virtual network card.
  • the implementation of the single IP and MAC address is to ensure that the virtual network card and the two mutually redundant physical network cards managed by the virtual network card have the same IP and MAC addresses, and present single IP and MAC address characteristics to the upper layer application and the user.
  • the implementation of the single IP address is implemented by the virtual network card 31.
  • each virtual network card When configuring the IP address, each virtual network card is configured with its own IP address and registered into the network protocol stack. The data can be transmitted to the virtual network card through the IP address during transmission.
  • the virtual NIC is managed on two physical NICs.
  • the single MAC address is implemented by obtaining the MAC address of one of the physical network cards, and then setting the same MAC address to another physical network card and the virtual network card. This implementation can guarantee a single MAC address for the customer.
  • Each virtual network card and its two mutually redundant physical network cards present the same IP and MAC address characteristics for the customer. If there are N virtual network cards in the system, each virtual network card and two physical network cards managed by the virtual network card They all have their own IP and MAC addresses, which are independent of each other and do not affect each other.
  • compatibility includes extended compatibility of a virtual network card and compatibility between a redundant network card and a non-redundant network card.
  • a global description table is used to maintain the extension of multiple virtual network cards.
  • the example structure of the global description table member is as follows:
  • vUnit is the serial number of the virtual network card in the global description table
  • rUnitNum1 is the first physical network card identifier managed by the virtual network card
  • rUnitNum2 is the second physical network card identifier managed by the virtual network card
  • mac_data[6] is the MAC address
  • pIpAddr is the IP address of the virtual network card
  • pGateWay is the gateway of the virtual network card.
  • VNET_NUM is the number of virtual network cards, and N is equal to VNET_NUM-1.
  • modifying the global description table can meet the different requirements of different systems for dual redundancy.
  • two physical NICs that belong to different virtual NICs are configured to be mutually redundant, or by adding or deleting virtual The number of NICs, adjust the number of redundant physical NICs.
  • Non-redundancy requirements to the transition of redundancy requirements by eliminating the virtual network card and the identity of the two physical NICs managed by it, the transition from the redundancy requirements of the two physical NICs to the non-redundancy requirements can be realized, which greatly improves the compatibility of the system. Sex.
  • the network card there may be a network card that requires a redundancy function and a network card that does not have a redundancy function.
  • the network card identifiers other than the NET_END_TBL table are required to have no redundancy function.
  • the NIC processing requires separate configuration of their respective IP addresses.
  • a virtual network card is configured between the MUX layer and the network card driver layer of the VxWorks system, and two physical network cards are managed by using the virtual network card to implement a dual-redundancy architecture of multiple network cards, and a dual network redundancy mechanism is implemented, and multiple supports are supported.
  • the type of architecture and network card can meet the requirements of different systems for dual redundancy.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

本发明适用于计算机网络领域，提供了一种VxWorks系统下的多网卡双冗余装置及系统，所述装置包括：虚拟网卡，配置于MUX层与网卡驱动层之间，用于管理两个互为冗余的物理网卡，将链路连接良好的物理网卡句柄传递到网卡驱动层，使用链路连接良好的物理网卡收发数据；链路监测单元，用于对物理网卡的链路连接状态进行监测，在链路切换条件满足时，输出链路切换通知；以及链路切换单元，用于根据所述链路切换通知，将链路连接故障的物理网卡切换到链路连接良好的物理网卡；所述虚拟网卡与其管理的两个互为冗余的物理网卡对外呈现相同的MAC地址和IP地址。本发明支持多种类型的体系结构及网卡，可以满足不同系统对双冗余功能的要求。

Description

一种VxWorks系统下的多网卡双冗余装置及系统 技术领域
本发明属于计算机网络领域，尤其涉及一种VxWorks系统下的多网卡双冗余装置及系统。
背景技术
随着网络技术的成熟，具有价格低廉、连接方便等优点的以太网已成为各种控制系统接口互连的主要媒介。它作为一种通用网络数据通信系统，在全球计算机网络领域已经得到了广泛的应用。同时，随着以太网的稳定性、抗干扰性和带宽问题的逐步改善，以太网正在大规模进入工业控制领域。用于工业过程控制、通信、航天器和导航系统中的网络不但要求信息传输速度快，抗干扰能力强，还要求网络具有高稳定性和高可靠性，在网络局部故障或受损时，全系统不至于瘫痪失效。
双冗余设计作为一种提高系统可靠性的有效方法，已经得到了广泛的应用。对于网络系统中的单个节点，常常需要对网卡进行双冗余备份，即每个节点都采用两个网络接口，两个网络接口间用两个集线器或交换机互连，当正常通信的网卡或线路出现故障时该节点能自动地切换到备份网卡进行通信。
VxWorks操作系统是美国WindRiver公司于1983年设计开发的一种嵌入式实时操作系统（Real Time Operation System，RTOS），是嵌入式开发环境的关键组成部分，具有良好的持续发展能力、高性能的内核、高可靠性和卓越的实时性，被广泛应用在通信、军事、航空、航天等精尖技术及实时性要求极高的领域中。VxWorks操作系统支持多网卡，但非双冗余设计，每块网卡都有独立的物理地址和IP 地址，以独立的形式供应用系统使用。
理论上讲，双冗余网卡技术可以在开放系统互连参考模型（Open System Interconnection Reference Model，OSI）各层中实现，而且越在底层实现，检测和切换的速度越快，效果越好。
在应用层中实现双冗余设计，主要方法是在程序中发起任务，以查询的方式不断对当前工作网卡的工作状态进行判断，当判断出当前使用的网卡处于非正常状态时，将删除当前网卡的路由，在主机列表中删除当前主机名，并解除网卡与协议的绑定，然后进行备份网卡的配置，为备份网卡绑定协议，设置子网掩码和IP地址。在驱动层中实现双冗余设计，主要方法是在网卡的底层驱动中根据网卡的链路连接状态来交换默认网卡及备份网卡的句柄来实现双冗余切换，在软件上需要修改网卡底层的驱动代码，实现比较复杂，兼容性及可移植性较差。
因此，在应用层中实现双冗余网卡的方法比较简单，容易实现，但网卡的切换速度较慢，不利于网络的可靠性和实时性。在驱动层中实现双冗余设计切换速度较快，但需要对网卡的底层驱动修改较多，实现比较复杂，兼容性及可移植性较差。
发明内容
本发明实施例的目的在于提供一种 VxWorks 系统下的多网卡双冗余装置，使得多网卡双冗余设计容易实现，切换速度快，具有良好的兼容性及可移植性。
本发明实施例是这样实现的，一种 VxWorks 系统下的多网卡双冗余装置，所述装置包括：
虚拟网卡，配置于 MUX 层与网卡驱动层之间，用于管理两个互为冗余的物理网卡，将链路连接良好的物理网卡句柄传递到网卡驱动层，使用链路连接良好的物理网卡收发数据；
链路监测单元，用于对物理网卡的链路连接状态进行监测，在链路切换条件满足时，输出链路切换通知；以及
链路切换单元，用于根据所述链路切换通知，将链路连接故障的物理网卡切换到链路连接良好的物理网卡；
所述虚拟网卡与其管理的两个互为冗余的物理网卡对外呈现相同的 MAC 地址和 IP 地址 。
本发明实施例的另一目的在于提供一种网络数据通信系统，所述系统包括：
多个虚拟网卡，配置于 MUX 层与网卡驱动层之间，分别用于管理两个互为冗余的物理网卡，将链路连接良好的物理网卡句柄传递到网卡驱动层，使用链路连接良好的物理网卡收发数据；
多个与每个虚拟网卡对应的链路监测单元，用于对相应虚拟网卡所管理的物理网卡的链路连接状态进行监测，在链路切换条件满足时，输出链路切换通知；以及
多个与每个虚拟网卡对应的链路切换单元，用于根据所述链路切换通知，将相应虚拟网卡所管理的链路连接故障的物理网卡切换到链路连接良好的物理网卡；
所述每个虚拟网卡与其管理的两个互为冗余的物理网卡对外呈现相同的 MAC 地址和 IP 地址 。
本发明实施例在 VxWorks 系统的 MUX 层与网卡驱动层之间配置一个虚拟网卡，利用虚拟网卡管理两个物理网卡，实现多网卡双冗余架构，并实现了多网卡双冗余机制，其 设计容易实现，切换速度快；进一步地， 既能解决单 IP 地址的问题，又能保证对底层驱动程序尽可能少地更改，保证了虚拟网卡的通用性与各个模块的独立性，兼容性及可移植性更好；支持多种类型的体系结构及网卡，可以满足不同系统对双冗余功能的要求。
附图说明
下面将结合附图及实施例对本发明作进一步说明，附图中：
图1是VxWorks系统下的SENS协议栈层次图；
图2是本发明实施例提供的多网卡双冗余架构的拓扑结构图；
图3是本发明实施例提供的多网卡双冗余装置的结构图；
图4是本发明实施例提供的虚拟网卡的设计结构图；
图5是本发明实施例提供的链路连接状态机的结构图；
图6是本发明实施例提供的链路监测单元的结构图；
图7是本发明实施例提供的链路连接状态监测转换实现流程图；
图8是本发明实施例提供的链路连接状态转换模块的结构图；
图9是本发明实施例提供的链路切换实现流程图。
具体实施方式
为了使本发明的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本发明进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
本发明实施例在VxWorks系统下的MUX层与网卡驱动层之间配置一个虚拟网卡，利用虚拟网卡管理两个物理网卡，实现多网卡双冗余架构，并实现多网卡双冗余机制。
VxWorks系统中的网络协议栈称为可裁减增强型网络协议栈（Scalable Enhanced Network Stack，SENS），SENS协议栈层次如图1所示。SENS的基本特征和传统的TCP/IP网络协议栈相似，但从图1中可以看出SENS最大的特点是在数据链路层和网络协议层之间多了MUX层。在SENS中，网络接口的驱动程序称为增强型网络驱动程序（Enhanced Network Driver，END），它处于数据链路层。TCP/IP层和UDP层合称为网络协议层。在数据链路层和网络协议层之间有应用程序接口（API），这个接口在SENS中称为MUX（Multiplexer）接口。
在网络协议层，VxWorks系统典型地使用TCP/IP协议（也支持其它协议），在数据链路层典型地使用以太网（Ethernet），也支持其它数据传输的物理媒体，例如远距离连接使用的串行线路接入方式，如PPP等。但是，无论使用什么物理媒体，网络接口驱动都要用到MUX与网络协议层通信。
应用MUX的主要目的是将网络接口驱动和协议层分开，这样就使得网络接口驱动和协议层彼此基本上保持独立。这种独立性使得加载一个新的协议或网络接口驱动，所有现有的基于MUX的协议就都可以用这个新的网络接口驱动程序。同样，如果要加一个新的基于MUX的协议，现有的网络接口驱动也能够用MUX来与新协议通信。
本发明实施例在MUX层与网卡驱动层之间配置一个虚拟网卡，利用虚拟网卡管理两个物理网卡，这样就形成了多网卡双冗余架构的拓扑结构，如图2所示。
图3示出了本发明实施例提供的多网卡双冗余装置的结构，为了便于说明，仅示出了与本发明实施例相关的部分。
虚拟网卡31配置在MUX层与网卡驱动层之间，用于管理两个互为冗余的物理网卡，包括MUX层接口311和网卡驱动层接口312。
在本发明实施例中，虚拟网卡31与其管理的两个互为冗余的物理网卡对外呈现相同的介质访问控制（Media Access Control，MAC）地址和IP地址。
MUX层接口311用于MUX层及虚拟网卡31之间的数据传递。
网卡驱动层接口312用于虚拟网卡31与其管理的物理网卡驱动层的网卡句柄的传递。
链路监测单元32用于对物理网卡的链路连接状态进行监测，在链路切换条件满足时，输出链路切换通知。
链路切换单元33根据链路监测单元32输出的链路切换通知，将链路连接故障的物理网卡切换到链路连接良好的物理网卡，保证网络的稳定性及可靠性。
本发明实施例提供的上述双冗余装置的结构既能解决单IP地址的问题，又能保证对底层驱动程序尽可能少地更改，保证了虚拟网卡的通用性与各个模块的独立性，兼容性及可移植性更好。
在上述结构中，MUX层接口311是静态的，网卡驱动层接口312除了互相传递的参数是动态变化的之外也是静态的。链路监测单元32及链路切换单元33是动态的。链路监测单元32在实施链路监测的过程中启动一个定时器，隔一段时间就去检测网络的链路连接状态，若链路连接状态异常，则告知链路切换单元33，实现物理网卡的切换。物理网卡的切换致使两个物理网卡接口之间传递的网卡句柄的互换，最终实现了网络冗余的功能，保证了网络的稳定性及可靠性。
在本发明实施例中，对于虚拟网卡31的配置，主要是对MUX层接口311和网卡驱动层接口312两个接口的配置。虚拟网卡31不仅要用于TCP/IP网络协议栈与网卡数据链路层之间的数据传输，而且要呈现出物理网卡具有的特性，有实际的网络节点、MAC地址及IP地址。
虚拟网卡31的具体设计结构如图4所示，由图4可知，虚拟网卡31有其自身的函数列表，具体如下：
LOCAL NET_FUNCS vnetEndFuncTable =
{
(FUNCPTR)vnetEndStart,
(FUNCPTR)vnetEndStop,
(FUNCPTR)vnetEndUnload,
(FUNCPTR)vnetEndIoctl,
(FUNCPTR)vnetEndSend,
(FUNCPTR)vnetEndMCastAdd,
(FUNCPTR)vnetEndMCastDel,
(FUNCPTR)vnetEndMCastGet,
(FUNCPTR)vnetEndPollSend,
(FUNCPTR)vnetEndPollRcv,
vnetEndEtherAddressForm,
vnetEndEtherPacketDataGet,vnetEndEtherPacketAddrGet
};
NET_FUNCS为网卡驱动函数列表的结构体类型。
因此，在本发明实施例中，对虚拟网卡31的设计即转变成了函数列表中具体函数的设计。对于MUX层，虚拟网卡31提供了驱动加载时的函数列表，由VnetEndLoad函数加载虚拟网卡31的函数列表，返回虚拟网卡31的标识句柄给MUX层，数据从MUX层提供给TCP/IP网络协议栈处理。
对于虚拟网卡31与网卡驱动层的接口，除了VnetEndLoad函数有自己的具体实现外，其余的函数都是调用底层物理网卡的驱动函数，不同类型的物理网卡均有各自的底层驱动函数。具体物理网卡的驱动函数的选择由链路监测单元32及链路切换单元33来决定，当链路连接故障时，虚拟网卡31切换相应的物理网卡句柄，将链路连接良好的物理网卡句柄传递到网卡驱动层，使用链路连接良好的物理网卡收发数据。
作为本发明的一个实施例，在多网卡均要求双冗余设计的网络数据通信系统中，根据实际要求，要创建多个虚拟网卡，每个虚拟网卡管理两个互为冗余的物理网卡，互不干扰，每个虚拟网卡及其管理的两个互为冗余的物理网卡均呈现单MAC地址和单IP地址，但各个虚拟网卡的实现都采取图4中虚拟网卡的函数列表，在系统注册时使用不同的设备号来区别不同的虚拟网卡。
作为本发明的一个实施例，在链路连接状态的监测过程中，将链路连接状态分为四种状态：链路良好状态LINK_UP、链路良好到故障的过渡状态LINK_FAIL、链路故障到良好的过渡状态LINK_BACK、链路故障状态LINK_DOWN，当链路处于链路故障状态LINK_DOWN，且满足链路切换条件时，实施链路切换，如图5所示。其中：
LINK_UP与LINK_DOWN为两个稳定的状态，LINK_FAIL与LINK_BACK为两个过渡状态，即线路状态在链路良好状态LINK_UP与链路故障状态LINK_DOWN之间转换时，要在一定的时间内链路连接状态稳定后才能进行转换，必须满足时间条件才能进行链路连接状态的转换。
本发明实施例中，如图6所示，链路监测单元32包括定时循环监测模块321和链路连接状态转换模块322，定时循环监测模块321定时监测读取物理层（Physical Layer，PHY）状态寄存器，循环监测物理网卡的链路连接状态，链路连接状态转换模块322根据定时循环监测模块321监测的当前链路连接状态，将当前链路连接状态转换到相应的状态，在当前链路连接状态满足链路切换条件时，调用链路切换单元33实施链路切换。
具体的链路连接状态转换如图7所示，详述如下：
若链路的初始连接状态为链路良好状态LINK_UP，定时循环监测模块321定时监测读取PHY状态寄存器，若监测到链路连接状态为UP，则链路连接状态转换模块322将链路连接状态停留在链路良好状态LINK_UP，若链路连接状态为故障DOWN，则链路连接状态转换模块322将链路连接状态转换到链路良好到故障的过渡状态LINK_FAIL；定时循环监测模块321再去定时监测读取PHY状态寄存器，若监测到链路良好UP，则链路连接状态转换模块322将链路连接状态良好到故障过渡到链路良好状态LINK_UP，若监测到链路故障DOWN，则链路连接状态转换模块322判断链路故障延迟downDelay[N]是否已满足条件，若不满足，则将链路故障延迟downDelay[N]减1，将链路连接状态停留在链路良好到故障的过渡状态LINK_FAIL，等待定时循环监测模块321的下次监测；若故障延迟downDelay[N]为0，链路连接状态转换模块322将链路连接状态则转为链路故障状态LINK_DOWN，此时调用链路切换单元33，实施链路的切换。
若链路的初始状态为链路故障状态LINK_DOWN，定时循环监测模块321定时监测读取PHY状态寄存器，若监测到链路故障DOWN，则链路连接状态转换模块322将链路连接状态停留在链路故障状态LINK_DOWN，判断链路故障时间downTime[N]是否满足条件，若链路故障时间downTime[N]等于0，则调用链路切换单元33，实施链路的切换，若不满足条件，则对链路故障时间downTime[N]减1处理；若定时循环监测模块321监测到链路良好UP，则链路连接状态转换模块322将链路连接状态转换到链路故障到良好的过渡状态LINK_BACK，定时循环监测模块321再去定时监测读取PHY状态寄存器，若链路故障DOWN，则链路连接状态转换模块322将链路连接状态故障到良好过渡到链路故障状态LINK_DOWN，将链路故障时间downTime[N]复位；若定时循环监测模块321监测到链路良好UP，则链路连接状态转换模块322判断链路良好延迟upDelay[N]是否已满足条件，若不满足，将链路良好延迟upDelay[N]减1，将链路连接状态停留在链路故障到良好的过渡状态LINK_BACK，等待定时循环监测模块321的下次监测；若链路良好延迟upDelay[N]为0，则将链路连接状态转到链路良好状态LINK_UP。
图8示出了链路连接状态转换模块的结构，为了便于说明，仅示出了与本发明实施例相关的部分。
链路连接状态机3221记录链路连接状态的变化。链路切换条件配置模块3222配置链路切换的条件，例如链路故障延迟downDelay[N]、链路故障时间downTime[N]、链路良好延迟upDelay[N]等。链路转换控制模块3223根据定时循环监测模块321监测的物理网卡的链路连接状态，以及链路连接状态机3221记录的链路连接状态，控制链路连接状态的转换，当链路切换条件满足时，发出链路切换通知，调用链路切换单元33实施链路切换。
在存在多个虚拟网卡的网络数据通信系统中，每个虚拟网卡均有各自的链路监测单元来监测其管理的两个物理网卡的链路连接状态，互不影响，图6中的N即虚拟网卡的标识，表示第N个虚拟网卡。因此，若系统中有N个虚拟网卡，则需要创建N个定时监测看门狗任务。
链路切换单元33主要实现的是当前使用物理网卡的句柄与备用物理网卡的句柄之间的互换，具体流程如图9所示，详述如下：
在步骤S901中，判断有无链路切换的通知，有则执行步骤S902，否则继续执行步骤S901；
在S902步骤中，获取两条链路的状态；
在S903步骤中，判断两条链路是否均故障，是则返回执行步骤S901，否则执行步骤S904；
在步骤S904中，交换当前网卡与备用网卡的句柄；
在步骤S905中，置故障网卡为备用状态。
由图9可知，链路切换单元33处于等待切换通知信号的循环模式，若获取到链路切换通知信号，则获取两条链路的连接状态；若两条链路的连接状态均有故障，则不进行切换，否则获取链路连接状态良好的通路的网卡句柄，实现两条链路网卡句柄的互换，最后设置处于故障状态的链路处于备用状态。
在存在多个虚拟网卡的网络数据通信系统中，每个虚拟网卡均有各自的切换通知信号，实现的切换只发生在各自管理的两个物理网卡之间，若系统中有N个虚拟网卡，则启动N个切换任务，来实现各个虚拟网卡管理的两个物理网卡之间的双冗余切换。
在本发明实施例中， 单IP及MAC地址的实现是要保证虚拟网卡及其管理的两个互为冗余的物理网卡的IP及MAC地址相同，对上层应用程序及用户呈现单IP及MAC地址特性。
单IP地址的实现是通过虚拟网卡31实现的，在配置IP地址时，给每一个虚拟网卡配置各自的IP地址，注册进网络协议栈，数据在传输时通过虚拟网卡的IP地址可以传递到此虚拟网卡管理的两个物理网卡上。
单MAC地址的实现是通过获取其中一个物理网卡的MAC地址，然后给另一个物理网卡及虚拟网卡设置同样的MAC地址，这样的实现可以保证对于客户来说的单MAC地址。
每个虚拟网卡及其管理的两个互为冗余的物理网卡对于客户来说呈现相同的IP及MAC地址特性，若系统中有N个虚拟网卡，各个虚拟网卡及其管理的两个物理网卡均有各自的IP及MAC地址，各自相互独立，互不影响。
在本发明实施例中，兼容性包括虚拟网卡的扩展兼容及冗余网卡与非冗余网卡之间的兼容。
为了兼容不同系统中对双冗余的不同要求，在本发明实施例中，用一个全局描述表来维护多个虚拟网卡的扩展，全局描述表成员的示例结构如下：
struct net_end_tbl
{
int vUnit;/*virtual net number in endDevTbl*/
int rUnitNum1; /*the first net managed by virtual net*/
int rUnitNum2;/*the second net mangede by virtual net*/
char mac_data[6];/* MAC address */
char* pIpAddr;/*virtual net IP address*/
BOOL flag;/* flag*/
} NET_END_TBL;
上述结构中，vUnit为虚拟网卡在全局描述表中的序列号，rUnitNum1为虚拟网卡管理的第一个物理网卡标识，rUnitNum2为虚拟网卡管理的第二个物理网卡标识，mac_data[6]为MAC地址，pIpAddr为虚拟网卡的IP地址，pGateWay为虚拟网卡的网关。
全局描述表的示例结构如下：
NET_END_TBL netEndTbl[VNET_NUM]=
{
{0,rUnitNum1,rUnitNum2,{0x0,0x0,0x0,0x0,0x0,0x0},"IP地址","网关地址",FALSE},
……,
{ N,rUnitNum1,rUnitNum2,{0x0,0x0,0x0,0x0,0x0,0x0},"IP地址","MAC地址",FALSE},
};
在上述全局描述表中，VNET_NUM为虚拟网卡的数目，N等于VNET_NUM-1。
根据不同的系统要求，修改这个全局描述表则可以满足不同系统对双冗余的不同要求，例如将分属于不同虚拟网卡的两个物理网卡配置为互为冗余，或者通过增加、删减虚拟网卡的数目，调整冗余的物理网卡数量。通过修改全局描述表中虚拟网卡管理的两个物理网卡的标识可以方便地实现不同对的物理网卡的冗余；通过增加虚拟网卡的个数及两个物理网卡的标识可以实现两个物理网卡的非冗余要求到冗余要求的转变；通过删减虚拟网卡及其管理的两个物理网卡的标识可以实现两个物理网卡的冗余要求到非冗余要求的转变，大大提高了系统的兼容性。
另外，系统中有可能存在要求冗余功能的网卡及无冗余功能要求的网卡，针对此情况，在本发明实施例中，对于NET_END_TBL表中之外的网卡标识，均按无冗余功能要求的网卡处理，需要单独配置各自的IP地址。
本发明实施例在VxWorks系统的MUX层与网卡驱动层之间配置一个虚拟网卡，利用虚拟网卡管理两个物理网卡，实现多网卡双冗余架构，并实现了多网卡双冗余机制，支持多种类型的体系结构及网卡，可以满足不同系统对双冗余功能的要求。
以上所述仅为本发明的较佳实施例而已，并不用以限制本发明，凡在本发明的精神和原则之内所作的任何修改、等同替换和改进等，均应包含在本发明的保护范围之内。

Claims (11)

1、一种VxWorks系统下的多网卡双冗余装置，其特征在于，所述装置包括：
虚拟网卡，配置于MUX层与网卡驱动层之间，用于管理两个互为冗余的物理网卡，将链路连接良好的物理网卡句柄传递到网卡驱动层，使用链路连接良好的物理网卡收发数据；
链路监测单元，用于对物理网卡的链路连接状态进行监测，在链路切换条件满足时，输出链路切换通知；以及
链路切换单元，用于根据所述链路切换通知，将链路连接故障的物理网卡切换到链路连接良好的物理网卡；
所述虚拟网卡与其管理的两个互为冗余的物理网卡对外呈现相同的MAC地址和IP地址。
2、如权利要求1所述的装置，其特征在于，所述虚拟网卡包括：
MUX层接口，用于所述MUX层及虚拟网卡之间的数据传递；
网卡驱动层接口，用于所述虚拟网卡与其管理的物理网卡驱动层的网卡句柄的传递。
3、如权利要求1所述的装置，其特征在于，所述链路监测单元包括：
定时循环监测模块，用于定时循环监测物理网卡的链路连接状态；
链路连接状态转换模块，用于根据所述定时循环监测模块监测的当前链路连接状态，将当前链路连接状态转换到相应的状态，在当前链路连接状态满足链路切换条件时，调用所述链路切换单元实施链路切换。
4、如权利要求3所述的装置，其特征在于，所述链路连接状态转换模块包括：
链路连接状态机，用于记录链路连接状态的变化；
链路切换条件配置模块，用于配置链路切换的条件；
链路转换控制模块，用于根据所述定时循环监测模块监测的链路连接状态，以及所述链路连接状态机记录的链路连接状态，控制链路连接状态的转换，当链路切换条件满足时，发出链路切换通知。
5、如权利要求1至4任一权利要求所述的装置，其特征在于，所述链路连接状态包括链路良好状态、链路良好到故障的过渡状态、链路故障到良好的过渡状态，以及链路故障状态；
当链路处于链路故障状态，且满足链路切换条件时，实施链路切换。
6、一种网络数据通信系统，其特征在于，所述系统包括：
多个虚拟网卡，配置于MUX层与网卡驱动层之间，每个虚拟网卡具有单MAC地址和单IP地址，分别用于管理两个互为冗余的物理网卡，将链路连接良好的物理网卡句柄传递到网卡驱动层，使用链路连接良好的物理网卡收发数据；
多个与每个虚拟网卡对应的链路监测单元，用于对相应虚拟网卡所管理的物理网卡的链路连接状态进行监测，在链路切换条件满足时，输出链路切换通知；以及
多个与每个虚拟网卡对应的链路切换单元，用于根据所述链路切换通知，将相应虚拟网卡所管理的链路连接故障的物理网卡切换到链路连接良好的物理网卡；
所述每个虚拟网卡与其管理的两个互为冗余的物理网卡对外呈现相同的MAC地址和IP地址。
7、如权利要求6所述的系统，其特征在于，所述虚拟网卡包括：
MUX层接口，用于所述MUX层及虚拟网卡之间的数据传递；
网卡驱动层接口，用于所述虚拟网卡与其管理的物理网卡驱动层的网卡句柄的传递。
8、如权利要求6所述的系统，其特征在于，所述链路监测单元包括：
定时循环监测模块，用于定时循环监测物理网卡的链路连接状态；
链路连接状态转换模块，用于根据所述定时循环监测模块监测的当前链路连接状态，将当前链路连接状态转换到相应的状态，在当前链路连接状态满足链路切换条件时，调用所述链路切换单元实施链路切换。
9、如权利要求8所述的系统，其特征在于，所述链路连接状态转换模块包括：
链路连接状态机，用于记录链路连接状态的变化；
链路切换条件配置模块，用于配置链路切换的条件；
链路转换控制模块，用于根据所述定时循环监测模块监测的链路连接状态，以及所述链路连接状态机记录的链路连接状态，控制链路连接状态的转换，当链路切换条件满足时，发出链路切换通知。
10、如权利要求6所述的系统，其特征在于，所述多个虚拟网卡采用全局描述表维护，实现虚拟网卡的扩展兼容及冗余网卡与非冗余网卡之间的兼容；
所述全局描述表包含有虚拟网卡在全局描述表中的序列号，虚拟网卡管理的第一个物理网卡标识，虚拟网卡管理的第二个物理网卡标识，虚拟网卡的MAC地址，以及虚拟网卡的IP地址；
对于在所述全局描述表之外的物理网卡标识，按无冗余要求的物理网卡处理，单独配置所述物理网卡的IP地址。
11、如权利要求6至10任一权利要求所述的系统，其特征在于，所述链路连接状态包括链路良好状态、链路良好到故障的过渡状态、链路故障到良好的过渡状态，以及链路故障状态；
当链路处于链路故障状态，且满足链路切换条件时，实施链路切换。
PCT/CN2010/076292 2009-12-17 2010-08-24 一种VxWorks系统下的多网卡双冗余装置及系统 WO2011072536A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009101890476A CN102104470A (zh) 2009-12-17 2009-12-17 一种VxWorks系统下的多网卡双冗余装置及系统
CN200910189047.6 2009-12-17

Publications (1)

Publication Number Publication Date
WO2011072536A1 true WO2011072536A1 (zh) 2011-06-23

Family

ID=44157021

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076292 WO2011072536A1 (zh) 2009-12-17 2010-08-24 一种VxWorks系统下的多网卡双冗余装置及系统

Country Status (2)

Country Link
CN (1) CN102104470A (zh)
WO (1) WO2011072536A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102917390A (zh) * 2012-09-21 2013-02-06 北京创毅讯联科技股份有限公司 一种控制lte数据卡的连接状态的方法和系统
CN111371654A (zh) * 2020-03-18 2020-07-03 四川九州电子科技股份有限公司 一种智能融合产品网口自动化测试系统和方法
CN111628891A (zh) * 2020-05-25 2020-09-04 中车青岛四方车辆研究所有限公司 一种基于qnx的双以太网冗余的实现方法
CN112165446A (zh) * 2020-08-17 2021-01-01 河北汉光重工有限责任公司 一种VxWorks系统网络侦听方法
CN112260893A (zh) * 2020-10-14 2021-01-22 天津津航计算技术研究所 一种基于网络心跳的VxWorks操作系统的以太网冗余装置
CN113472635A (zh) * 2021-05-31 2021-10-01 杭州沃趣科技股份有限公司 一种实现双端口Active-Active的冗余保护方法和系统
CN113645048A (zh) * 2021-08-09 2021-11-12 武汉德创信通科技有限公司 网卡切换方法、装置以及现场可编程逻辑门阵列fpga
CN115022178A (zh) * 2022-06-24 2022-09-06 中国电信股份有限公司 网卡切换方法、装置、电子设备及可读存储介质

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102263660A (zh) * 2011-07-19 2011-11-30 中国舰船研究设计中心 双网卡冗余切换方法及装置
CN103312578B (zh) * 2012-03-12 2016-12-14 联想(北京)有限公司 一种获得网卡资源的方法及装置
CN103514121B (zh) * 2012-06-29 2016-05-25 中国船舶重工集团公司第七0九研究所 WindowsXp操作系统下一种网卡冗余切换方法
CN103023632B (zh) * 2012-12-31 2016-06-22 广东工业大学 一种无线网卡的通讯方法
CN103490971A (zh) * 2013-09-26 2014-01-01 山东神思电子技术股份有限公司 一种虚拟通信链路完整性监测方法及装置
CN103684719B (zh) * 2013-12-10 2017-02-15 中国船舶重工集团公司第七0九研究所 一种与平台无关的网络双冗余热切换方法
CN103944750B (zh) * 2014-03-14 2017-08-29 华为技术有限公司 一种绑定网卡故障处理方法及装置
CN104978174B (zh) * 2014-04-08 2018-04-27 华为技术有限公司 多操作系统中网卡之间的切换方法和系统
CN104468238A (zh) * 2014-12-22 2015-03-25 上海斐讯数据通信技术有限公司 基于vxworks系统的双网卡冗余切换方法
CN106656659B (zh) * 2016-11-30 2020-12-29 浙江宇视科技有限公司 一种网络路径的选择方法以及网络硬盘录像机
CN106612233B (zh) * 2016-12-29 2019-12-13 广州华多网络科技有限公司 一种多通道网络切换方法和系统
CN108632155B (zh) * 2017-03-16 2021-11-23 网宿科技股份有限公司 云平台流量调度方法和系统、计算机可读的存储介质
CN108155978B (zh) * 2017-11-27 2021-08-10 北京机电工程研究所 一种VxWorks环境下冗余网卡热备份的方法
CN108494534A (zh) * 2018-03-12 2018-09-04 西安电子工程研究所 一种自行防空武器系统双冗余以太网设计方法
CN110636637B (zh) * 2018-06-22 2021-08-20 视联动力信息技术股份有限公司 一种Linux设备的网络连接方法和装置
CN110690994A (zh) * 2019-09-25 2020-01-14 天津津航计算技术研究所 一种通用双冗余网卡切换的方法
CN111212451A (zh) * 2019-12-26 2020-05-29 曙光信息产业股份有限公司 一种切换网络传输通道的方法和装置
CN113626094A (zh) * 2021-06-21 2021-11-09 天津津航计算技术研究所 一种VxWorks下网卡MAC地址的操作方法
CN113794618B (zh) * 2021-09-17 2023-03-24 北京奥特雷柏科技有限公司 基于虚拟网卡的冗余网络通信方法、装置及终端设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5521913A (en) * 1994-09-12 1996-05-28 Amber Wave Systems, Inc. Distributed processing ethernet switch with adaptive cut-through switching
CN101404568A (zh) * 2008-11-17 2009-04-08 国电南瑞科技股份有限公司 双网卡热备冗余方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1324856C (zh) * 2004-01-05 2007-07-04 联想(北京)有限公司 一种基于多网卡的网络设备的数据传输方法和装置
JP4862743B2 (ja) * 2007-05-17 2012-01-25 日本電気株式会社 ノード、通信方法およびノード用プログラム
CN101309135B (zh) * 2008-03-07 2011-06-22 华中科技大学 一种提高工业无线传感器网络可靠性的方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5521913A (en) * 1994-09-12 1996-05-28 Amber Wave Systems, Inc. Distributed processing ethernet switch with adaptive cut-through switching
CN101404568A (zh) * 2008-11-17 2009-04-08 国电南瑞科技股份有限公司 双网卡热备冗余方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
YANG, SHENGWU ET AL.: "A realization method for Network Card Quick Switch Under vxWorks", COMPUTER AND MODERNIZATION, 28 February 2006 (2006-02-28) *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102917390A (zh) * 2012-09-21 2013-02-06 北京创毅讯联科技股份有限公司 一种控制lte数据卡的连接状态的方法和系统
CN111371654A (zh) * 2020-03-18 2020-07-03 四川九州电子科技股份有限公司 一种智能融合产品网口自动化测试系统和方法
CN111628891A (zh) * 2020-05-25 2020-09-04 中车青岛四方车辆研究所有限公司 一种基于qnx的双以太网冗余的实现方法
CN112165446A (zh) * 2020-08-17 2021-01-01 河北汉光重工有限责任公司 一种VxWorks系统网络侦听方法
CN112260893A (zh) * 2020-10-14 2021-01-22 天津津航计算技术研究所 一种基于网络心跳的VxWorks操作系统的以太网冗余装置
CN113472635A (zh) * 2021-05-31 2021-10-01 杭州沃趣科技股份有限公司 一种实现双端口Active-Active的冗余保护方法和系统
CN113645048A (zh) * 2021-08-09 2021-11-12 武汉德创信通科技有限公司 网卡切换方法、装置以及现场可编程逻辑门阵列fpga
CN113645048B (zh) * 2021-08-09 2024-02-02 武汉德创信通科技有限公司 网卡切换方法、装置以及现场可编程逻辑门阵列fpga
CN115022178A (zh) * 2022-06-24 2022-09-06 中国电信股份有限公司 网卡切换方法、装置、电子设备及可读存储介质
CN115022178B (zh) * 2022-06-24 2023-10-03 中国电信股份有限公司 网卡切换方法、装置、电子设备及可读存储介质

Also Published As

Publication number Publication date
CN102104470A (zh) 2011-06-22

Similar Documents

Publication Publication Date Title
WO2011072536A1 (zh) 一种VxWorks系统下的多网卡双冗余装置及系统
AU2004306913B2 (en) Redundant routing capabilities for a network node cluster
Wang et al. Virtual routers on the move: live router migration as a network-management primitive
JP5717164B2 (ja) コンピュータシステム、及びコンピュータシステムのメンテナンス方法
WO2019200728A1 (zh) 虚拟网关主备切换方法、装置及计算机可读存储介质
EP1117038A2 (en) Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system
WO2007140120A9 (en) Methods and apparatus for fast ethernet link switchover in the event of a link failure
JP6299640B2 (ja) 通信装置
WO2012100372A1 (en) Method for rru bypass in wireless communication network and rru device
JP7161008B2 (ja) アプリケーション冗長化管理システムおよびアプリケーション冗長化管理方法
KR20170053433A (ko) 방화벽의 이중화 방법 및 이를 위한 장치
JP4636247B2 (ja) パケットネットワークおよびレイヤ２スイッチ
JP4133738B2 (ja) 高速ネットワークアドレス引継ぎ方法、ネットワーク装置及びプログラム
JP2004297475A (ja) Ｌａｎスイッチおよびその通信制御方法
JP5862336B2 (ja) 通信制御装置、通信制御方法、及び通信制御プログラム
WO2020250407A1 (ja) 監視装置、冗長切替方法、冗長切替プログラム、および、ネットワークシステム
JPH11296396A (ja) 切替隠蔽機能付き高可用性システム
WO2021152670A1 (ja) 通信装置、切り替え制御方法、及びプログラム
JPH10247181A (ja) 拠点バックアップ計算機システム
WO2018179683A1 (ja) 監視システム、監視方法、情報処理装置および監視プログラム
JP4559497B2 (ja) 機能分散型パケット転送システムおよびその制御方法
JP5652770B2 (ja) ネットワークシステムおよび分岐接続装置
WO2012077949A2 (ko) 사이버 물리 시스템
Rajagopalan et al. Designing a Network for a Highly Available OpenShift on an HCI Appliance
JP2018166324A (ja) 監視システム、監視方法および監視プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10836973

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10836973

Country of ref document: EP

Kind code of ref document: A1