Techniques for propagating routing awareness for autonomous networks are described. In at least some embodiments, routing awareness refers to attributes of autonomous networks that route communication sessions between different endpoints. According to various embodiments, routing awareness indicates whether a particular autonomous network supports a protocol for propagating routing awareness among different autonomous networks. Routing awareness may also include performance attributes of autonomous networks. Such routing awareness enables entities involved in routing communication sessions to make informed decisions regarding routing and handling of communication sessions.

Exemplary methods performed by a first network device (ND) include generating first and second prefix entries associating incoming Internet Protocol (IP) traffic to first and second data structures (DSs), respectively. Generating the first DS includes generating a first proxy including forwarding information causing incoming IP traffic to be forwarded to a second ND, and generating a second proxy referencing a third DS. Generating the second DS includes generating a first proxy including forwarding information causing incoming IP traffic to be forwarded to the second ND, and generating a second proxy referencing the third DS. The methods include generating the third DS including forwarding information causing the incoming IP traffic to be forwarded to a third ND, the third DS further including first state information indicating whether the forwarding information included in the first proxies of the first and second DSs should be used for forwarding the incoming IP traffic.

The present disclosure provides a technique for ensuring that a service or conversation is carried in a congruent manner on a Link Aggregation Group (LAG). The Service ID (e.g., conversation ID) to link mapping is configured on both sides of the LAG independently of each other. The Service ID to link assignment is stored in a well-defined format, e.g. in an assignment table. A digest is then prepared on the assignment table. The digest is exchanged between the two sides of the LAG. If there is a mismatch between the digests, then the service is transmitted on a predefined and agreed-upon default link if congruency has to be enforced for that particular service. Furthermore, the digest exchange allows verification on the configuration to check whether all services to be handed-off are configured on both sides.

A multi-link convergence method include: receiving a first binding request sent by a client using a first link; sending a first LSID to the client using the first link; receiving a first authentication request sent by the client using the first link; performing authentication on the first link according to the first authentication request; if the first link is authenticated successfully, sending a BID to the client using the first link; receiving a second binding request sent by the client using a second link, where the second binding request carries the BID; sending a second LSID to the client using the second link; receiving a second authentication request sent the client by using the second link; performing authentication on the second link according to the second authentication request; and if the second link is authenticated successfully, sending a binding acknowledgement message to the client by using the second link.

A fully-connected mesh network includes a plurality of switches. A first switch receives a packet traveling through the mesh network from an external source node to an external destination node specified by the packet. A plurality of links, which are all included in a mesh link aggregation group (LAG), couple each possible pair of the switches by a respective single link. Each of the respective links is included individually in an individual LAG. Each of the switches is configured to receive a packet from another switch of the plurality of switches via only the mesh LAG, and each switch that receives a packet via the mesh LAG is configured to transmit the packet to another switch of the plurality of switches via only one of the individual LAGs. The packet travels to the destination node at most two hops across the plurality of switches.

A network system, method, and device are provided for improving network communication performance between at least a first client site and a second client site, where the first client site and the second client site are at a distance from one another that is such that would usually require long haul network communication. The network system includes at least one network bonding/aggregation computer system for bonding or aggregating one or more diverse network connections so as to configure a bonded/aggregated connection that has increased throughput; and at least one network server component, configured to interoperate with the client site network component, the network server component including a server/concentrator or a cloud concentrator element that is implemented at an access point to an multiple protocol label switching network.

A method and a multi-switch architecture include learning a media access control (MAC) address at a first switch in a multi-switch architecture; storing the MAC address in a forwarding database of the first switch; transmitting a data frame to one or more switches in the multi-switch architecture via inter-switch connectivity between the first switch and the one or more switches, wherein the data frame is created to enable the one or more switches to learn the MAC address therefrom; learning the MAC address from the data frame at the one or more switches; and storing the MAC address in a forwarding database for each of the one or more switches. This further includes transmitting the data frame via ports and queues in the inter-switch connectivity that are separate from ports and queues in a data path between the first switch and the one or more switches to avoid data path interference.

Disclosed are a method and system for information interaction between systems in a same portal in a distributed resilient network interconnection, wherein the method is applied to each system in an portal in a link aggregation group, including: sending a distributed relay control protocol (DRCP) message through an intra-portal interface, wherein at least system information of a present system is carried; after receiving a DRCP message sent by an adjacent system, if it is determined that the present system and the adjacent system can form one portal in the distributed resilient network interconnection, determining an operational Key value of the present system. The system includes: a sending state machine, a receiving state machine, a negotiating state machine, a synchronizing state machine and a periodic sending state machine.

The present document discloses a notification method and device and an acquisition device for a MAC address of ESADI. The method includes: a RB issuing a MAC address which is reachable natively by the RB via a LSP of the ESADI; and Step 204: the RB notifying multiple RBs which correspond to the MAC address and belong to the same MC-LAG by way of a MAC-Reachability TLV extension of the LSP. The present document solves the problem in the related technology that the RB is unable to notify the remote RB of native multi-chassis RB IDs when accessing the TRILL network by a multi-chassis access, so that the remote RB can acquire which RBs belong to the same MC-LAG, thereby improving the flexibility of the processing manner.

An information handling system is provided. The information handling system includes a plurality of aggregation devices configured to distribute information in a virtual link trunk and a plurality of nodes coupled to the aggregation devices. When one of the plurality of aggregation devices received a reboot command, that aggregation device is configured to transmit a first message to the nodes indicating that the aggregation device is rebooting, receive a first acknowledgement message from the nodes indicating that they will not send any information to the rebooting aggregation device. The aggregation device is then configured to reboot, receive a second message from the nodes indicating the nodes are ready to receive information from the rebooted aggregation device, transmit a second acknowledgement message to the nodes indicating that the rebooted aggregation device has rebooted and is capable of receiving information, and receive information from at least one of the nodes for transmission to at least one other node.