OSMS Agent Service Fails to Start on Instances with more than one VNIC (Doc ID 2750767.1)

Last updated on DECEMBER 08, 2022

Applies to:

Symptoms

OSMS agent service fails to start on instances with more than one VNIC. Attempts to start the agent service manually on Windows fails as well. You may see associated entries in the Windows event log stating the service timed-out or took too long to respond.

For illustration purposes, the routing table from an instance with two VNICs is provided as follows. The primary interface on the instance has the IP address 10.x.0.5 and the secondary interface has the IP address 10.x.0.21

1. Routing table as-is  (from output of command "route print") with traffic to 169.254.169.254 going through the secondary interface with IP address 10.x.0.21:

Changes

 Addition of a secondary VNIC to the instance

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.