A communication device for use in a system including a database storing a unique identifier and position information for every mobile communication terminal is provided with an acquisition unit that acquires, based on the unique identifier of a mobile communication terminal serving as a communication destination, the position information of the mobile communication terminal serving as the communication destination from the database, and acquires an IP address of a router accommodating the mobile communication terminal serving as the communication destination, based on the acquired position information, and a communication unit that transmits a packet having the IP address in a header.

This application provides an address processing method and a network device. The method includes: obtaining, by a first network device, an address; determining, by the first network device, a length of a valid address of the address, where the valid address of the address is a 1.sup.st bit, whose bit value is 1, of the address to a last bit of the address; and adding, by the first network device when the length of the valid address of the address is less than a table width of a target table, S zeros before the valid address of the address to obtain an adjusted address, and processing the adjusted address based on the adjusted address and the target table, where S is a difference between the table width of the target table and the length of the valid address of the address.

The present disclosure provides example computer-implemented method, medium, and system for managing IP addresses for DPDK enabled network interfaces for cloud native pods. One example method includes creating a pod of one or more containers, where the pod connects to multiple networks through multiple network interfaces. A poll mode driver (PMD) is attached to a first network interface of the multiple network interfaces, where the PMD enables one or more data plane development kit (DPDK) applications inside the pod to manage the first network interface. A first container network interface (CNI) is created to handle the DPDK enabled first network interface. A first Internet protocol (IP) address is allocated to the first network interface using the first CNI. The first IP address is passed to the one or more DPDK applications using the first CNI.

A system for providing a Domain Name System (DNS) service may include providing an agent for installation on a subscriber device. The subscriber device may be connected to the DNS service via an entry point device. The system includes receiving, from the agent, agent data indicative of a subscriber identifier and a unique identifier associated with the entry point device. The system may then determine, based on the agent data, a current Internet Protocol (IP) address associated with the entry point device and associate the unique identifier with the subscriber identifier. The system may then dynamically map the subscriber identifier to the current IP address and provide DNS service to the subscriber device based on the current IP address.

Example implementations described herein are directed to systems and methods for managing internet protocol (IP) address assignment to servers on rack(s) based on their physical locations within the rack(s). Through the example implementations, the physical location of a server within a data center rack can be determined based on the IP address. Example implementations can involve issuing a ping local to determine a plurality of servers; retrieving power on time, current system time, and operating system (OS) uptime for each of the plurality of servers; determining a power on order for the plurality of servers; determining physical locations of the plurality of servers within one or more racks based on installation instructions and power on order; and assigning IP addresses to the plurality of servers based on the physical locations.

An access request scheduling method includes determining a city and a city operator corresponding to an access source IP segment; selecting, from cloud delivery nodes of the city operator, a preferred node of the access source IP segment; determining a mapping relationship between the access source IP segment and an IP of the preferred node; and issuing the mapping relationship to scheduling agent modules of the cloud delivery nodes in a network.

Techniques are presented herein for providing a persistent external Internet Protocol (IP) address for extra-cluster services. One example involves initiating, in a cluster, a first pod with a label that identifies a service. The first pod is configured to provide the service to one or more network entities outside the cluster. The first pod is assigned an IP address configured for communicating outside the cluster. A mapping of the service to the IP address is stored. In response to a determination that the service has been disrupted, a second pod is initiated in the cluster with the label that identifies the service. The second pod is configured to provide the service to the one or more network entities outside the cluster. Based on the mapping and the label that identifies the service, the IP address is assigned to the second pod.

Systems and methods for InfiniBand fabric optimizations to minimize SA access and startup failover times. A system can comprise one or more microprocessors, a first subnet, the first subnet comprising a plurality of switches, a plurality of host channel adapters, a plurality of hosts, and a subnet manager, the subnet manager running on one of the one or more switches and the plurality of host channel adapters. The subnet manager can be configured to determine that the plurality of hosts and the plurality of switches support a same set of capabilities. On such determination, the subnet manager can configure an SMA flag, the flag indicating that a condition can be set for each of the host channel adapter ports.

Systems and methods for transparent high availability for customer virtual machines using a hypervisor-based side channel bonding and monitoring are disclosed herein. The method can include creating a network path bond between at least one compute instance and a plurality of Network Virtualization Devices (“NVD”), the network path bond including a plurality of network paths, each network path connecting the compute instance with the Virtualized Network Interface Card (“VNIC”) of one of the plurality of NVDs, identifying a first one of the network paths as an active network path and a second one of the network paths as an inactive network path, performing a health check on the active network path, determining that the active network path failed the health check, marking the first one of the network paths as failed subsequent to determining that the active network path failed the health check, and identifying the second one of the network paths as the active network path.

An example method of identifying a hybrid connection associated with a network flow in a multi-cloud computing system includes: obtaining, by a network analyzer, network information from a plurality of data centers in the multi-cloud computing system, the plurality of data centers corresponding to a respective plurality of namespaces; identifying Internet Protocol (IP) subnetworks associated with the hybrid connection from the network information; generating connection indexes for the namespaces relating source IP subnetworks of the IP subnetworks, destination IP subnetworks of the IP subnetworks, and an identifier for the hybrid connection; searching a source IP address and a destination IP address of a flow record for the network flow in the connection indexes to obtain the identifier for the hybrid connection; and tagging the flow record with the identifier for the hybrid connection.