1 of 1 people found this helpful
Have you checked NetPath plugin is installed on that agent? Settings > All Settings > Manage Agents > More Actions > View Plugin Report.
Also make sure you use Orion Primary IP (IP displayed in node management) when you create new NetPath Probe.
Thank you Lan Li. Using the Orion Primary IP address of the Node where the agent was installed did the trick.
I might have discovered this sooner on my own, but I had edited the node properties and changed the IP. The server I installed the agent on is dual homed. The IP address that the Orion agent picked up was the IP that's on a private VLAN used to connect to an iSCSI SAN. I had changed it to the server's data NIC IP. After reading your post, it occurred to me that maybe Orion still considered the iSCSI VLAN IP as the primary IP. Once I used that IP when creating the probe, voila!
I've manually deployed the agent on the client machine and set it up so the server can initiate a connection to an agent on port 1222. When I add agent on the Agent management. I'm successfully able to connect and all plugin looks and green. Although When I tried to create new service under NetPath for the following service and I can't see new created remote agent in the list of Probe dropdown. I can see Agent is polling to primary server as well. I'm I missing something please help
Probing Interval: 10