Friday Feb 14, 2014

Adding an asset on a remote network

I saw an interesting question about discovering assets:

"I'm trying to discover a new chassis. I have three Proxy Controllers and all of them can ping the chassis, but only one has the firewall access to communicate with it. None of the Proxy Controllers has a direct connection to the network with the chassis, so that network isn't in the network list. How do I get the discovery job to route correctly?"

There is a solution in the discovery profile here. The discovery profile has a field for the target host or IP address, and a dropdown for the network. When you put the profile together, you supply the asset's IP address, and then select a network that has a route to the network with the chassis on it. Run that and you'll be able to discover the asset.

About

This blog discusses issues encountered in Ops Center and highlights the ways in which the documentation can help you

Search

Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
5
6
8
9
10
11
12
13
15
16
17
18
19
20
22
23
24
25
26
27
29
30
31
      
Today