AON Network Management
Networking made simple.
Virtual networking is the foundation of any Enterprise Cloud
Cloudistics AON™ Network management is the foundation for the industry-leading capabilities of the Cloudistics platform. By simplifying the network layer, Cloudistics makes compute resources, storage resources, hypervisors, and geographic locations deployable, manageable and supportable—without losing any core value and functionality, all through one pane of glass.
AON’s patented technology provides unique capabilities and rich features to drive agility, compliance, rigidity, and control that many organizations require. Whether the goal is to simply take advantage of Cloudistics network orchestration to deliver software-defined storage, compute, virtualization, one-click Application deployments and single pane of glass management OR to deliver a self-service, secure and controlled network for DevOps and API driven controls, AON Network management is at the heart of the Cloudistics platform that allows customers to meet these needs.
No other product has the ability for IT teams to manage the entire infrastructure platform including all its hardware and software layers from one console and still reside behind an organizations firewall. Therefore, Cloudistics boasts of delivering a TRUE cloud experience, and our customers agree. AON Network management is the core of making that Cloud experience a premium one.
features and capabilities
AON allows networks to be partitioned and isolated using either VLANs or virtual networks (VNETs) or both. Customers that use VLANs today may continue to use VLANs in Cloudistics. They may import their existing VMs and VLANs on other infrastructure onto the Cloudistics platform, or they may create new VLANs. We support up to 64 VLANs today. VNETs are virtual networks that are natively integrated into the platform and simplify application deployments, security, network isolation, and resource planning.
With AON™ virtual networking and application level firewall rules, Cloudistics supports true micro-segmentation. By implementing micro-segmentation at the network layer, we can secure individual applications in their own secure islands.
Network virtualization with the Cloudistics VNETs allows virtual networks to be dynamically created and destroyed in support of application needs, without requiring the manual reconfiguration of the underlying physical network. Virtual networks are much easier to use and manage than VLANs (virtual local area networks). Unlike VLANs, they support network address-preserving workload migrations.
Native Network Virtualization Built-in
Cloudistics is the only platform the natively supports network virtualization. It is the 3rd leg of the stool and is essential for a true software-defined data center (SDDC) that can match the agility of the public cloud.
Line-speed network virtualization
AON approach to virtual networking delivers line-speed east/west networking between all of its resources from the application through compute and its underlying storage. This is the heart of any enterprise cloud infrastructure.
64 vNIC’s per VM
A VM can have multiple virtual NICs or vNICs; we support 64 vNICs per VM.
A vNIC can either be in bridged mode (meaning it does not use virtual networking) or in virtual networking mode. A vNIC may have multiple IP addresses, this is important for an application such as a Load Balancer.
Network Function Virtualization (NFV)
Networking functions such as switching, DHCP and firewalls are implemented in software and are built-in. Each VNET automatically creates its own NFV and its associated microservices. These microservices can be managed from the portal.
Support for 3rd Party NFV’s
For more advanced functionality, customers can choose custom NFV’s provided from other vendors such as Palo Alto Networks, F5 and Citrix Netscaler Load Balancer.
Public and Private VNETS
Cloudistics allows the range of IP addresses used for VNETs to be either public or private, though most of our customers use private IP addresses today. If you use public addresses, that means the range of IP addresses used are unique across the Internet. If you use private addresses that means the range of IP addresses that are used are unique across that organization and cannot be used anywhere else in the organization. Public and Private VNETs may be used by VMs running in any VDC.
All north-south traffic flows through our router/switch. We use layer 3 protocols like BGP or eBGP to advertise upstream a bunch of routes for which we are to be considered the default gateway. If one of our VMs migrates to a different Cloudistics rack/POD with a different physical switch/router, we send out a BGP update. All southbound IP traffic from the outside world will be sent to our router/switch. The data center network administrator may use BGP filtering to control which packets are routed to/from our switch/router. If the traffic is intended for a VM in bridged mode, the traffic is routed directly to that VM. Else if the VM is in virtual networking mode, the traffic is routed to the NFV VM for the virtual network the VM belongs to.