Nagios Support Forum

We purchased Nagios XI for a customer that wants to monitor their Motorola Radio Network. We installed NagiosXI using VMware Workstation Player on a server running SERVER 2016. Currently we have the radio network on Ethernet port 1 of the server and it is working the way we want it too so far. However, the customer has decided they want email/text notification, and have used another ethernet port to connect to the internet for notification, and access to the client. Since these are two different networks, I am having problems understading how to connect these two networks on the server. Am I doing something wrong. PLEASE HELP.

Bill Clark

Server 2016 should come with the ability to setup Hyper-V so you wouldn't need to run VMWare Player on the server (instead you'd use free Hyper-V) but the choice is yours.

Generally, you would need to add a route/firewall rules at the network level so that the packets know to go down that path instead of the default path but it really depends on how you have it setup. You'll need to work with your firewall/security/network teams to do that.

Does the XI server have a 2nd NIC now?

The first thing you need to do is see if you can ping something on the other end of the pipe:
- Change X.X.X.X to something that's on the other end of the internet connection that you know you have access to
See here for the XI side:
See here for the Linux (XI server) side:

Thanks for replying Sean,

First of all, I need to let you know that I have very little experience with virtual machines and even less with servers.

I did do a 'ip a' command. This is what I have:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue static UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:d29d brd ff:ff:ff:ff:ff:ff
inet 10.246.1.105/24 brd 10.246.1.255 scope global noprefixroute ens33
valid_lft forever preferred_lft forever
inet6 fe80::a44:a9ab:b5d6:aa72/64 scope link nonprefixroute
valid_lft forever preferred_lft forever

I did do a ip route:

default via 10.246.1.254 dev ens33 proto static metric 100
10.246.1.0/24 dev ens33 proto kernel scope link src 10.246.1.105 metric 100

the host server has 4 ethernet ports and 1 wifi connection. I am using ethernet port 1 on the server for the network I am monitoring with NagiosXI.

That ethernet port is 10.246.1.104
VMware Nagios IP is 10.246.1.105
The wif fi adaptor to the internet is 192.168.1.82

The monitored network has its own gateway to all of the sites.
The Gateway IP is 10.246.1.254

The Wifi Gateway is 192.168.1.2

Please let me know what else I can give you to help.

Thanks

Can you ping out from the XI server command line to the internet?
What is the output of this command?
The line below means that your default route is set to go out through 10.246.1.254 on interface ens33:

default via 10.246.1.254 dev ens33 proto static metric 100

Is that what you want?

That is the network that we are monitoring. The internet network is 192.168.1.X
I can not ping the internet or dns 8.8.8.8

Is it possible to add my wifi device in the nmtui and Nagios be able to recognize both adaptors?

Right now it looks like you've only got 1 network adapter assigned to your Nagios virtual machine. That network adapter leads off to the 10.246.1.0/24 network, which if I'm reading this correctly, is a closed network. No internet connection there, just devices that you want to monitor. Does that sound right?

If I'm understanding correctly, then there's probably another NIC that the Windows Server 2016 host uses to get out to 192.168.1.0/24. Your Nagios VM will need a virtual NIC that is bridged to the NIC that Windows is using. You will have to shut down the Nagios VM in order to add this second virtual NIC. Also make sure you're creating a bridge to the NIC that Windows is using. If you pass the NIC through to the VM, then Windows won't be able to use it, and you will lose connection to the Windows machine.

When Nagios comes back up, we will need to make sure that the routes are correct. But let's do this one step at a time. Let's start with getting the second NIC added. When you have that, and Nagios is back up and running, give us the output of ip a, and ip route. Then we'll work on the next step.

Thanks Sean,

I do only have 1 adaptor set up in the Nagios server. I will add another nic to the virtual machine. That is done thru the nmtui gui correct?

I am not on site right now, but will be able to be there within a couple of hours. I will let you know when I get that far.

Thanks again for your help
Bill

I am not on site right now, but will be able to be there within a couple of hours. I will let you know when I get that far.
Thanks again for your help

Hi Bill,

Thanks for the update and let us know if you have any other questions.