Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »


1. Manage networks



1.1. Limit Public IP bandwidths for a VDC

Unable to render {include} The included page could not be found.



1.2. Reserve private IPs

The private IP reservation feature will prevent users from assigning reserved IPs to VMs within the platform. The platform does not display reserved IPs to allow users to select them for VMs. You can only assign reserved IPs to VMs from outside of Abiquo, for example, using a script. If you onboard a VM with a reserved IP, the platform logs a warning message.

Privileges: Manage private IP reservation

To reserve private IPs:

  1. Go to Virtual datacenters → Networks → Private

  2. Select the IPs and click the lock button

  3. Enter the reason for the reservation

  4. The platform will list the VMs in the virtual datacenter. Optionally select VMs to indicate where the IPs might be used. Note that you must check that the VMs are able to use these IPs. This selection does not assign the IPs to VMs.

    Select private IPs to reserve

The platform will display a padlock symbol and the reason beside the IP reserved addresses.

Reserved private IP address



2. Manage NAT



3. Manage firewalls

3.1. Introduction to firewalls

Unable to render {include} The included page could not be found.

3.2. Display firewall policies

Unable to render {include} The included page could not be found.

3.3. Synchronize firewall policies

Unable to render {include} The included page could not be found.

3.4. Create a firewall policy

Unable to render {include} The included page could not be found.

3.5. Edit firewall rules

You can define firewall rules for inbound and outbound traffic in your firewall policy.

In AWS, before you edit firewall rules, synchronize the firewall to update the rules because AWS will not allow you to create a rule that already exists in the security group. Remember that it may take some time for firewall rules to propagate throughout AWS. Until the rules have propagated, the platform will not be able to detect them. See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/query-api-troubleshooting.html#eventual-consistency

To add a new firewall rule:

  1. Select the virtual datacenter or location

  2. Select the firewall

  3. On the Firewall rules panel, click the pencil Edit button

  4. Select the Inbound or Outbound tab for the traffic direction you wish to control

  5. Enter the details of a rule

    1. Protocol

      • Select from Common protocols, OR

      • Select and enter a Custom protocol

    2. Port range with the Start port and End port that this rule will apply to.
      To enter one port, enter the same value twice, or optionally apply the rule to a number of ports at the same time. 
      For Azure and GCP, you can enter:

      1. a single port, such as 80

      2. a range, such as 1024-65535

      3. a list of port/range, such as 80,1024-65535

    3. Sources or Targets as a network address and netmask, or a comma separated list of these (with no spaces)

  6. Click Add. The firewall rule will be added to the Firewall rules list

  7. Enter more rules as required, then click Save

Edit the rules for a firewall policy to add allowed protocols and ports

3.6. Move firewall policies

Unable to render {include} The included page could not be found.

3.7. Delete a firewall policy

Unable to render {include} The included page could not be found.


4. Manage load balancers

Unable to render {include} The included page could not be found.


4.1. Display load balancers

Unable to render {include} The included page could not be found.

4.2. Create load balancers

Unable to render {include} The included page could not be found.

4.3. Edit load balancers

Unable to render {include} The included page could not be found.


5. Manage VPNs

Unable to render {include} The included page could not be found.

  • No labels