The problem that routeros cannot access the gateway by ping in ESX environment
Routeros has been built in the esx environment, has been running normally, due to changes in the environment, made a host and storage migration, and then routeros can not get through, after logging in through the console can not ping the gateway, ping's own IP is not accessible, delete the network card and add a new network card, you can ping your own ip, or ping does not get through the gateway for a long time, and finally determined that it is the mac address problem Use the interface ethernet reset-mac-address ether1 command to restore the mac of each network card and it will be normal.
The reason is roughly that after the change of the virtualized environment, the mac address has changed, resulting in abnormal network communication.