Abstract: Embodiments disclosed herein relate to source-based symmetric routing of network traffic in virtual networks. In particular, a source of network traffic in the virtual network is equipped with a routing table that causes the source of the network traffic to route the network traffic symmetrically across zones of the virtual network.

Abstract: Embodiments disclosed herein relate to source-based symmetric routing of network traffic in virtual networks. In particular, a source of network traffic in the virtual network is equipped with a routing table that causes the source of the network traffic to route the network traffic symmetrically across zones of the virtual network.

Abstract: A device may receive a firewall filter entry that includes one or more match conditions associated with filtering network traffic. The device may identify an access control list (ACL) template associated with the firewall filter entry. The ACL template may be associated with a template type. The device may identify one or more rules, for verifying the firewall filter entry, based on the template type associated with the ACL template. The device may verify the firewall filter entry using the one or more rules. The device may determine a hardware resource, for storing the firewall filter entry, based on the template type and based on verifying the firewall filter entry. The device may store the firewall filter entry using the hardware resource of the device.

Abstract: A device may receive a firewall filter entry that includes one or more match conditions associated with filtering network traffic. The device may identify an access control list (ACL) template associated with the firewall filter entry. The ACL template may be associated with a template type. The device may identify one or more rules, for verifying the firewall filter entry, based on the template type associated with the ACL template. The device may verify the firewall filter entry using the one or more rules. The device may determine a hardware resource, for storing the firewall filter entry, based on the template type and based on verifying the firewall filter entry. The device may store the firewall filter entry using the hardware resource of the device.

Abstract: A device may receive an indication to perform a reboot associated with a network service being provided using a first virtual machine (VM) running on the device. The device may launch, based on receiving the indication, a second VM on the device. The device may shut down, based on launching the second VM, the first VM. The device may configure the second VM for forwarding control plane traffic associated with the network service. The device may configure, based on configuring the second VM for forwarding the control plane traffic, the second VM for forwarding data plane traffic associated with the network service. The device may provide, based on configuring the second VM for forwarding the data plane traffic, the network service using the second VM.

Abstract: A device may receive a firewall filter entry that includes one or more match conditions associated with filtering network traffic. The device may identify an access control list (ACL) template associated with the firewall filter entry. The ACL template may be associated with a template type. The device may identify one or more rules, for verifying the firewall filter entry, based on the template type associated with the ACL template. The device may verify the firewall filter entry using the one or more rules. The device may determine a hardware resource, for storing the firewall filter entry, based on the template type and based on verifying the firewall filter entry. The device may store the firewall filter entry using the hardware resource of the device.

Abstract: A device may receive an indication to perform a reboot associated with a network service provided via a first virtual machine (VM) of the device and a first container of the device. The device may create a second VM with a boot mode enabled and a second container with the boot mode enabled. The boot mode, while enabled on the second VM, may prevent the second VM from communicating with the first container. The boot mode, while enabled on the second container, may prevent the second container from communicating with the first VM. The device may shut down the first container. The device may disable, after shutting down the first container, the boot mode on the second VM. The device may disable the boot mode on the second container. The device may cause the network service to be provided by the second container and the second VM.