Discovery VLAN visibility issue

arielgritti · ‎10-14-2023

Hi Community

I have a challenge to discover devices over VLANs in remote locations where the subnets/VLANs aren't routed and are using the same addresses (192.168.1.0/24).

How can we discover devices over those VLANs?

The Network team proposes connecting to a VPN for each remote location (+4500). The first question (forgetting the fact that doing it for +4500 locations is a really high number) is whether it is possible.

Another idea? A MID server in each location? Another expensive solution. Is ACC (Agent Client Collection) an option here?

Did you see a similar network configuration and how it was solved at the network level? ACLs? NAT?

We're able to discover devices on the network/VLANs already routed with public IPs. That is running fine. The challenge is for those VLANs.

Any help/idea is welcome.

Thanks,

Ariel

Rahul Priyadars · ‎10-15-2023

Service Now Product Perspective You already wrote possible Options.

--> 1 Mid Server Per Location and Runs Discovery as it is. Problem - Maintenance

--> ACC agents on Devices in those Vlan still need a Mid Server .

Why do we need a Mid Server ? Location - Assuming those VLANs can not talk/Communicate with Each. So in my view if Your n/w team can give some more Consolidation around those 4500 locations VLANS else i do not see much options from Service Now Side.

Regards

RP

arielgritti · ‎10-16-2023

Hi Rahul

Thanks for your feedback, I appreciate it.

What do you think about this? https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/discovery/concept...

I'm exploring the "Private IP Address" configuration + Initial router; It is an option?

And a potential routing at the Mid Server VM level? We've 4 dedicated VM's running Mid Servers. We can do some "DNS" or "routing" actions on this side?

Thanks,

Ariel

Rahul Priyadars · ‎10-16-2023

ahh Vancouver - Still not explored much as of now but thanks for Pointing me out on this URL.

Regards

RP

arielgritti · ‎10-16-2023

I believe it's from Utah too (I just shared the first link I found, it was Vancouver).

The "issue" or "challenge" here is more at the "network configuration" level/side than in ServiceNow as you have mentioned.

We need a "network expert" to bring some light here.