FAQ
From Netmon
Installing NetmonSE
What if I cannot get DHCP working? What if my network does not support DHCP?
If the netmon auto-installer cannot successfully attain an IP address using DHCP, it will prompt you to enter an IP address manually. It will present you with this screen:
Choose "configure network manually". You will then be asked for the IP address, subnet mask, gateway and DNS server to use during the installation. Once the device can successfully connect to your network with these settings, the installation will continue as normal. Once Netmon is installed, you unfortunately will need to reconfigure the network settings.
What does it mean when I cannot connect to the Debian repositories?
This is the result of a network connectivity issue. You will see an error message like this:
To diagnose the network issue, switch to the command console by pressing CTRL+ALT+F2. Run the command:
wget http://mirrors.kernel.org/
DNS Problem
If there is a DNS issue, the output will say “Hostname lookup failure.” Run the command:
nano /etc/resolv.conf
This will open the DNS settings file in a text editor. If the dns servers are incorrect, edit them to reflect your correct DNS servers. If there is no data in the file, enter a new line that says:
nameserver 10.10.1.27
Where 10.10.1.27 is the ip address of your DNS server. Press CTRL+X to save and exit from the text editor.
Now run wget http://mirrors.kernel.org again and it should complete successfully if DNS entries were correct. Press CTRL+ALT+F1 to switch back to the installer screen, and select <Go Back> to try the step again.
Other Connection Issues
If wget is able to resolve the DNS name, but is still not able to connect, the issue is probably a routing or firewall issue. Contact your System Administrator to see if there is something blocking internet access.
If you need to reconfigure the IP address, reboot and start the installer again.
Network Adapter Compatibility
If any of the above steps do not resolve the issue, it is possible that there is some kind of compatibility issue with your network adapter. Try a different network adapter, contact support@netmon.ca and describe the model so we can investigate compatibility issues with that adapter.
I'm getting an error that says "Temporary Failure in resolving DNS Hostname"
On some environments, DNS resolution does not become operational in time for the installer to download. When this happens, we must manually download and run the installer program. After the failure message, it will ask you to login. Login with the credentials root/netmon.
Once logged in, run the commands:
wget http://www.netmon.ca/support/downloads/netmonse-latest.py
python ./netmonse-latest.py
My Netmon install gives me error messages and won't start
This is almost always due to a network outage, or some other kind of hiccup, during the installation process. Follow the instructions on screen to reboot the machine and try again. If this repeatedly fails, put the installer CD back in the drive and start the entire installation process over again. If the problem persists, contact support@netmon.ca.
Using Netmon (SE, Professional, Enterprise)
Its prompting me for a username and password, what is it?
Remember to always change the default password the first time you login!
Gnome desktop credentials
netmon/netmon How to change: Run the Terminal program found on the desktop. Run the command passwd.
Netmon Application credentials:
admin/netmon How to change: In Netmon, Settings > User Management > Manage User Accounts.
Operating system root/administrator credentials:
root/netmon How to change: Run the command passwd.
When I run a Latency Report for an ICMP or TCP tracker, all the values come back N/A. What needs to be setup to make this report work?
For each of your trackers, you must set Logging Threshold to "log everything". From this point on you will have latency information for those trackers.
Why can't my Netmon device update?
Netmon uses the rsync protocol (port 873) to retrieve patch updates from the Netmon update server. Your firewall is most likely blocking requests over this port, or there is no internet connectivity from your Netmon device. To test internet connectivity, run the command
ping -c10 dev.netmon.ca
From the netmon command prompt.
I've activated Netmon, now what do I do?
Refer to our Getting Started guide at http://wiki.netmon.ca/index.php/User_Guide:Getting_Started
How do I set up my mail server?
Within the Netmon application, goto Settings > Netmon Services > Email Alert Service > Configure. Specify the IP address or hostname of your SMTP server, and the address from which alerts will appear to be coming from.
Netmon comes with its own internal mail server, which is used if the server in Settings > Netmon Services > Email Alert Service > Configure is set to 127.0.0.1.
What is SNMP? How do I find out more about it?
SNMP is the Simple Network Management Protocol, used to retrieve real-time status and other information from network devices. For more information, see http://en.wikipedia.org/wiki/Snmp
Errors And Solutions
Unable to establish a connection to the core process manager / Critical Error / Fatal Error
This means the Netmon background services are not running. The background services are what actually powers netmon's monitoring functionality. To restart the services, run this command:
/etc/init.d/netmon restart
See here for help on running commands: How to access the command prompt
If the error persists, you can determine the reason they are not starting by looking at the output of:
cat /var/log/netmon/procmond
If this says "Invalid serial key", please contact Netmon sales to resolve issues with your license.
If there are no error messages in the logs and the services still will not start, please contact support at netmon.ca
UPDATED 06/24/2008
Occasionally this error message occurs due to an incomplete or interrupted update of the operating system or Netmon itself.
First, make sure the operating system distribution is up-to-date. Login via SSH as root and run the command "aptitude update" and wait till finished. Next, run the command "aptitude dist-upgrade". You may have to answer "Yes" to some prompts and reboot once the upgrade has finished.
Once you have finished upgrading the operating system and have rebooted, check if you can login to the web interface and check for any further error messages. If this has not resolved the issue, check the current Netmon patch level (Settings->Netmon Update Service). You should see an output screen reporting the current Netmon and component versions.
This system is currently running Netmon v4.8
The following components are currently installed:
Name Description Version
========================================================
services Netmon Background Services 9
environment Operating System 7
middleware Middleware 16
ui User Interface and Documentation 1
Note the Netmon version (currently 4.8) and the component versions. Click the "Check for New Updates Now" button and you will be notified if there are any components needing to be upgraded. The upgrade process will automatically run and restart the services. If this does not resolve the issue, it may be necessary to perform a more thorough investigation of the system. Please contact Netmon Technical Support for further assistance.
Error -103 Unable to connect to PostgreSQL server: could not connect to server
This means Netmon's database engine is not started. To start the database, run the command:
/etc/init.d/postgresql-8.1 restart
If the error persists, please contact support at netmon.ca
Cannot add a device
If netmon is unable to add a device under the Devices screen, this is usually due to one of the following problems:
- The community string mismatches with the community string that was setup on the device
- There is a network connectivity problem between netmon and the device
- Netmon's IP address is not allowed to access SNMP services on the device. On some devices, you must manually list which IP addresses are able to request SNMP communication with the device. Exactly how this is done varies on all devices, so consult your device's documentation on how this is done.
- The SNMP TCP port (usually 161) is not open on the device, preventing SNMP requests from being received. This can be tested using Netmon's port scanning tool under Networks > Port Scan (select 'complete' scan).
SVCCONTROL Alert Response fails due to SMB signing on Windows server
When attempting to restart a Windows service on a server that has SMB signing required, the svccontrol command will fail with a message similar to the following:
netmon:~# /usr/local/samba-tng/bin/svccontrol -S 190.10.9.28 -U Administrator%********* -W NETMON.CA -c "service stop W3SVC" Server: \\190.10.9.28: User: Administrator Domain: NETMON.CA Connection: WARNING: remote site seems to require smb signing, which we do not (yet) support. session setup ok Domain=[NETMON.CA] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2] cli_send_tconX failed: STATUS_ACCESS_DENIED failed tcon_X cli_net_use_add: connection failed FAILED WARNING: remote site seems to require smb signing, which we do not (yet) support. cli_nt_session_open: cli_nt_create failed on pipe \svcctl to machine 190.10.9.28. Error was STATUS_ACCESS_DENIED ncacn_np_use_add: connection to \\190.10.9.28:\PIPE\svcctl failed Failed Service Stopped (W3SVC) Exit Status: SUCCESS
This issue can be resolved by editing the Group Policy of the target server.
How to disable SMB signing on Windows 2003 Server Domain Controller: 1. Click Start, point to Programs, point to Administrative Tools, and then click Domain Controller Security Policy. 2. In the left pane, expand Local Policies, and then click Security Options. 3. In the right pane, double-click Microsoft network server: Digitally sign communications (always). 4. Click to select the Define this policy setting check box, click Disabled, and then click OK. 5. Double-click Microsoft network server: Digitally sign communications (if client agrees). 6. Click to select the Define this policy setting check box, click Enabled, and then click OK. 7. Double-click Microsoft network client: Digitally sign communications (always). 8. Click to clear the Define this policy setting check box, and then click OK. 9. Double-click Microsoft network client: Digitally sign communications (if server agrees). 10. Click to clear the Define this policy setting check box, and then click OK. 11. From the command line, run "gpupdate /force".
Navigation
