v1.4.0rc1-16 Bug reports and comments

[designweb]

upgraded to 10 48 hours later get false report of loop on port 6, then 24 hours later AF24 on port 2 starts flapping, shutdown power to that port and now AF24 dead all power readings are RED on status, but voltages show normal?? changed to rc11 no difference

Jan 1 00:00:07 netonix: 1.4.0rc10 on WS-24-400A
Jan 1 00:00:12 kernel: link state changed to 'up' on port 1
Jan 1 00:00:12 kernel: link state changed to 'up' on port 2
Jan 1 00:00:12 kernel: link state changed to 'up' on port 5
Jan 1 00:00:12 kernel: link state changed to 'up' on port 6
Jan 1 00:00:12 kernel: link state changed to 'up' on port 7
Jan 1 00:00:12 kernel: link state changed to 'up' on port 8
Jan 1 00:00:12 kernel: link state changed to 'up' on port 10
Jan 1 00:00:12 kernel: link state changed to 'up' on port 9
Jan 1 00:00:12 kernel: link state changed to 'up' on port 11
Jan 1 00:00:12 system: Setting MAC address from flash configuration: EC:13:B3:01:1C:BE
Jan 1 00:00:14 kernel: link state changed to 'up' on port 23
Jan 1 00:00:14 kernel: link state changed to 'up' on port 24
Jan 1 00:00:16 admin: adding lan (eth0) to firewall zone lan
Jan 1 00:00:22 admin: removing lan (eth0.1303) from firewall zone lan
Jan 1 00:00:26 admin: adding lan (eth0.1303) to firewall zone lan
Jan 1 00:00:26 kernel: link state changed to 'down' on port 2
Jan 1 00:00:27 kernel: link state changed to 'down' on port 5
Jan 1 00:00:27 kernel: link state changed to 'down' on port 6
Jan 1 00:00:27 kernel: link state changed to 'down' on port 7
Jan 1 00:00:27 kernel: link state changed to 'down' on port 8
Jan 1 00:00:27 kernel: link state changed to 'down' on port 9
Jan 1 00:00:27 kernel: link state changed to 'down' on port 10
Jan 1 00:00:27 kernel: link state changed to 'down' on port 11
Jan 1 00:00:28 kernel: link state changed to 'down' on port 23
Jan 1 00:00:28 kernel: link state changed to 'up' on port 1
Jan 1 00:00:29 kernel: link state changed to 'up' on port 2
Jan 1 00:00:29 kernel: link state changed to 'down' on port 24
Jan 1 00:00:29 kernel: link state changed to 'up' on port 8
Jan 1 00:00:29 kernel: link state changed to 'up' on port 10
Jan 1 00:00:29 kernel: link state changed to 'up' on port 6
Jan 1 00:00:29 kernel: link state changed to 'up' on port 5
Jan 1 00:00:29 kernel: link state changed to 'up' on port 9
Jan 1 00:00:29 kernel: link state changed to 'up' on port 7
Jan 1 00:00:30 kernel: link state changed to 'up' on port 11
Jan 1 00:00:31 kernel: link state changed to 'up' on port 23
Jan 1 00:00:32 kernel: link state changed to 'up' on port 24
Jan 1 00:00:37 admin: adding lan (eth0.1303) to firewall zone lan
Jan 1 00:00:39 system: starting ntpclient
Apr 9 03:32:30 dropbear[1419]: Running in background
Apr 9 03:32:39 switch[1493]: Detected warm boot
Apr 11 09:52:54 Loop protection: detected loop from port 6 to port 6, disabling port 6 for 180 seconds
Apr 11 09:55:57 Loop protection: re-enabling port 6
Apr 11 11:10:54 Loop protection: detected loop from port 6 to port 6, disabling port 6 for 180 seconds
Apr 11 11:13:57 Loop protection: re-enabling port 6
Apr 11 11:17:59 kernel: link state changed to 'down' on port 23
Apr 11 11:18:40 kernel: link state changed to 'up' on port 23
Apr 11 11:28:29 UI: Configuration changed by admin (83.167.161.232)
Apr 11 11:28:29 UI: Credentials_Password: changed
Apr 11 11:28:34 passwd: Password for admin changed by admin
Apr 11 11:55:19 kernel: link state changed to 'down' on port 23
Apr 11 11:56:00 kernel: link state changed to 'up' on port 23
Apr 11 12:01:50 kernel: link state changed to 'down' on port 24
Apr 11 12:02:13 kernel: link state changed to 'up' on port 24
Apr 12 10:06:05 Loop protection: detected loop from port 6 to port 6, disabling port 6 for 180 seconds
Apr 12 10:09:08 Loop protection: re-enabling port 6
Apr 12 16:59:44 kernel: link state changed to 'down' on port 2
Apr 12 16:59:46 kernel: link state changed to 'up' on port 2
Apr 12 16:59:48 kernel: link state changed to 'down' on port 2
Apr 12 16:59:50 switch[1434]: 48V is out of range (38.0V)
Apr 12 16:59:50 switch[1434]: 24V is out of range (19.2V)
Apr 12 16:59:50 switch[1434]: 24V (Ports 13-24) is out of range (15.6V)
Apr 12 16:59:50 switch[1434]: 3V is out of range (2.3V)
Apr 12 16:59:50 kernel: link state changed to 'up' on port 2
Apr 12 16:59:52 kernel: link state changed to 'down' on port 2
Apr 12 16:59:54 kernel: link state changed to 'up' on port 2
Apr 12 16:59:56 kernel: link state changed to 'down' on port 2
Apr 12 16:59:58 kernel: link state changed to 'up' on port 2
Apr 12 17:00:01 kernel: link state changed to 'down' on port 2
Apr 12 17:00:04 kernel: link state changed to 'up' on port 2
Apr 12 17:00:05 kernel: link state changed to 'down' on port 2
Apr 12 17:00:07 kernel: link state changed to 'up' on port 2
Apr 12 17:00:09 kernel: link state changed to 'down' on port 2
Apr 12 17:00:11 kernel: link state changed to 'up' on port 2
Apr 12 17:00:14 kernel: link state changed to 'down' on port 2
Apr 12 17:00:16 kernel: link state changed to 'up' on port 2
Apr 12 17:00:19 kernel: link state changed to 'down' on port 2
Apr 12 17:00:21 kernel: link state changed to 'up' on port 2
Apr 12 17:00:24 kernel: link state changed to 'down' on port 2

[sirhc]

Loop Protection can be disabled on the Device/COnfiguration Tab if you think it is a false alert.

However Loop Protection is not like RSTP.

It sends a special BPDU packet out each port every second and if the packet comes back even to the same port or another port it shut the sending or receiving port down for 180 seconds.

So if a customer or another piece of equipment further out on your network has a leaky VLAN or a loop it will cause this to happen.

Leaky VLANs or equipment can cause false loop protections.

[designweb]

Thanks Chris

I only say it is probably false because there is a Motorola link on the end that has nothing on the end yet, however what has caused the over voltage readings and the AF24HD to die is a major concern, cable diagnostics perfect, port 1 has AF24HD and port 5 a Siklu and other ports have various M5 and AC and are all working well, taken down to 1.39 and AF24HD now powers up but port only at 10mb Half Duplex no mac address or data






Current Time
12/04/2016 18:21:46


Uptime
00:20:50


CPU Usage
100 %300 %


Memory Usage
128 MB48.10 MB


MAC Address
ec:13:b3:01:1c:be


IP Address
172.16.121.148


Firmware Version
1.3.9


Board Rev
D





Board 48V60 V38.530 VBoard 24V (Ports 1 - 12)27 V17.620 VBoard 24V (Ports 13 - 24)27 V19.120 VBoard 3V4 V2.13 V

[sirhc]

I have no idea, you need to investigate more and find more info out.

Were there any storms in your area?
Maybe the AF24HD died?
Maybe the port in the switch died?

I do know but there is no way the switch can kill an AF24HD as it is a 48VH device and that is all the switch can deliver and it physically can not swap polarity on paris or anything as that is all hardwired.

Personally I would go on site:
1) Test the AF24HD with a POE brick and laptop
2) Test port in switch by turning off poe and using a laptop to insure you are getting 1G connection, maybe run a cable diagnostics on the port.

[designweb]

I have brought up backup link which allows me to get to other side of AF and after powercycling three times the wireless link is up but the port has a data error dpstat-reserved-Full, cable diagnostics on port report perfect cable, tried auto neg down to half 10 and port stays down. Engineer will get to site later and test switch port but looks like airfibre may be RMA

[sirhc]

Well when your engineer is on site you should test out the switch to insure it is not damaged.

Procedure:
1) Turn off POE on that port
2) Unplug cables from port and run cable diagnostics on that port as you should get OPEN, OPEN, OPEN, OPEN
3) Plug your laptop into the port and make sure you get 1G connection

Now if all has passed at this point the last thing to do is test that the Current sensors did not get damaged.

If the port appear to work next plug in new AF24 with a short jumper and power it up with 48VH.
On the main Status Tabis should read 45-52 watts, if it read half that amount or no watts then 1 or more of the 2 current sensors on that port got fried.

This happened to me in this post:
viewtopic.php?f=30&t=1429

[IntL-Daniel]

Unfortunately again false detections in the log with rc11:

Apr 12 22:10:46 switch[1359]: 48V is out of range (34.3V)
Apr 13 06:09:40 switch[1359]: 48V is out of range (34.3V)

...rolling back to 1.3.9 :(

[IntL-Daniel]

By the way this post viewtopic.php?f=17&t=1459&start=80#p12092 was probably lost in space...could anyone comment? Thanks.

[designweb]

left AF24HD off overnight, switch still on 1.3.9 still complaining voltages out of range, powered AF reinstalled 3.2, (this had been on there for many months anyway absolutely faultless) AF back online at a gig looking as if nothing had happened but read out below

shared memory for mutex already exists
Compiled for board Luton26-ref, chip VTSS_CHIP, ports: 26
mux version is 1
temp sensor version 2
setting io expander 1 249
port 1 config changed
port 2 config changed
port 3 config changed
port 4 config changed
port 5 config changed
port 6 config changed
port 7 config changed
port 8 config changed
port 9 config changed
port 10 config changed
port 11 config changed
port 12 config changed
port 13 config changed
port 14 config changed
port 15 config changed
port 16 config changed
port 17 config changed
port 18 config changed
port 19 config changed
port 20 config changed
port 21 config changed
port 22 config changed
port 23 config changed
port 24 config changed
port 25 config changed
port 26 config changed
poe_thread, portCount 26
current temp is 42 C
setting fan speed to 255/5 (power usage is 157.17 W)
getCPUUsage 5496470 1450562 26
getFanSpeed 0: 0 52263 1567890
found fan at 1
getFanSpeed 1: 52263 52533 8100
Detected warm boot
switch[716]: Detected warm boot
PoE initialized
using bitstring '01010000011000101010100011000000000000000000000000000000', bits 56, led 0
setting clock 26 load 27 data 25 reset 28 data_out 23
using bitstring '101000001001000101010100000000000000000000000000', bits 48, led 1
setting clock 20 load 21 data 19 reset 22 data_out 24
found fan at 2
getFanSpeed 2: 52533 52830 8910
found fan at 0
getFanSpeed 0: 52830 53140 9300
found all 3 fans
!48V is out of range (38.5V)
switch[714]: !48V is out of range (38.5V)
!24V is out of range (19.1V)
switch[714]: !24V is out of range (19.1V)
!24V (Ports 13-24) is out of range (19.2V)
switch[714]: !24V (Ports 13-24) is out of range (19.2V)
!3V is out of range (2.1V)
switch[714]: !3V is out of range (2.1V)
getCPUUsage 5497139 1450690 19
current temp is 42 C
setting fan speed to 100/5 (power usage is 15.50 W)
getFanSpeed 0: 54727 55028 9030
getFanSpeed 1: 55028 55143 3450
getFanSpeed 2: 55143 55230 2610
getCPUUsage 5497796 1450771 12
getFanSpeed 0: 55230 55322 2760
getFanSpeed 1: 55322 55409 2610
getFanSpeed 2: 55409 55496 2610
getFanSpeed 0: 55496 55582 2580
getFanSpeed 1: 55582 55669 2610
getFanSpeed 2: 55669 55751 2460
getCPUUsage 5498449 1450892 18
getFanSpeed 0: 55751 55839 2640
getFanSpeed 1: 55839 55927 2640
current temp is 42 C
setting fan speed to 100/5 (power usage is 17.00 W)
getFanSpeed 2: 55927 56013 2580
getFanSpeed 0: 56013 56101 2640
getFanSpeed 1: 56101 56190 2670
getFanSpeed 2: 56190 56269 2370
getCPUUsage 5499103 1450988 14
getFanSpeed 0: 56269 56358 2670
getFanSpeed 1: 56358 56445 2610
getFanSpeed 2: 56445 56528 2490
getFanSpeed 0: 56528 56615 2610
getFanSpeed 1: 56615 56704 2670
getFanSpeed 2: 56704 56784 2400
getCPUUsage 5499758 1451120 20
getFanSpeed 0: 56784 56869 2550
current temp is 42 C
setting fan speed to 100/5 (power usage is 16.90 W)
getFanSpeed 1: 56869 56958 2670
getFanSpeed 2: 56958 57043 2550
getFanSpeed 0: 57043 57129 2580
getFanSpeed 1: 57129 57216 2610
getFanSpeed 2: 57216 57295 2370
getCPUUsage 5500411 1451253 20
getFanSpeed 0: 57295 57385 2700
getFanSpeed 1: 57385 57474 2670
getFanSpeed 2: 57474 57558 2520
getFanSpeed 0: 57558 57647 2670
getFanSpeed 1: 57647 57735 2640
getFanSpeed 2: 57735 57818 2490
current temp is 42 C
setting fan speed to 100/5 (power usage is 17.00 W)
getCPUUsage 5501067 1451357 15
getFanSpeed 0: 57818 57907 2670
getFanSpeed 1: 57907 57998 2730
getFanSpeed 2: 57998 58081 2490
getFanSpeed 0: 58081 58167 2580
getFanSpeed 1: 58167 58255 2640
getFanSpeed 2: 58255 58340 2550
getCPUUsage 5501719 1451490 20
getFanSpeed 0: 58340 58426 2580
^C

[sirhc]

FIXED
- Fixed SNMP reported uptime - rc2
- Fixed rare problem with mac table not loading - rc3
- Fixed small UI issues with Firefox and IE - rc3
- Fixed SNMP CPU counters - rc4
- Fixed SNMP firmware version string - rc4
- Fixed so log messages now used VLAN ID instead of index - rc4
- Fixed RADIUS to work with SSH- rc9
- Fixed port not being in VLAN Bug- rc9
- Fixed pps being included in totals when port was excluded- rc9
- Fixed false fan failure detection *we hope*- rc9
- Fixed cleared log to indicate who cleared it- rc9
- Fixed so no duplicate VLAN ID allowed- rc9
- Fixed SSH session ending messages so not reported by dropbear- rc9
- Fixed Firefox autocomplete (workaround) - rc10
- Fixed language encoding - rc10
- Fixed console in UI - rc10
- Fixed graphs on Status Tab - rc11
- Fixed some incorrect voltage readings/alerts - rc11
- Fixed some more I2C communications problems mostly for SMART DC models. - rc12
- Fixed RSTP path cost now able to set to 1 - rc12

ENHANCEMENTS
- Increased MAX allowed DC input voltage for WS-8-250-DC and WS-12-250-DC to 61.5V for off grid solar sites - rc2
- IMPROVED SMART DC switches I2C communication- rc9
- Added HTTP Port to be changed- rc9
- Added telnet for CLI access- rc9
- Added Discovery to Tools menu- rc9
- Added multiple languages support- rc9
- Added VLAN information to SNMP- rc9
- Added Revert Timer Help Balloon- rc9
- Added total power consumption to SNMP- rc9
- Added DC input voltage graph on the Device/Status Tab- rc9
- Added tooltips to buttons- rc9
- Added increased SMTP Username length- rc9
- Added Power tab on all models for time conditions- rc9
- Change ifDescr and ifAlias- rc9
- Time Condition graphic on Christmas tree rc10
- Added To line to email header rc10
- Added more graphs for SMART DC models under Device/Status Tab - rc11
- Added an Enable/Disable check box for TFTP backup - rc11
- Reduced CPU usage - rc12

KNOWN ISSUES
- None

rc12 Released 4/14/2016 - If your running v1.4.0rcX or have a SMART DC Switch I recommend upgrading
rc11 Released 4/12/2016
rc10 Released 4/08/2016
rc9 Released 4/05/2016
rc4 Released 2/29/2016
rc3 Released 2/11/2016
rc2 Released 2/06/2016