FAQ: Virtual Appliance PHY Errors in System Log

This article applies to Sentry virtual appliances running on VMware products (e.g. ESX or VMware Workstation). The following warning level errors may be found in the System log upon booting of the ForumOS:

W Cannot set 'WAN' interface to Auto-Negotiate : SIOCGMIIPHY on 'eth1' failed: Operation not supported

W Cannot set 'LAN' interface to Auto-Negotiate : SIOCGMIIPHY on 'eth2' failed: Operation not supported

W Cannot set 'MGMT' interface to Auto-Negotiate : SIOCGMIIPHY on 'eth0' failed: Operation not supported

 

These errors are related to the ForumOS CLI "network config phy" setting which allows for configuring the link speed and duplex for the 3 network interfaces in Sentry (MGMT, WAN, and LAN).  The system defaults to "Auto-Negotiate" for all 3 interfaces and this can cause issues with the underlying network settings within the VMware technology.

Typically these error messages can be safely ignored.  There are no known issues that result from these warnings in the system log. However, if there are consistent networking issues believed to be related to the phy setting in the CLI, administrators should try the following VMware modification to resolve the problem.

Possible Solution

Modifications to the virtual machine VMX file have been shown to remove these errors from the Sentry logs when testing with VMware Workstation v10.0.2. 

IMPORTANT: These are changes to the host VMware product, not Forum Sentry, and any additional questions or issues related to these settings should be directed to VMware Support.

1. Export the existing Sentry configuration file (.FSX) on the System>>Configuration>>Import/Export page of the Sentry WebAdmin interface.

2. Make note of the existing network settings for this Sentry instance. Use the CLI commands "show interfaces", "show routes", and "show static-hosts".

3. Shutdown the VM - use the ForumOS CLI command "shutdown".

4. Locate the "virtual_appliance_name".vmx file and make a backup copy of it.

5. Edit the vmx file making changes to any "ethernet#.virtualDev=" line, where # is typically 0, 1, 2, or 3, changing the value "vlance" to the value "e1000".  There will be multiple occurrences of this line and some may already have the value "e1000".

Examples:

change: ethernet1.virtualDev = "vlance"

to: ethernet1.virtualDev = "e1000"

change: ethernet2.virtualDev = "vlance"

to: ethernet2.virtualDev = "e1000"

change: ethernet3.virtualDev = "vlance"

to: ethernet3.virtualDev = "e1000"

 6. Save the vmx file.

 7.  Start the virtual machine; check the System log for the errors.

 8.  Ensure all previous network connectivity remains.

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.