Date: Fri, 29 Mar 2024 06:16:24 +0000 (UTC) Message-ID: <913404973.4027.1711692984578@skald.opmantek.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4026_6812851.1711692984577" ------=_Part_4026_6812851.1711692984577 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
TABLE OF CONTENTS
RELATED ARTICLES
Ping it with a big echo request.
[root@opmantek co= nf]# ping -c 5 -s 1472 192.168.88.254 PING 192.168.88.254 (192.168.88.254) 1472(1500) bytes of data. 1480 bytes from 192.168.88.254: icmp_seq=3D1 ttl=3D63 time=3D319 ms 1480 bytes from 192.168.88.254: icmp_seq=3D2 ttl=3D63 time=3D323 ms 1480 bytes from 192.168.88.254: icmp_seq=3D3 ttl=3D63 time=3D321 ms 1480 bytes from 192.168.88.254: icmp_seq=3D4 ttl=3D63 time=3D320 ms 1480 bytes from 192.168.88.254: icmp_seq=3D5 ttl=3D63 time=3D322 ms --- 192.168.88.254 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4330ms rtt min/avg/max/mdev =3D 319.542/321.519/323.551/1.450 ms
What does nmap think about it?
[root@opmantek co= nf]# nmap 10.10.1.1 Starting Nmap 5.51 ( http://nmap.org ) at 2017-04-04 15:05 KST Nmap scan report for 10.10.1.1 Host is up (0.011s latency). Not shown: 998 closed ports PORT STATE SERVICE 22/tcp open ssh 23/tcp open telnet Nmap done: 1 IP address (1 host up) scanned in 13.53 seconds [root@opmantek conf]#=20
Suddenly the node cannot be found in the GUI. When attempting to r= e-add the node to NMIS via the GUI we receive a 'node already exists' error= .
Something has become very corrupt, we need to purge NMIS of all relevant= node configuration.
The problem node should now be functioning properly in the NMIS GUI.
If a node isn't providing the data we think it should sometimes looking = at manual update & collect debugs is helpful. Redirect or tee the= output to a file in order to review latter.
[root@opmantek ~]= # /usr/local/nmis8/bin/nmis.pl node=3Dasgard debug=3D9 type=3Dupdate > n= odeUpdate.txt -or- [root@opmantek ~]# /usr/local/nmis8/bin/nmis.pl node=3Dasgard debug=3D9 typ= e=3Dupdate | tee nodeUpdate.txt ################### [root@opmantek ~]# /usr/local/nmis8/bin/nmis.pl node=3Dasgard debug=3D9 typ= e=3Dcollect > nodeCollect.txt -or- [root@opmantek ~]# /usr/local/nmis8/bin/nmis.pl node=3Dasgard debug=3D9 typ= e=3Dcollect | tee nodeCollect.txt
nmis= .pl provides 2 methods for checking the directory structure of nmis and= ensuring that the structure is complete and has the correct permissions (b= ased on your Config.nmis). Running type=3Daudit will report disc= repancies between your structure and what is required, type=3Dconfig will f= ix those errors
# optionally audi= t your config /usr/local/nmis8/bin/nmis.pl type=3Daudit # fix your config /usr/local/nmis8/bin/nmis.pl type=3Dconfig
Additonally, the script fixperms.pl will go through and set the permiss= ions on each file to ensure that NMIS can access the files it requires to o= perate normally
# fix permissions= =20 /usr/local/nmis8/admin/fixperms.pl
Sometimes there are things happening on Linux systems which don't make s= ense, many times it is because SELinux is preventing things. You can = spend a lot of time getting SELinux to behave, or you can put it in permiss= ive mode, or disable it, in the NMIS VM it has been disabled.
Much information to be found with Google, the following describes either= option.
http://www.crypt.gen.nz/selinux/disable= _selinux.html
Contacts.nmis must have the correct DutyTime format.
conf/Config.nmis must have the proper auth_method order as well as that = method being provisioned.
If LDAP isnt working tcpdump can be used to see the response code from t= he LDAP server.
Are we collecting many interfaces that are not necessary?
Check the view.json file for number of interfaces and interface type.&nb= sp; Look for common things such as interface type and description. Us= e models or Config.nmis to disable collection.
When troubleshooting syslog issues the following script will gather more= rsyslog daemon information then the nmis support tool.
When troubleshooting snmptrapd issues the following script will gather m= ore snmptrad daemon information then then nmis support tool.
When troubleshooting models it's important to know if all the OID's that= have a 'friendly name' are referenced within Model files have been defined= in /usr/local/nmis8/mibs/nmis_mibs.oid. Some Model files import or c= all other Model, Graph or Common files. If an OID 'friendly name' has= not been defined in nmis_mibs.oid it may not be obvious which model file i= s causing the problem. In order to validate friendly names more easil= y the script below has been provided. It will parse all the OID frien= dly names out of the model files and look for them in nmis_mibs.oid. = If they are not found the operator will be notified. At some point t= his script should be converted to perl; this would make it much faster.