We have remotes sites with a mixture of MPLS, Frame, and VPN end points. No groups created yet, getting starting on a clean slate.
I am starting to work on MPLS remote sites. What I am thinking of is this: Each site has one router, may have multiple switches and/or WAP's.
|Node - MPLS Router/MPLS Serial Interface||Node - Remote Router Loobpack Address|
|Node - Remote Router Loopback Address||Group - Remote Switches/Wireless AP's|
|Groups - Switches||Groups - Remote Servers|
I am thinking that if I use the Loopback address on the remote router, I can setup alerts for the Multilink and ethernet interfaces?
Any suggestions for custom properties (I have a custom property indicating city), I have read where others have created custom properties using Tier(x).
Chris, do you have any internal site identifiers? What about subnet, could you just create the groups based on the IPs of the devices at the site or is that not reasonable (maybe you have overlapping subnets)?
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.