Skip to content

Edge Ping#

Workflows → EPEdge Pings

The EdgePing workflow is used to test service connectivity in a fully virtualized setup with testman SimNode containers.

Warning

This workflow cannot be used in a hardware setup, nor is it capable of sending a ping from a network switch to a host. It can only be used to ping an IP from a testman SimNode container.

Ping test types#

This workflow supports three connectivity tests:

  • Edge to ping from a single testman host to a single destination
  • Gateway to ping from multiple testman hosts to the gateway IP address
  • EdgeMesh to ping between multiple testman hosts

Edge#

This sends ping packets to a single destination, from a single source host.

The number of ping messages being sent is count * 1. The following parameters must be specified:

  • interfaceResource
  • vlanID
  • destination
Example
apiVersion: services.eda.nokia.com/v2
kind: EdgePing
metadata:
    name: edgeping-72d9e649-1758-4224-a073-e519f5265433
    namespace: eda
spec:
    count: 3
    pingType: Edge
    interfaceResource: leaf-2-ethernet-1-2-1
    vlanID: 100
    destination: 10.0.0.8

Gateway#

This sends ping packets from all hosts associated with a VLAN or RoutedInterface in a particular VirtualNetwork. The destination IP of the packets is the IRBInterface gateway IP of the BridgeDomain associated with the VLAN, or the RoutedInterface IP address.

The number of ping messages is count * num_hosts, where num_hosts is the number of sub-interfaces created by the VirtualNetwork. The following parameters must be specified:

  • virtualNetwork
Example
apiVersion: services.eda.nokia.com/v2
kind: EdgePing
metadata:
    name: edgeping-f63dc46a-2b02-4fea-a9ba-e712bb0992e9
    namespace: eda
spec:
    count: 3
    pingType: Gateway
    virtualNetwork: my-vnet

EdgeMesh#

This sends ping packets between all hosts associated with a VLAN or RoutedInterface in a particular VirtualNetwork.

The number of ping messages is count * num_hosts * (num_hosts - 1) / 2, where num_hosts is the number of sub-interfaces created by the VirtualNetwork. The following parameters must be specified:

  • virtualNetwork
Example
apiVersion: services.eda.nokia.com/v2
kind: EdgePing
metadata:
    name: edgeping-147762ba-798d-4ef5-8c6a-8aace9cada04
    namespace: eda
spec:
    count: 3
    pingType: EdgeMesh
    virtualNetwork: my-vnet

IP address assignment#

When a VLAN or RoutedInterface is created, an EdgeInterface is created for every sub-interface. If the interface is connected to a testman SimNode, an IP address is configured with the relevant VLAN ID on that simulated node. This IP address is taken from a pool that matches the IRBInterface or RoutedInterface.

If no IRBInterface was found for the BridgeDomain that the VLAN is connected to, the following default pools are used to assign IP addresses:

  • IPv4: 10.0.0.0/16
  • IPv6: fd12:3456:789a:0001:0000::/112

Dependencies#

VirtualNetwork#

If the type of this ping is EdgeMesh or Gateway, the virtualNetwork property selects the VirtualNetwork resource to find sub-interfaces attached to testman hosts.

Interface#

If the type of this ping is Edge, the interfaceResource property in combination with the vlanID selects the sub-interface attached to a testman host.

Referenced resources#

No other resources are referenced by the EdgePing workflow.

Examples#

apiVersion: services.eda.nokia.com/v2
kind: EdgePing
metadata:
    name: edgeping-2607fb76-1b1b-4773-bf30-0305d5f4902d
    namespace: eda
spec:
  count: 9
  destination: 10.0.0.21
  interfaceResource: leaf-2-ethernet-1-2-1
  pingType: Edge
  vlanID: 100
cat << 'EOF' | kubectl apply -f -
apiVersion: services.eda.nokia.com/v2
kind: EdgePing
metadata:
    name: edgeping-2607fb76-1b1b-4773-bf30-0305d5f4902d
    namespace: eda
spec:
  count: 9
  destination: 10.0.0.21
  interfaceResource: leaf-2-ethernet-1-2-1
  pingType: Edge
  vlanID: 100
EOF
Example execution
apiVersion: services.eda.nokia.com/v2
kind: EdgePing
metadata:
  annotations:
    workflows.core.eda.nokia.com/id: '422'
    workflows.core.eda.nokia.com/root-workflow-group: services.eda.nokia.com
    workflows.core.eda.nokia.com/root-workflow-kind: EdgePing
    workflows.core.eda.nokia.com/root-workflow-name: edgeping-2607fb76-1b1b-4773-bf30-0305d5f4902d
    workflows.core.eda.nokia.com/root-workflow-namespace: eda
    workflows.core.eda.nokia.com/root-workflow-version: v2
    workflows.core.eda.nokia.com/state: Completed
    workflows.core.eda.nokia.com/username: admin
  name: edgeping-2607fb76-1b1b-4773-bf30-0305d5f4902d
  namespace: eda
spec:
  count: 9
  destination: 10.0.0.21
  interfaceResource: leaf-2-ethernet-1-2-1
  pingType: Edge
  vlanID: 100
status:
  result: >-
    Ping successful, 9 packets transmitted, 9 received:
    leaf-2-ethernet-1-2-1:100 -> 10.0.0.21
workflowStatus:
  stages:
    - name: Initializing
      state: Completed
    - name: pinging from testman
      state: Completed
  state: Completed

Custom Resource Definition#

To browse the Custom Resource Definition go to crd.eda.dev.

EdgePing

services.eda.nokia.com / v2

SPEC

EdgePingSpec defines the desired state of EdgePing

  • #
  • #
  • #
  • #
  • #
  • #

STATUS

EdgePingStatus defines the observed state of EdgePing

  • #