When you create an interface, it is configured as either IPv4 or IPv6. The next step is to set up the interface addressing using either dynamic and/or static IP addresses.

Some Monitoring Point models (m22, m30, r40 and r400) support configuring either DHCP or a single static IP address on an interface. These Monitoring Points only support IPv4 addressing.

The other models support configuring DHCP and/or multiple static IP addresses on an interface. For these, up to 128 IP addresses can be configured on an interface and at least one is required (either static or DHCP). Both IPv4 and IPv6 addresses are supported in these cases. Multiple static IP addresses are supported on Physical (Ethernet), VLAN, and Wireless interface types.

For Monitoring Points that support IPv6, it is possible to configure multiple IPv6 addresses. However, policy routing for IPv6 is not supported at this time.

Potential loss of connectivity: Care must be taken when changing the IP address configuration on the primary network connection. If the new address is in a different subnet than the old one, you will lose network connectivity to the Monitoring Point after restarting networking.

View addressing

Web admin

  1. Log in to Web Admin.
  2. Navigate to Network Settings > Network Interfaces.
  3. For the interface you want to view, the Active column contains the addressing information.

Admin API

  1. Log in to Admin API.
  2. Navigate to Interface > GET /interface/{interface_name}/.
  3. In the Parameters section, specify the interface_name you are interested in.
  4. Click Submit.
    • The Response Body section shows the interface configuration including.
      • iftype - interface type (e.g., ethernet).
      • name - interface name (e.g., eth0).
      • family - “inet” indicates IPv4, “inet6” indicates IPv6.
      • method - “static” indicates static IP addresses, “dchp” indicates DHCP and Stateless and Stateful DHCPv6 (IPv6), “auto” indicates SLAAC (IPv6).
      • address - the list of static addresses configured on the interface.
      • dhcp_address - IP address provided by DHCP.
      • dhcp_netmask - the netmask provided by DHCP.
      • dhcp_gateway - the gateway address provided by DHCP.

curl

  1. In APM, navigate to > Manage Monitoring Points.
  2. Click the Monitoring Point you want to connect to.
    • The Name field contains the hostname.
    • The Local Network Interface field in the right pane contains the IP address.
      • Use the Public IP if you are connecting across the Internet.
  3. View the interface configuration using:

    curl -k -u <username> -X GET -H 'Accept: application/json' 'https://<hostname>/api/v1/interface/<interface_name>/?config_state=active' | python -m json.tool
    

The variables above are defined as follows:

  • <username> - the user name on the Monitoring Point.
  • <hostname> - the hostname or IP address of the Monitoring Point.
  • <interface_name> - the interface you are interested in.

The response shows the interface configuration including:

  • iftype - interface type (e.g., ethernet).
  • name - interface name (e.g., eth0).
  • family - “inet” indicates IPv4, “inet6” indicates IPv6.
  • method - “static” indicates static IP addresses, “dchp” indicates DHCP and Stateless and Stateful DHCPv6 (IPv6), “auto” indicates SLAAC (IPv6).
  • address - the list of static addresses configured on the interface.
  • dhcp_address - IP address provided by DHCP.
  • dhcp_netmask - the netmask provided by DHCP.
  • dhcp_gateway - the gateway address provided by DHCP.

Web admin

  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. The Address Source field shows the interface address.

Add addressing

At least one IP address (either static or dynamic) must be configured on an interface. Some Monitoring Points allow you to configure additional addresses.

Web admin

  1. Log in to Web Admin.
  2. Navigate to Network Settings > Network Interfaces.
  3. For the interface you want to add an address to, select > Edit.
  4. To add a dynamic address, in the Dynamic Address field, select one of the options.
    • The selection is added to the Interface Addresses field.
  5. To add a static address, in the Static Address field, specify the Address, Netmask, and Gateway you want to add and click .
    • The address is added to the Interface Addresses field.
  6. Repeat the previous step for all the static addresses you want to add.
  7. Click Submit.
    • The address(es) specified are added to the interface but the change does not take effect until networking is restarted.
  8. Restart networking.
    • The changes are applied to the interface.

Admin API

  1. Log in to Admin API.
  2. Determine which interfaces are available.
    1. Navigate to Interface > GET /interface/ and click Submit.
      • The Response Body section shows the configured interfaces.
  3. Configure an additional IP address on an interface.
    1. Navigate to Interface > POST /interface/{interface_name}/address/.
    2. In the Parameters section:
      1. Set interface_name to the name of the interface you are configuring (e.g., eth0).
      2. Set family as appropriate. “inet” for IPv4, and “inet6” for IPv6.
    3. In the body section, click the Model Schema on the right.
      • The text is copied to the body field.
    4. Edit the text in the body field as follows:
      1. Change “string” in "address": "string" to the IP address you are adding to the interface. Either an IPv4 or an IPv6 address can be specified (depending on how family is set).
      2. Change “string” in "netmask": "string" to the netmask of the IP address you are adding. For IPv4, use either a prefix (e.g., 24) or a dotted decimal mask (e.g., 255.255.255.0). For IPv6, use a prefix (e.g., 64).
      3. Change “string” in "gateway": "string" to the IP address of the gateway the Monitoring Point uses to access the Internet for the configured address. Alternatively, remove the comma after "netmask": "<netmask>" as well as "gateway": "<gateway>" to use the default gateway configured on the interface.
    5. Click Submit.
      • In the Response Body section, look for "success": true to confirm that the address was added successfully.
  4. Repeat the steps from 3 above for all the addresses you want to add.
  5. Restart networking to apply the changes.
    1. Navigate to Service > PUT /service/{service_name}/.
    2. In the Parameters section:
      1. Set service_name to “networking”.
      2. Set action to “restart”.
      3. Click Submit.
        • You will briefly lose connectivity to the Admin API.
  6. Verify that the new address exists on the interface.
    1. Navigate to Interface > GET /interface/{interface_name}/address/.
    2. In the Parameters section:
      1. Set interface_name to the name of the interface you configured.
      2. Set config_state to “active”.
      3. Set family as appropriate. “inet” for IPv4, and “inet6” for IPv6.
      4. Click Submit.
        • The Response Body section shows the addresses configured on the interface.

curl

  1. In APM, navigate to > Manage Monitoring Points.
  2. Find the hostname of your Monitoring Point in the Name column of the table.
  3. Determine which interfaces are available.

    curl -k -u <username> -X GET -H 'Accept: application/json' 'https://<hostname>/api/v1/interface/?config_state=active' | python -m json.tool
    
  4. Configure an additional IP address on an interface.

    curl -k -u <username> -X POST -H 'Content-Type: application/json' -H 'Accept: application/json' -d '{"address": "<address>", "netmask": "<netmask>", "gateway": "<gateway>"}' 'https://<hostname>/api/v1/interface/<interface_name>/address/?family=<addr_type>' | python -m json.tool
    
    • gateway is optional. Remove the comma after "netmask": "<netmask>" if you omit "gateway": "<gateway>".
  5. Restart networking to apply the changes.

    curl -k -u <username> -X PUT -H 'Content-Type: application/json' -d {} 'https://<hostname>/api/v1/service/networking/?action=restart' | python -m json.tool
    
    • You will briefly lose connectivity to the Admin API.
  6. Verify that the new address exists on the interface.

    curl -k -u <username> -X GET 'https://<hostname>/api/v1/interface/<interface_name>/?config_state=active' | python -m json.tool
    

The variables above are defined as follows:

  • <username> - the user name on the Monitoring Point.
  • <address> - the IP address you are adding to the interface. Either an IPv4 or an IPv6 address can be specified.
  • <addr_type> - the type of IP address. Use “inet” for IPv4 and “inet6” for IPv6 addresses.
  • <gateway> - (optional) the IP address of the gateway the Monitoring Point uses to access the Internet for the configured address. If not specified, the default gateway configured on the interface is used.
  • <hostname> - the hostname or IP address of the Monitoring Point.
  • <interface_name> - the name of the interface you are configuring.
  • <netmask> - the netmask of the IP address you are adding. For IPv4, use either a prefix (e.g., 24) or a dotted decimal mask (e.g., 255.255.255.0). For IPv6, use a prefix (e.g., 64).

USB

To add an IP address to an interface:

  1. Download the additional static IP addresses config file.
  2. The downloaded file contains the following editable fields:
    • <interface> - the interface you are configuring (e.g., eth0).
    • <inet for ipv4 or inet6 for ipv6> - the address family you are using. Use inet for IPv4 and inet6 for IPv6.
    • <address> - the IP address you are adding to the interface. Either an IPv4 or an IPv6 address can be specified.
    • <netmask> - the netmask of the IP address you are adding. For IPv4, use either a prefix (e.g., 24) or a dotted decimal mask (e.g., 255.255.255.0). For IPv6, use a prefix (e.g., 64).
    • <gateway> - (optional) the IP address of the gateway the Monitoring Point uses to access the Internet for the configured address. If not specified, the default gateway configured on the interface is used.
    • Repeat address, netmask, and gateway as a group for each additional address to be configured.
  3. Edit the downloaded config file for your needs.
    • Uncomment sections to be used (if required).
    • Replace content in arrow brackets (no arrow brackets should remain).
  4. Copy the file onto a USB stick.
  5. Make sure the Monitoring Point is ready.
  6. Insert the USB stick into the Monitoring Point.
    • The Monitoring Point reads the configuration from the USB stick and indicates that it is doing so.
  7. Wait until the Monitoring Point is finished.
  8. Remove the USB stick.
    • The Monitoring Point configuration is updated.
    • Any problems updating the configuration are logged in the usb.log file on the USB stick.
  9. Verify that the interface acquired an IP address.
    1. In APM, navigate to > Manage Monitoring Points.
    2. Select the Monitoring Point you are interested in.
    3. On the right side panel, check Local Network Interfaces for an IP address on the interface.

Web admin

  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. For DHCP, in the Address Source field, select From DHCP.
  5. For a static IP address, in the Address Source field, select Static configuration.
    • In the IP Address field, add the static IP address (e.g., 192.168.1.1).
    • In the Netmask field, add the netmask (e.g., 255.255.255.0).
  6. Click Save.
  7. Click Restart Networking.

Edit addressing

Web admin

  1. Log in to Web Admin.
  2. Navigate to Network Settings > Network Interfaces.
  3. For the interface you want to edit, select > Edit.
  4. To edit dynamic addressing, in the Dynamic Address field, select the type of dynamic addressing to use (e.g., DHCP) or select None to disable dynamic addressing.
  5. To edit static addresses, in the Interface Addresses field, edit the static IP address configuration and click .
  6. Click Submit.
    • The address is changed but the change does not take effect until networking is restarted.
  7. Restart networking.
    • The changes are applied to the interface.

Admin API

To edit addressing on an interface you need to delete an address then add a different one.

Web admin

  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. In the Address Source field, edit the IP Address and Netmask fields as appropriate.
  5. Click Save.
  6. Click Restart Networking.

Delete addressing

Web admin

  1. Log in to Web Admin.
  2. Navigate to Network Settings > Network Interfaces.
  3. For the interface you want to edit, select > Edit.
  4. In the Interface Address field, click next to the address you want to delete.
    • The address is deleted from the Interface Addresses section.
  5. Repeat the previous step for all the addresses you want to delete.
  6. Click Submit.
    • The address(es) specified are removed from the interface but the change does not take effect until networking is restarted.
  7. Restart networking.
    • The changes are applied to the interface.

Admin API

  1. Log in to Admin API.
  2. Determine which addresses are configured on the interface.
    1. Navigate to Interface > GET /interface/{interface_name}
    2. In the Parameters section:
      1. Set interface_name to the interface you are configuring (e.g., eth0).
      2. Click Submit.
        • The Response Body section shows the interface configuration, including static IP addresses.
  3. Delete an IP address from the interface.
    1. Navigate to Interface > DELETE /interface/{interface_name}/address/.
    2. In the Parameters section:
      1. Set interface_name to the interface you are configuring (e.g., eth0).
      2. In the body section, click the Model Schema on the right.
        • The text is copied to the body field.
      3. Change “string” in "address": "string" to the address you are deleting.
      4. Click Submit.
        • In the Response Body section, look for "success": true to confirm that the address was deleted successfully.
  4. Restart networking to apply the changes.
    1. Navigate to Service > PUT /service/{service_name}/.
    2. In the Parameters section:
      1. Set service_name to “networking”.
      2. Set action to “restart”.
      3. Click Submit.
        • You will briefly lose connectivity to the Admin API.
  5. Verify that the address was removed from the interface.
    1. Navigate to Interface > GET /interface/{interface_name}/address/.
    2. In the Parameters section:
      1. Set interface_name to the name of the interface you configured.
      2. Set config_state to “active”.
      3. Set family as appropriate. “inet” for IPv4, and “inet6” for IPv6.
      4. Click Submit.
        • The Response Body section shows the addresses configured on the interface.

curl

  1. In APM, navigate to > Manage Monitoring Points.
  2. Find the hostname of your Monitoring Point in the Name column of the table.
  3. Determine which addresses are configured on the interface.

    curl -k -u <username> -X GET 'https://<hostname>/api/v1/interface/<interface_name>/?config_state=active' | python -m json.tool
    
  4. Delete an IP address from the interface.

    curl -k -u <username> -X DELETE -H 'Content-Type: application/json' -H 'Accept: application/json' -d '{"address": "<address>"}' 'https://<hostname>/api/v1/interface/<interface_name>/address/' | python -m json.tool
    
    • You cannot delete the last address on an interface unless dynamic addressing (e.g., DHCP) is also configured.
  5. Restart networking to apply the changes.

    curl -k -u <username> -X PUT -H 'Content-Type: application/json' -d {} 'https://<hostname>/api/v1/service/networking/?action=restart' | python -m json.tool
    
    • You will briefly lose connectivity to the Admin API.
  6. Verify that the address was removed from the interface.

    curl -k -u <username> -X GET 'https://<hostname>/api/v1/interface/<interface_name>/?config_state=active' | python -m json.tool
    

The variables above are defined as follows:

  • <username> - the user name on the Monitoring Point.
  • <address> - the IP address you are deleting from the interface. Either an IPv4 or an IPv6 address can be specified.
  • <hostname> - the hostname or IP address of the Monitoring Point.
  • <interface_name> - the name of the interface you are configuring.

Web admin

  1. Log in to Web Admin
  2. Click Network Configuration.
  3. Click on the interface you are interested in.
  4. In the Address Source field, select From DHCP.
    • The interface address and netmask will be obtained from DHCP.
  5. Click Save.
  6. Click Restart Networking.

Legacy IPv6 support

For Monitoring Points that support it and that have software older than EMP 12.6.0, IPv6 is enabled and disabled globally on the Monitoring Point. Once it is enabled, interfaces can be configured with IPv6.

Enable IPv6 on a Monitoring Point

Admin API

  1. Complete Monitoring Point setup.
  2. Access the Admin API.
  3. Navigate to Appliance > PUT /appliance/.
  4. In the Parameters section, in the IPv6 field, select enable.
  5. Click Submit.
    • The Response Code section should show “200”.
  6. Restart the Monitoring Point.
    • IPv6 is enabled on the Monitoring Point.

curl

  1. Complete Monitoring Point setup setup.
  2. Discover your Monitoring Point hostname at > Manage Monitoring Points.
  3. Enable IPv6.

    curl -k -u <username> -X PUT -H 'Content-Type: application/json' -d '{}' 'https://<hostname>/api/v1/appliance/?ipv6=enable' | python -m json.tool
    
  4. Restart networking to apply the changes.

    curl -k -u <username> -X PUT -H 'Content-Type: application/json' -d {} 'https://<hostname>/api/v1/service/networking/?action=restart' | python -m json.tool
    
    • You will briefly lose connectivity to the Admin API.

The variables above are defined as follows:

  • <username> - the user name on the Monitoring Point.
  • <hostname> - the hostname or IP address of the Monitoring Point.

Disable IPv6 on a Monitoring Point

Admin API

  1. Access the Admin API.
  2. Navigate to Appliance > PUT /appliance/.
  3. In the Parameters section, in the IPv6 field, select disable.
  4. Click Submit.
    • The Response Code section should show “200”.
  5. Restart the Monitoring Point.
    • IPv6 is disabled on the Monitoring Point.

curl

  1. Discover your Monitoring Point hostname at > Manage Monitoring Points.
  2. Disable IPv6.

    curl -k -u <username> -X PUT -H 'Content-Type: application/json' -d '{}' 'https://<hostname>/api/v1/appliance/?ipv6=disable' | python -m json.tool
    
  3. Restart networking to apply the changes.

    curl -k -u <username> -X PUT -H 'Content-Type: application/json' -d {} 'https://<hostname>/api/v1/service/networking/?action=restart' | python -m json.tool
    
    • You will briefly lose connectivity.

The variables above are defined as follows:

  • <username> - the user name on the Monitoring Point.
  • <hostname> - the hostname or IP address of the Monitoring Point.