Abstract: One embodiment discloses a method and apparatus for synchronizing IP information of virtual machines. The method includes: obtaining an IP relevant message of at least one virtual machine within a subnet, recording IP information and connection information of the at least one virtual machine based on the IP relevant message, and modifying connection information of a specific virtual machine in response to migration of the specific virtual machine. The apparatus corresponds to the method. With the method and apparatus above, IP information and connection information of respective virtual machines within the subnet are recorded regularly and routinely. Once a certain virtual machine is migrated, updating and modifying connection information of the migrated virtual machine is only needed, but without a need for resending a request to the Dynamic Host Configuration Protocol (DHCP) server. Thus, network disruptions caused by non-synchronization of IP information when the virtual machine is migrated are avoided.

Abstract: A PVLAN switch for connecting a PVLAN to a non-PVLAN device is configured as a primary VLAN with secondary VLANs, the primary VLAN includes promiscuous ports, each of the secondary VLANs includes a smart PVLAN trunk port, and the smart PVLAN trunk port is included in at least two secondary VLANs where the smart PVLAN trunk port and the promiscuous port connect to non-PVLAN devices. A frame is received on a smart PVLAN trunk port sent from a non-PVLAN device, and includes a destination address and a secondary VLAN ID. The PVLAN switch port ID for the first frame, and a primary VLAN ID for the secondary VLAN ID are identified. If the frame is a non-isolated port, the secondary VLAN ID is modified to be the primary VLAN ID, and the modified frame is sent to another non-PVLAN device connected to the PVLAN switch port.

Abstract: A PVLAN switch for connecting a PVLAN to a non-PVLAN device is configured as a primary VLAN with secondary VLANs, the primary VLAN includes promiscuous ports, each of the secondary VLANs includes a smart PVLAN trunk port, and the smart PVLAN trunk port is included in at least two secondary VLANs where the smart PVLAN trunk port and the promiscuous port connect to non-PVLAN devices. A frame is received on a smart PVLAN trunk port sent from a non-PVLAN device, and includes a destination address and a secondary VLAN ID. The PVLAN switch port ID for the first frame, and a primary VLAN ID for the secondary VLAN ID are identified. If the frame is a non-isolated port, the secondary VLAN ID is modified to be the primary VLAN ID, and the modified frame is sent to another non-PVLAN device connected to the PVLAN switch port.

Abstract: A PVLAN switch for connecting a PVLAN to a non-PVLAN device is configured as a primary VLAN with secondary VLANs, the primary VLAN includes promiscuous ports, each of the secondary VLANs includes a smart PVLAN trunk port, and the smart PVLAN trunk port is included in at least two secondary VLANs where the smart PVLAN trunk port and the promiscuous port connect to non-PVLAN devices. A frame is received on a smart PVLAN trunk port sent from a non-PVLAN device, and includes a destination address and a secondary VLAN ID. The PVLAN switch port ID for the first frame, and a primary VLAN ID for the secondary VLAN ID are identified. If the frame is a non-isolated port, the secondary VLAN ID is modified to be the primary VLAN ID, and the modified frame is sent to another non-PVLAN device connected to the PVLAN switch port.

Abstract: A PVLAN switch for connecting a PVLAN to a non-PVLAN device is configured as a primary VLAN with secondary VLANs, the primary VLAN includes promiscuous ports, each of the secondary VLANs includes a smart PVLAN trunk port, and the smart PVLAN trunk port is included in at least two secondary VLANs where the smart PVLAN trunk port and the promiscuous port connect to non-PVLAN devices. A frame is received on a smart PVLAN trunk port sent from a non-PVLAN device, and includes a destination address and a secondary VLAN ID. The PVLAN switch port ID for the first frame, and a primary VLAN ID for the secondary VLAN ID are identified. If the frame is a non-isolated port, the secondary VLAN ID is modified to be the primary VLAN ID, and the modified frame is sent to another non-PVLAN device connected to the PVLAN switch port.

Abstract: A PVLAN switch for connecting a PVLAN to a non-PVLAN device is configured as a primary VLAN with secondary VLANs, the primary VLAN includes promiscuous ports, each of the secondary VLANs includes a smart PVLAN trunk port, and the smart PVLAN trunk port is included in at least two secondary VLANs where the smart PVLAN trunk port and the promiscuous port connect to non-PVLAN devices. A frame is received on a smart PVLAN trunk port sent from a non-PVLAN device, and includes a destination address and a secondary VLAN ID. The PVLAN switch port ID for the first frame, and a primary VLAN ID for the secondary VLAN ID are identified. If the frame is a non-isolated port, the secondary VLAN ID is modified to be the primary VLAN ID, and the modified frame is sent to another non-PVLAN device connected to the PVLAN switch port.

Abstract: A PVLAN switch for connecting a PVLAN to a non-PVLAN device is configured as a primary VLAN with secondary VLANs, the primary VLAN includes promiscuous ports, each of the secondary VLANs includes a smart PVLAN trunk port, and the smart PVLAN trunk port is included in at least two secondary VLANs where the smart PVLAN trunk port and the promiscuous port connect to non-PVLAN devices. A frame is received on a smart PVLAN trunk port sent from a non-PVLAN device, and includes a destination address and a secondary VLAN ID. The PVLAN switch port ID for the first frame, and a primary VLAN ID for the secondary VLAN ID are identified. If the frame is a non-isolated port, the secondary VLAN ID is modified to be the primary VLAN ID, and the modified frame is sent to another non-PVLAN device connected to the PVLAN switch port.

Abstract: A PVLAN switch for connecting a PVLAN to a non-PVLAN device is configured as a primary VLAN with secondary VLANs, the primary VLAN includes promiscuous ports, each of the secondary VLANs includes a smart PVLAN trunk port, and the smart PVLAN trunk port is included in at least two secondary VLANs where the smart PVLAN trunk port and the promiscuous port connect to non-PVLAN devices. A frame is received on a smart PVLAN trunk port sent from a non-PVLAN device, and includes a destination address and a secondary VLAN ID. The PVLAN switch port ID for the first frame, and a primary VLAN ID for the secondary VLAN ID are identified. If the frame is a non-isolated port, the secondary VLAN ID is modified to be the primary VLAN ID, and the modified frame is sent to another non-PVLAN device connected to the PVLAN switch port.

Abstract: Embodiments of the invention relate to synchronizing multicast groups of a virtual machine during migration of the virtual machine. A first list and a second list, indicating multicast groups corresponding to the first port and second port respectively, are obtained in response to detection of migration of the virtual machine from a first port to a second port of a same switch. The second list is updated so that the second list contains the multicast groups in the first list. An undesired multicast group is aged. Multicast groups of a virtual machine may be synchronized in the process of migration of the virtual machine, thereby reducing or removing the time during which the virtual machine multicast service is disrupted.

Abstract: Embodiments of the invention relate to synchronizing multicast groups of a virtual machine during migration of the virtual machine. A first list and a second list, indicating multicast groups corresponding to the first port and second port respectively, are obtained in response to detection of migration of the virtual machine from a first port to a second port of a same switch. The second list is updated so that the second list contains the multicast groups in the first list. An undesired multicast group is aged. Multicast groups of a virtual machine may be synchronized in the process of migration of the virtual machine, thereby reducing or removing the time during which the virtual machine multicast service is disrupted.

Abstract: A PVLAN switch for connecting a PVLAN to a non-PVLAN device is configured as a primary VLAN with secondary VLANs, the primary VLAN includes promiscuous ports, each of the secondary VLANs includes a smart PVLAN trunk port, and the smart PVLAN trunk port is included in at least two secondary VLANs where the smart PVLAN trunk port and the promiscuous port connect to non-PVLAN devices. A frame is received on a smart PVLAN trunk port sent from a non-PVLAN device, and includes a destination address and a secondary VLAN ID. The PVLAN switch port ID for the first frame, and a primary VLAN ID for the secondary VLAN ID are identified. If the frame is a non-isolated port, the secondary VLAN ID is modified to be the primary VLAN ID, and the modified frame is sent to another non-PVLAN device connected to the PVLAN switch port.

Abstract: Embodiments of the invention relate to synchronizing multicast groups of a virtual machine during migration of the virtual machine. A first list and a second list, indicating multicast groups corresponding to the first port and second port respectively, are obtained in response to detection of migration of the virtual machine from a first port to a second port of a same switch. The second list is updated so that the second list contains the multicast groups in the first list. An undesired multicast group is aged. Multicast groups of a virtual machine may be synchronized in the process of migration of the virtual machine, thereby reducing or removing the time during which the virtual machine multicast service is disrupted.

Abstract: One embodiment discloses a method and apparatus for synchronizing IP information of virtual machines. The method includes: obtaining an IP relevant message of at least one virtual machine within a subnet, recording IP information and connection information of the at least one virtual machine based on the IP relevant message, and modifying connection information of a specific virtual machine in response to migration of the specific virtual machine. The apparatus corresponds to the method. With the method and apparatus above, IP information and connection information of respective virtual machines within the subnet are recorded regularly and routinely. Once a certain virtual machine is migrated, updating and modifying connection information of the migrated virtual machine is only needed, but without a need for resending a request to the Dynamic Host Configuration Protocol (DHCP) server. Thus, network disruptions caused by non-synchronization of IP information when the virtual machine is migrated are avoided.

Abstract: Embodiments of the invention relate to synchronizing multicast groups of a virtual machine during migration of the virtual machine. A first list and a second list, indicating multicast groups corresponding to the first port and second port respectively, are obtained in response to detection of migration of the virtual machine from a first port to a second port of a same switch. The second list is updated so that the second list contains the multicast groups in the first list. An undesired multicast group is aged. Multicast groups of a virtual machine may be synchronized in the process of migration of the virtual machine, thereby reducing or removing the time during which the virtual machine multicast service is disrupted.