Having set up our lab, we will now get into the nitty-gritty of setting up SolarWinds NPM. Just to confirm that the Windows Server can reach both routers, I will ping: Just run command prompt as administrator and use the command: route add 10.12.13.0 mask 255.255.255.0 10.11.12.1 Note: To make R2 reachable from the Windows Server, you can add a static route through the command prompt. The configuration on R2 is as follows: hostname R2 Username cisco privilege 15 secret cisco123 The configuration on R1 is as follows: hostname R1 The configuration on the routers is simple: IP addresses, EIGRP and SNMP community strings. Just search for “Loopback Manager” and follow the instructions on the command prompt window that opens.įor older versions of Windows, this article will help. Hint: Adding a loop-back interface to newer Windows operating systems is very simple. To create a network between the Windows Server and the GNS3 lab, I created a loopback interface on the Windows Server and then connected one of the routers to this loop-back interface. I’m using Windows Server 2012 R2 as my base OS even though Windows Server 2012 and Windows Server 2016 are also supported by SolarWinds NPM.įor the networking side of things, I’m using GNS3 to simulate my routers. To make this article as practical as possible, we will install SolarWinds NPM to monitor a Windows Server 2012 and two Cisco routers in a lab environment.įor this evaluation, I launched an AWS EC2 instance on which the SolarWinds NPM will be installed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |