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:
Edgeto ping from a single testman host to a single destinationGatewayto ping from multiple testman hosts to the gateway IP addressEdgeMeshto 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:
interfaceResourcevlanIDdestination
Example
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
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
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#
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
SPEC
EdgePingSpec defines the desired state of EdgePing
-
Number of ping packets to send.
default: 1format: int32range: 1 to 10 -
Destination address to ping.
-
Interface that sends the ping packet(s).
-
The type of ping to perform.
enum: "Gateway", "EdgeMesh", "Edge" -
Virtual network resource to perform the ping in.
-
Source VLAN ID of the ping packet(s).
format: int32range: 0 to 4094
STATUS
EdgePingStatus defines the observed state of EdgePing
-
Aggregate result of the Flow