Page 1 of 1

Map Architecture - Best Practice

Posted: Mon Mar 10, 2014 12:50 pm
by valbizures
I'm trying to use parent devices to group specific assets within my organization on the map view. For example:

I have a perimeter firewall who is a parent to all my devices. But rather than having them all linked to the firewall I would like to view them in the following map structure

Firewall
- Web Servers
Web Server 1, 2, 3, etc
- Security Servers
Security Server 1,2,3, etc

The only way I can think of doing this is by creating a "dummy" host called WebServers, make it a child of Sonicwall and make all Web Servers children of the dummy web servers host.

Question: Is this possible? Is this the best practice recommendation for creating such a map topology? I assume that I would have to turn off/disregard any notifications on this dummy host.

Any advice would be greatly appreciated.

Re: Map Architecture - Best Practice

Posted: Mon Mar 10, 2014 1:53 pm
by sreinhardt
You are correct, you would need a dummy host to make this work as you mentioned. There isn't really anything wrong with it, provided you keep those dummy hosts in an ok state. I would also suggest against adding any services to them, and just have the base check_dummy as the host check.

Re: Map Architecture - Best Practice

Posted: Mon Mar 10, 2014 3:43 pm
by valbizures
Thanks for the reply.

Basically what I ended up doing is creating a group.cfg w/ generic hosts and the IP address of 0.0.0.0. So far it appears to be working. I didn't specify any services so as of right now things are looking good.


Thanks again for the reply/confirmation.

Re: Map Architecture - Best Practice

Posted: Mon Mar 10, 2014 4:00 pm
by sreinhardt
You're welcome, I'm going to lock this up, but if you run into other issues let us know!