FIDO: Web Client
FIDO: Web Client
Where is the web client?
CampusThe read only interface requires no password. The comments field requires netid authentication and is enabled for net, noc, and tools groups.
Federated members are
https://fido-animal.net.wisc.edu/
FIDO: fido.cgi header information
FIDO: Use of colors in FIDO web applications
FIDO: fido.cgi alarm table information
FIDO: fido.cgi options
FIDO: Fido information page [fido_test_info.cgi]
FIDO: 'not found' alarms from the fido_snmp test
Default Web View
During significant network events, the FIDO report file can get large. The HTML you see in the FIDO frame is created server side and sent to the client. The default option view has been optimized such that the HTML you see is created only once per report update on the server side. If you are NOT using FIDO options, you will see 'Static View' displayed at the top. If you ARE using options, you will be shown which options have caused you to deviate from the static view.
The read only interface requires no password. The comments field requires your fido.uwsys.net username/password.
Federated members are
FIDO: fido.cgi header information
FIDO: Use of colors in FIDO web applications
FIDO: fido.cgi alarm table information
FIDO: fido.cgi options
FIDO: Fido information page [fido_test_info.cgi]
FIDO: 'not found' alarms from the fido_snmp test
Logging
You can optionally view a frame that follows the fido log file. Enable this by clicking 'show_logging' in FIDO options pane at the bottom of the main FIDO page.See also: [Link for document 9856 is unavailable at this time.]
Default Web View
During significant network events, the FIDO report file can get large. The HTML you see in the FIDO frame is created server side and sent to the client. The default option view has been optimized such that the HTML you see is created only once per report update on the server side. If you are NOT using FIDO options, you will see 'Static View' displayed at the top. If you ARE using options, you will be shown which options have caused you to deviate from the static view.
FAQ
Errant entries in the fido report file
There are a couple of scenarios in which data may appear to be stuck in the fido report file. One example of how to get yourself into this situation is if there are items in the monitoring screen for a particular OID and then the snmp poller stops monitoring ALL hosts for that OID.Use the fido_fix_report tool to get around this problem
[m7h@fido bin]$ sudo -u net ./fido_fix_report.pl test=ibCPUTemperature 2017/01/03 14:52:38:FATAL: cannot run when fido.pl is running! at ./fido_fix_report.pl line 76 [m7h@fido bin]$ sudo /usr/local/fido/etc/init.d/fido stop Stopping fido.pl: [ OK ] [m7h@fido bin]$ sudo -u net ./fido_fix_report.pl test=ibCPUTemperature 2017/01/03 14:52:44:Delete of 'ipam-animal.doit.wisc.edu ibCPUTemperature probe temperature (C)-ibCPUTemperature' wanted because of 'test=ibCPUTemperature' 2017/01/03 14:52:44:Delete of 'ipam-cssc.doit.wisc.edu ibCPUTemperature probe temperature (C)-ibCPUTemperature' wanted because of 'test=ibCPUTemperature' Commit Changes?: [y]: y 2017/01/03 14:52:47:Matched 2 item(s), saving to /var/local/fido/reports/fido.report.bin [m7h@fido bin]$ sudo /usr/local/fido/etc/init.d/fido restart Stopping fido.pl: [FAILED] Starting fido.pl: [ OK ]