
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2016 07:10 AM
Hi,
We have data available in Exit interface routing table but still we dont have any relationships. Anyone knows which sensor is responsible for creating the relationship of IPConnection::IPConnection.
Regards,
Vivek
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-16-2016 05:03 AM
Hi Vivek.
Starting with the Helsinki release, Service Maps will include layer 2 network switches in the maps.
For either Layer2 or Layer3 network devices, standard discovery must be run against the individual IP Addresses of the devices or the IP Ranges that include the devices.
Details about how to set the Network discovery up:
Is this job giving you any errors that you can share?
BR
Chatarina
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2016 07:15 AM
I've been chasing this for a while. It's kind of my Holy Grail for Network Change requests.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2016 04:33 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2016 11:02 PM
He Bradley,
We have already gone through that doc. We already have all the prerequisites. This doc doesn't have enough details like which sensor is creating this relationship and all.
Regards,
Vivek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-14-2016 06:16 AM
You may have the same issue we do, all our routers and switches are set to Layer 2, not Layer 3. I've asked and been told no by our Network Engineers. You have to have Layer 3 to get Discovery to do what you need for this. Apparently you can buy Service Watch to get this done on a Layer 2 network.