Add dynamic IPv4 addresses to Single Engine interfaces

You can configure dynamic IPv4 addresses for physical, VLAN, and port group interfaces on Single Engines.

Note: Dynamic IP addresses are not supported on Aggregated Link interfaces.

You can identify interfaces that have a dynamic IPv4 address using a DHCP Index. A modem interface always has a dynamic IP address.

For more details about the product and how to configure features, click Help or press F1.

Steps

  1. In the navigation pane on the left, browse to Interfaces.
  2. Right-click a physical, VLAN, or port group interface, then select New > IPv4 Address.
  3. Select Dynamic as the type of IP address.
  4. From the Dynamic Index drop-down list, select a DHCP index.
    The index is used for identification in other parts of the configuration (such as Engine Policies) to represent the possibly changing IP address.
  5. If the interface is used for system communications and NAT is applied, add contact addresses.
    1. If the default contact address is not dynamic, deselect Dynamic, then enter the static contact address.
    2. If components from some locations must use a different IP address for contact, click Exceptions, then define the location-specific addresses.
  6. If the interface’s dynamic IP address is assigned through point-to-point protocol, configure the settings.
    PPPoE can be used with physical, or VLAN interfaces.
    1. Click PPP Settings.
    2. From the Mode drop-down list, select PPPoE.
    3. Fill in the User Name, Password, and (optional) Service Name fields according to the details provided by your service provider.
      If you do not have these details, contact your service provider. By default, passwords and keys are not shown in plain text. To show the password or key, deselect the Hide option.
    4. Click OK.
  7. Click OK.
    The dynamic IPv4 address is added to the interface.
  8. Click Save.
    Do not close the Engine Editor.

Next steps

Continue the configuration in one of the following ways:
  • Add more IP addresses.
  • Add other types of interfaces.
  • Select system communication roles for interfaces.
  • Bind engine licenses to the Single Engine elements.