A transceiver arrangement comprising a receiver and a transmitter arranged for frequency-division duplex communication with a communication network, a transmission port for connecting to an antenna, a balancing impedance circuit arranged to provide an adaptive impedance arranged to mimic the impedance at the transmission port, a filtering arrangement connecting the receiver, transmitter, transmission port and balancing impedance circuit, and a common-mode signal reduction circuit is disclosed. The filter arrangement comprises filters of a first type arranged to pass signals at transmitter frequency and attenuate signals at receiver frequency and are connected between the transmitter and the transmission port and between the receiver and the balancing impedance circuit, and filters of a second type arranged to attenuate signals at transmitter frequency and pass signals at receiver frequency and are connected between the transmitter and the balancing impedance circuit and between the receiver and the transmission port. The common-mode signal reduction circuit comprises an inverting amplifier, the input of the inverting amplifier is provided by a voltage division between a first and a second impedance where the first and second impedance have equal impedances, and the output of the amplifier is provided to junction of a third and a fourth impedance where the third and fourth impedances have equal impedances, and the first and second impedances, and the third and fourth impedances, respectively, are connected in series between a filter of the first type and a filter of the second type. A communication device and method are also disclosed.

Two embodiments of a one-way network interface card are disclosed, a transmit-only version and a receive-only version. A network controller mounted on the circuit card is coupled to the host computer via a host computer interface. A first processor is coupled to a network interface of the network controller. A second processor has a separate network interface for communicating with a remote computer. A one-way link is coupled between the first processor and the second processor. For the transmit-only embodiment, the one-way link only allows information to be transferred from the first processor to the second processor, and thus information may only pass from the host computer to the remote computer. For the receive-only embodiment, the one-way link only allows information to be transferred from the second processor to the first processor, and thus information may only pass from the remote computer to the host computer.

A multi-chip module (MCM) may include a substrate, and first and second physical-layer (PHY) chips mounted on the substrate. In some implementations, the first PHY chip includes a multiplexer and a PHY circuit. The multiplexer is configured to receive a multiplexed data stream from a media access control (MAC) device, to demultiplex the multiplexed data stream into first and second data streams, to output the first data stream to the PHY circuit, and to output the second data stream to the second PHY chip. In some implementations, the first PHY includes a router and a PHY circuit. The router is configured to receive a plurality of data packets from a MAC device, to route one or more of the data packets having a first address to the PHY circuit, and to route one or more of the data packets having a second address to the second PHY chip.

In one embodiment, quasi-Output Queue behavior of a packet switching device is achieved using virtual output queue (VOQ) ordering independently determined for each particular output queue (OQ), including using maintained latency information of the VOQs of the particular OQ. In one embodiment, all packets from all VOQs with a same port-priority destination experience similar latency within specific time-window, which is similar to the packet service provided by an Output Queue switch architecture. In one embodiment, all input ports that send traffic to same output port-priority receive bandwidth which is proportional to their bandwidth demand divided by total bandwidth. Prior approaches that emulate the performance of an OQ switch architecture require complex and time-consuming scheduling determinations and do not scale. Independently determining the order for sending packets from the VOQs associated with each particular OQ provides a scalable and implementable system with quasi-Output Queue behavior.

Topology discovery between compute nodes and interconnect switches including creating, on an interconnect switch, a virtual topology discovery device for a first port, wherein the interconnect switch is coupled to a compute node via the first port, and wherein the virtual topology discovery device comprises a port identifier for the first port; mapping the virtual topology discovery device to the first port; receiving an inventory request from the compute node via the first port; routing the inventory request to the virtual topology discovery device for the first port; and sending, from the virtual topology discovery device for the first port, the port identifier to the compute node.

A failure at a first port of the controller node is detected, where the first port is initially assigned a first port identifier and is associated with a logical path through a communications fabric between the first port and a port at a host device. In response to detecting the failure, the first port identifier is assigned to a second port to cause the logical path to be associated with the second port. In response to detecting resolution of the failure, a probe identifier is assigned to the first port. Using the probe identifier, a health of network infrastructure between the first port and the host device is checked. In response to the checking, the first port identifier is assigned to the first port to cause failback of the logical path to the first port.

Described herein are systems, methods, and software to enhance network traffic management. In one implementation, a first host identifies a packet to be transferred from a first virtual machine on the first host to a second virtual machine on a second host. In response to identifying the packet, the first host identifies a source logical port for the first virtual machine, and transferring a communication to the second host, wherein the communication encapsulates the data packet and the source logical port. Once the packet is received by the second host, the second host may use the source logical port to determine a forwarding action for the packet.

Apparatuses, methods and storage medium associated with routing data in a switch are provided. In embodiments, the switch may include route lookup circuitry determine a first set of output ports that are available to send a data packet to a destination node. The lookup circuitry may further select, based on respective congestion levels associated with the first set of output ports, a plurality of output ports for a second set of output ports from the first set of output ports. An input queue of the switch may buffer the data packet and route information associated with the second set of output ports. The switch may further include route selection circuitry to select a destination output port from the second set of output ports, based on updated congestion levels associated with the output ports of the second set of output ports. Other embodiments may be described and/or claimed.

A first ingress interface on a switch receives a first control packet for establishing a Transmission Control Protocol (TCP) session and selects a first engine running on a first line card in the switch. A second ingress interface receives a second control packet and selects the same first engine. Data associated with the TCP session received by the first or second ingress interface subsequent to establishing the TCP session is to be forwarded to the first engine. The first ingress interface receives a third control packet and sends, to the selected first engine, a notification indicating the TCP session which is to be tracked. The first or second ingress interface receives a fourth packet with a payload associated with the TCP session and forwards, to the selected first engine, a copy of the fourth packet, thereby facilitating a plurality of engine instances to support application identification.

Methods and Systems are described for control at/of a network node. The network node can include a control module and first and second modules coupled to the control module. The first module can be configured to select first input/output (I/O) types of a field device coupled at an I/O interface of the network node. The second module can be configured to select a second I/O types of the field device. The first and second modules can be coupled to the I/O interface through a field device coupler.