Page 1 of 7
my watchdog is not working
Posted: Tue Sep 08, 2015 4:29 pm
by gerardor884
I have set up these settings on the watchdog, please advise if the setting are not properly set up. Thank you
Re: my watchdog is not working
Posted: Tue Sep 08, 2015 4:32 pm
by sirhc
1) What version of the firmware are you running? There were recent fixes for watchdog. ***see firmware release notes***
2) Please explain what happens? Either nothing or it keeps rebooting your radios?
Please post the VLAN Tab and Device/Config Tab
Re: my watchdog is not working
Posted: Tue Sep 08, 2015 5:05 pm
by gerardor884
1) What version of the firmware are you running? There were recent fixes for watchdog. ***see firmware release notes***
I have the firmware version 1.3.2
2) Please explain what happens? Either nothing or it keeps rebooting your radios?
it does nothing, it does not responds
Please post the VLAN Tab and Device/Config Tab
I am not using VLAN, VLAN is not enable
Re: my watchdog is not working
Posted: Tue Sep 08, 2015 6:15 pm
by sirhc
gerardor884 wrote:1) What version of the firmware are you running? There were recent fixes for watchdog. ***see firmware release notes***
I have the firmware version 1.3.2
2) Please explain what happens? Either nothing or it keeps rebooting your radios?
it does nothing, it does not responds
Please post the VLAN Tab and Device/Config Tab
I am not using VLAN, VLAN is not enable
What do you mean it does not respond?
It should not respond unless the pings fail 3 consecutive pings in a row and then disable the port POE for 5 seconds rebooting it the device and then send you a an SMPT message provided you have SMTP setup correctly.
I am running a test now to confirm it works, I know I tested this a few weeks ago.
This shows in the log that a ping watchdog was enabled. I have it pinging an address that nothing is at so it will fail.
Sep 8 17:56:18 UI: Configuration changed by 192.168.1.176
Sep 8 17:56:18 UI: PingWatchdog 1 Enable: changed from 'Disabled' to 'Enabled'
Sep 8 17:56:20 pinger: starting up with 1 ping watchdogs and 0 scheduled port bounces
Sure enough it did work and rebooted my camera
Sep 8 17:57:59 pinger: Failure pinging 192.168.1.15, powering off port 10 for 10 seconds
Sep 8 17:57:59 pinger: Cannot notify, SMTP is not enabled
CLICK IMAGE BELOW TO VIEW FULL SIZE
- watchdog.jpg (399.62 KiB) Viewed 9138 times
v1.3.3 FINAL bug reports and comments
Posted: Tue Sep 22, 2015 7:51 pm
by sirhc
Please post comments and reports bugs with v1.3.3 FINAL in this thread
v1.3.3 wrote:NOTE: We had some enhancements for the SFP ports but we decided to remove them as they were still buggy but will put them back in the v1.3.4 firmware so for now SFP ports are handled the same as v1.3.2. So if you needed the SFP enhancements to make your SFP module work please wait until we release v1.3.4rc1 which should be in a couple days.
FIXES
- Fixed VLAN configuration
- Fixed slowness with configurations with hundreds of VLANs
- Fixed slowness with MAC Table with thousands of MACs
- Fixed problem with MAC Table on SFP ports on 12 port models
- Fixed POE power being turned off when port is disabled or not in a VLAN if POE Smart is enabled
- Fixed IP address lookup for MAC Table
- Fixed support for WS-12-DC
- Fixed some log messages
- Fixed problem with Auto backup TFTP URLs containing a path
- Changed input voltage check to only happen on dumb DC models
ENHANCEMENTS
- Added reboot after resetting to defaults in CLI
- Added timed shutdown periods for PoE on DC models
- Improved VLAN tab UI
- Added Flow Control indicator to Link column on Status tab
- Added email notifications for LACP port status changes
- Changed RSTP to be enabled by default
KNOWN ISSUES
- Ubiquiti Discovery Protocol is still flaky
- IPERF is a work in progress
Re: v1.3.3 FINAL bug reports and comments
Posted: Tue Sep 22, 2015 8:26 pm
by keefe007
What was fixed with VLAN configuration?
Re: v1.3.3 FINAL bug reports and comments
Posted: Tue Sep 22, 2015 8:44 pm
by sirhc
keefe007 wrote:What was fixed with VLAN configuration?
Eric is off line but I believe it was to do with the Management VLAN
Here was one example where it solved an issue:
viewtopic.php?f=17&t=930&p=7712&hilit=v1.3.3rc5#p7697
Re: v1.3.3 FINAL bug reports and comments
Posted: Wed Sep 30, 2015 4:00 pm
by anvilcom
After lab'ing our WS-12-250-AC we finally deployed it. I hadn't tested the email feature since 1.2.4 or so. Now testing shows that ssmtp actually uses the mail host name as the client host name while EHLO 'ing. Our server will drop the connection as it detects this as a forged host name - and rightly so.
I checked both /etc/ssmtp/ssmtp.conf and /jffs/etc/ssmtp/ssmtp.conf. They both have the the same value for the two different variables:
- Code: Select all
mailhub=[mail.ourdomain.com]:25
hostname=mail.ourdomain.com
AFAIK, hostname should be the actual host name assigned to the switch, not the name of the mail server.
We are running version 1.3.3
Maybe this has already been addressed, but I thought I'd report it anyway.
Re: v1.3.3 FINAL bug reports and comments
Posted: Wed Sep 30, 2015 5:40 pm
by designweb
i have not seen one mac address since putting 1.3.3 on ten switches so far, all worked fine on previous versions
Re: v1.3.3 FINAL bug reports and comments
Posted: Wed Sep 30, 2015 5:48 pm
by sirhc
designweb wrote:i have not seen one mac address since putting 1.3.3 on ten switches so far, all worked fine on previous versions
I am not sure I follow what your saying here?