Tag not monitored by Microsoft.
Apologies for the delayed response. Since you are using a Marketplace product provided by Juniper Networks I recommend reaching out to them for support.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I'm building vSRX on Azure. If the following error log appears in the log when starting the machine, the ARP information of the opposite address cannot be confirmed. Therefore, communication with the outside world is not possible. Please let me know what is the cause and if there is a solution.
mlx5_core0: ERR: mlx5_init_once:942:(pid 0): Unable to find vendor specific capabilities
hn1: <Hyper-V Network Interface> on vmbus0
tcp_lro_init_args not implemented
tcp_lro_init_args not implemented
tcp_lro_init_args not implemented
tcp_lro_init_args not implemented
if_sethwtsomax ** NOT IMPLEMENTED **if_sethwtsomaxsegcount ** NOT IMPLEMENTED **if_sethwtsomaxsegsize ** NOT IMPLEMENTED **mlx5_core0: WARN: mlx5_fwdump_prep:76:(pid 0): Failed to find vendor-specific capability, error 2
By repeatedly starting and stopping the machine, you can successfully check the ARP information of the opposite address. The addresses I see in the ARP information are those reserved by Azure for the default gateway within the virtual network's subnet.
Tag not monitored by Microsoft.
Apologies for the delayed response. Since you are using a Marketplace product provided by Juniper Networks I recommend reaching out to them for support.