how to determine cluster network mac address

The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category 'Performance'. This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category 'Other.

The cookies is used to store the user consent for the cookies in the category 'Necessary'. The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category 'Functional'. The cookie is used to store the user consent for the cookies in the category 'Analytics'.

These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. Show network device info and take note of the MAC address. Login via console with user admin and select option 3. If you have dynamic MAC on you Libra Esva and if you already experienced the problem the solution is to read the old MAC address from Esva console and force Hyper-v to use this. You can configure the MAC address by editing the settings of the virtual machine in Hyper-V Manager or Failover Cluster Manager. To avoid losing the network configuration, ensure that each virtual network adapter has a static MAC address.

In Libra Esva (and all other linux kernel based VM) the networking configuration may be lost after failover because a new MAC address is assigned by Hyper-v to the virtual network adapter. Libra Esva Virtual Appliances that will be deployed using failover clustering should be configured with a static media access control (MAC) address for each virtual network adapter. Use static MAC addresses with failover clustering! Libra Esva network is unreachable after a Microsoft Hyper-V failover.

How to determine cluster network mac address