Page 2 of 2
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 8:01 am
by twingard51
This is getting a bit frustrating. The ipaddress was reachable on Friday. Now it is not. I did try starting and stopping the iptables service. I can ping/reach the gateway on the network from the host. I did try restarting the network service and determined that the device is up. I tried using nslookup and got a reverse lookup result : 195.1.11.172 in-addr.arpa name=nag4prd.pgworks.com. Why did the ipaddress suddenly become unreachable by ping....
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 9:44 am
by tmcdonald
Do you have any sort of firewall between the Nagios server and the machine you are pinging from?
What was the result of disabling the firewall? Were you then able to ping consistently or access the web interface?
Have any modifications been made to the system post-install?
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 10:11 am
by twingard51
No change when iptables is down or up
ficonfig shows the device is up and broadcasting
The only change I made is using the tui tool to change to static ip and apply device configuration and dns
the host is fully resolveable with nslookup when I use the fqdn, but not short host name
As mentioned I can ping out consistently from the host, but over the weekend it became unreachable from other hosts on the network
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 10:22 am
by twingard51
if config shows device is broadcasting on the local loopback and on eth0....
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 10:28 am
by ssax
There are only a few options for what could be wrong.
1. Someone changed a firewall rule or ACL/Route on a router/switch in between the hosts.
2. The local firewall, you already stopped the iptables service and checked so that wasn't the problem.
3. There is another device on your network with the same IP.
4. The netmask/default gateway isn't set properly.
If you set it back to DHCP does it work properly? If so, verify the IP/Netmask/Gateway.
Edit: Also if you do a traceroute to the machine where does it show it dying?
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 11:19 am
by twingard51
I cannot use DHCP here. Not allowed except on the desktop pcs
The device is alive(eth0) but I can't ping it so I don't think I can use traceroute from another machine to reach it
the netmask is set to 255.255.255.0 which is what the netmask is on all the servers
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 11:47 am
by twingard51
I think I can access from the same subnet. I will do that and use the configuration manager to finish configuring...standby...and thanks
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 12:02 pm
by jdalrymple
You need to be able to ping your default gateway... can you?
Code: Select all
[jdalrymple@localhost ~]$ ping -c 3 `route | grep default | awk '{print $2}'`
PING 192.168.145.2 (192.168.145.2) 56(84) bytes of data.
64 bytes from 192.168.145.2: icmp_seq=1 ttl=128 time=0.088 ms
64 bytes from 192.168.145.2: icmp_seq=2 ttl=128 time=0.104 ms
64 bytes from 192.168.145.2: icmp_seq=3 ttl=128 time=0.113 ms
Sounds like you have some lurking network issues. I'd double and triple check my netmask, and FWIW, NM often confuses the matter. I'm sure it's just as heated of a debate as emacs vs. vi - but there are some things I simply cannot get NM to do, it has a mind of its own. I disable it on every install
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 12:16 pm
by twingard51
heated debate...I don't bother, I have been using vi for a lifetime and it just works...I am on the website by using a browser on the same subnet...I am configuring, but what files need to be configured in http config to allow myadmin? I'll figure out the netowrk subnet problem after. I'm just glad to be at the website.
Re: starting nagios xi web infterface
Posted: Mon Mar 23, 2015 12:21 pm
by jdalrymple
What do you mean by "myadmin"? The httpd files in a default NagiosXI install don't restrict based upon anything except login credentials. Have you changed them?
Network subnet may be the only problem. If you cannot ping the machine from a remote network then there is no chance that you'll be able to drag http across to the other network.