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

Version 1 Next »

The IP Interface Settings page lists information about network interfaces configured for the host. Depending on your host deployment, you may or may not be able to modify information on this page.

BloxOne supports interface modifications for the following deployments: BloxOne VMBloxOne Appliance, and BloxOne Container. If you have multiple network interfaces configured for the host, you can enable or disable them as well as set routing priorities by configuring routing metrics. You can also modify the network configuration for physical appliances or virtual appliances that were deployed through OVA deployments using the downloaded Infoblox image. If you have configured multiple network interfaces on your Kubernetes-based hosts, all the Ethernet ports are displayed in this section. For information about using multiple interfaces, see Multiple Network Interfaces for Hosts.
You can configure IPv4-only or IPv4/IPv6 dual-stack networks for a host. However, IPv4/IPv6 dual-stack networks are not supported if you plan to enable DNS or DHCP services on the host.

On the IP Interface Settings page of the Edit <Host> wizard, you can view or update IP interface settings, as follows :

  1. Select the check box of the network interface from the list, and then click Edit.

  2. In the Edit IP Interface Settings section, complete the following:

  • Network Interface: Displays the name of the Ethernet ports on the appliance, such as enp1s0 or enp2s0. All network interfaces you have configured appear in the table. You cannot modify this field. You can configure up to two network interfaces for the same network gateway.

  • Interface Type: Displays whether the network interface is WAN or LAN based on your deployment. You may or may not be able to change the interface type. When your hosts have multiple interfaces, the lowest metric interface will be marked as WAN and the rest of the interfaces will be marked as LAN.

  • IPv4 MTU: Enter the maximum transmission unit for the IPv4 network, which is the size of the largest protocol data unit that can be communicated in a single network layer transaction. Valid values are from 576 to 9001. The default value is 1500.
    If you are configurating a dual-stack network for the host, the minimum MTU value for the IPv4 address must be set to 1280. Otherwise, the IPv6 address will not be functional.

  • IPv4 Network Mode: Displays whether the IPv4 interface is being configured for DHCP or Static. When configured for DHCP, the IP address is dynamically assigned, so you cannot modify the IP address associated with the interface. When configured as Static, you must assign a valid IPv4 address for the interface.

  • Gateway: Displays the gateway for the interface. Each IPv4 gateway supports up to two network interfaces. If you configure more than two network interfaces for the same gateway, the gateway address will not be displayed for those interfaces.

  • IPv4 CIDR: The IPv4 address and netmask.

  • IPv4 Metric: A metric is a value that you assign to an IP route for a particular interface for routing purposes. Valid IPv4 metric values are from 0 to 4294967294. The default value is 0. 
    The metric value is used by BloxOne to determine which interface should be used for cloud communication. The metric value is important if you have multiple network interfaces configured with the gateway. The lower the metric value, the higher the priority the interface has in the IP routing table. For example, when you set the metric value at 0 for one interface and 20 for another, the interface with metric value 0 has a higher priority than the one with metric value 20, and it will become the primary interface to be used for cloud traffic through the configured gateway. If the primary interface (the one with a lower metric value) is down, the traffic will go through the next prioritized interface. If you configure the same metric value for two interfaces, the system will decide and take the best route to the destination (the one with less hops) via the associated interface. If the number of hops is the same for both paths, the traffic will be load-balanced between the two associated interfaces.

  • IPv6 MTU: Enter the maximum transmission unit for the IPv6 network, which is the size of the largest protocol data unit that can be communicated in a single network layer transaction. Valid values are from 1280 to 9001. The default value is 1500. This value must be greater than or equal to the IPv4 MTU value.
    If you are configurating a dual-stack network for the host, the minimum MTU value for the IPv4 address must be set to 1280. Otherwise, the IPv6 address will not be functional. In addition, the IPv6 MTU must be greater than or equal to the IPv4 MTU.

  • IPV6 Network Mode: If configured, displays whether the IPv6 interface is being configured as DHCP, RA, Auto Select, or Static.

    • DHCP: When configured for DHCP, the IP address is dynamically assigned by the DHCP server, so you cannot modify the IP address associated with the interface.

    • RA: When configured as router advertisements, the host in your IPv6 network auto-generated a link-local address to communicate with other hosts or neighbors on the same network.

    • Auto Select: When configured as Auto Select, the system selected the best way to obtain an IPv6 address for the host.

    • Static: When configured as Static, you have manually assigned a valid IPv6 address, CIDR, and gateway for the host.

  • Gateway: The default gateway for the IPv6 interface.

  • IPv6 CIDR: The IPv6 address and CIDR associated with the interface.

  • IPv6 Metric: A metric is a value that you assign to an IP route for a particular interface for routing purposes. Valid metric values are from 0 to 4294967294. The default value is 1024.
    The metric value is used by BloxOne to determine which interface should be used for cloud communication. The metric value is important if you have multiple network interfaces configured with a gateway. The lower the metric value, the higher the priority the interface has in the IP routing table. For example, when you set the metric value at 0 for one interface and 20 for another, the interface with metric value 0 has a higher priority than the one with metric value 20, and it will become the primary interface to be used for cloud traffic through the configured gateway. If the primary interface (the one with a lower metric value) is down, the traffic will go through the next prioritized interface. If you configure the same metric value for two interfaces, the system will decide and take the best route to the destination (the one with less hops) via the associated interface. If the number of hops is the same for both paths, the traffic will be load-balanced between the two associated interfaces.

  • Interface State: Indicates whether the admin state of the configured network interface is administratively Enabled or Disabled. All network interfaces, except the one with the lowest metric value, are Disabled by default. To use a specific interface, you must first toggle the state to Enabled (green). When the network interface is disabled, it will not be in use, but the configuration stays intact.

Click Save to save your configuration, or click Cancel to discard your changes.

  • Enable Service Traffic: Displays whether the BloxOne service is enabled on all IP interfaces or only on LAN.

    • On all IP Interfaces: This indicates that BloxOne services are enabled on all IP interfaces for this host.

    • LAN: This indicates the BloxOne services are enabled only on LAN for this host.

Click Next to go to the DNS Local Resolver Settings page. You can also click Cancel to cancel the configuration or click Finish to save the configuration.

  • No labels