This section describes the steps to resolve the issue of virtual service not responding to ICMP or any other access method despite being shown healthy in Avi Load Balancer user interface.

Resolution

Identify the issue using the following steps:

  1. Find the SE in which virtual service has been placed.

  2. Check the interface list for the SE. To learn the MAC address of the SE interface,

    1. Navigate to Infrastructure > Service Engine.

    2. Click the edit icon.

    3. Find the interface MAC for the virtual service.

  3. Login to the OpenStack neutron-server. Type the command neutron port-list, along with the grep option for the MAC address. In the below example, the grep command is used to filter the neutron port-list having MAC address ending with 63:f2.

    root@avi-mitaka2:~# neutron port-list | grep 63:f2
12a2992f-caf0-4f7d-aed9-c9964fd2918a	Avi-Data:cluster-005056b04388:cloud-29b82860-0bae-4a9b-ae34-54d955f0cba4	fa:16:3e:34:63:f2	{"subnet_id": "5876f319-9dd8-4173-9bea-ad40656d26dc", "ip_address": "10.0.1.54"}

  4. Use the neutron port-show command for the port ID (12a2992f-caf0-4f7d-aed9-c9964fd2918a).

    neutron port-show port-id is the complete syntax.

  5. Check if Allowed Address Pairs (AAP) is enabled for the specific virtual IP. Value for the flag admin_state_up will return True if AAP is enabled.

    root@avi-mitaka2:~# neutron port-show 12a2992f-caf0-4f7d-aed9-c9964fd2918a
-------------------------------------------------------------------------------------------------------+
Field	Value
-------------------------------------------------------------------------------------------------------+
admin_state_up	True
| allowed_address_pairs | {"ip_address": "10.0.1.49", "mac_address": "fa:16:3e:34:63:f2"} |

To know more about AAP, see OpenStack Cloud Advanced Configuration Options.

Note:

This resolution is applicable only if AAP is used in virtual service configuration in the OpenStack cloud.