Discovery VLAN visibility issue

[arielgritti]

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

[Carlos Loza]

Hi Ariel,

just adding to what already has been discussed,

I've used the network discovery before and for example, the way it works, you can do something like scanning a /16 network (over the weekend) to find all the subnets reported by the Routers there, and it dumps them all in the IP Networks module, you still need to manually add them to schedules, though

it could be a possibility on your case if all of those +4500 are visible from the 4 Mids you mention, it ultimately ends on the network team to do all those routing rules, so the Mids can see everything, I think

[arielgritti]

Hi Carlos,

Thanks for your feedback here, I appreciate it.

The fact here is I know the networks, there are 12 x centers (2 routed, visible for Mid Servers, 10 not routed, not visible for Mid Servers, with some /xx configuration (/22, /23, /24, etc).

The issue is that those VLANs aren't routed; then Mid Server can't "see" them. My doubt (probably I wrongly asked it) is how to route those VLANs in a network to make them visible for the Mid Servers. It's not a ServiceNow configuration, it's a network configuration.

Thanks,

Ariel