restarting vtss appl

[drbaker]

I can confirm, disabling discovery tab in switch configuration the problem dissapears. Brand new switchs with last RC firmware upgrade.

[GREG3f]

I experienced the same issue...monitor: restarting vtss_appl in the logs and packet loss to and through the switch when the messaged appeared in the logs.Disabled the Discovery Tab option as suggested and so far so good.

I should also say the Netonix Rebooted itself either right before the packet loss started or during the issue.

This issue only appeared shortly after I upgraded a Mikrotik ARM Router to the latest stable firmware. Not sure if it was related but thought I would mention it in case it sheds some light on this bizzar issue.

WS12-250-AC with 1.5.0
Mikrotik RB3011 upgraded to 6.43.8

[cbwecomm]

This still seems to be an issue, as I just discovered it as well.

[Stephen]

Hello cbwecomm,

Please be sure you are on the latest firmware if you are seeing this issue.
There was a significant effort sometime back to deal with vtss_appl restarts,

Here are a few more links with information about that:
viewtopic.php?f=17&t=5687&hilit=vtss_appl&start=10
viewtopic.php?f=17&t=240&p=32801&hilit=vtss_appl#p32801


If you are experiencing vtss_appl restarts with the latest firmware, please provide some more details, logs, topology, config, etc so we can try and figure out what is causing it.

[VW-Richard]

Out of curiosity what functions are handled by vtss_api?

Nevermind; It looks like everything that makes it a switch.

This is after globally disabling STP.

Code: Select all

Jun 15 14:15:13 monitor: restarting vtss_appl
Jun 15 14:15:18 LACP: starting negotiation with partner 00-1C-73-A0-08-F3
Jun 15 14:15:20 LACP: LACP changed state to Active on port 26 (key 256)
Jun 15 14:15:20 LACP: LACP changed state to Active on port 25 (key 256)
Jun 15 14:18:04 UI: Configuration changed by admin (::ffff:192.168.244.11)
Jun 15 14:18:04 UI: Discovery_Ubiquiti: changed from 'Enabled' to 'Disabled'
Jun 15 14:18:04 UI: Discovery_Cisco: changed from 'Enabled' to 'Disabled'
Jun 15 14:18:04 UI: Discovery_LLDP: changed from 'Enabled' to 'Disabled'
Jun 15 14:18:04 UI: Discovery_Discovery_Tab: changed from 'Enabled' to 'Disabled'
Jun 15 14:18:04 UI: Discovery_Broadcast_On_Protocols: changed from 'Enabled' to 'Disabled'
Jun 15 14:18:27 monitor: restarting vtss_appl
Jun 15 14:18:30 LACP: starting negotiation with partner 00-1C-73-A0-08-F3
Jun 15 14:18:32 LACP: LACP changed state to Active on port 26 (key 256)
Jun 15 14:18:33 LACP: LACP changed state to Active on port 25 (key 256)
Jun 15 14:18:40 UI: Configuration changed by admin (::ffff:192.168.244.11)
Jun 15 14:18:40 UI: Discovery_LLDP: changed from 'Disabled' to 'Enabled'
Jun 15 14:18:43 monitor: restarting vtss_appl
Jun 15 14:18:58 monitor: restarting vtss_appl
Jun 15 14:19:00 LACP: starting negotiation with partner 00-1C-73-A0-08-F3
Jun 15 14:19:02 LACP: LACP changed state to Active on port 26 (key 256)
Jun 15 14:19:02 LACP: LACP changed state to Active on port 25 (key 256)
Jun 15 14:20:28 UI: Configuration changed by admin (::ffff:192.168.244.11)
Jun 15 14:20:29 UI: Discovery_LLDP: changed from 'Enabled' to 'Disabled'


[Stephen]

Nevermind; it looks like everything that makes it a switch.

Correct. (click for more info)

It's not necessarily strange for it to spin around a few time's after certain config changes as long as it's not continuing to do so.

Be sure you're on the latest firmware

[cbwecomm]

1.5.6 ; same issue. Trying the "disable discovery tab" This is either a bug that continued to exist later on (and yes, I know I have a ways to upgrade), or it's something else...we did have this switch go through some insane heat recently (was maxed at 125C).

[cbwecomm]

I can confirm disabling the discovery tab stops the packet loss and lockup/hang.

[sirhc]

Have you considered upgrading to the latest firmware to address the vtss_appl restart issue, and have you observed any improvements after disabling the discovery tab?

Thank you

Yes people should always upgrade to the LATEST including RC version FIRST otherwise we are looking for something that is not there and we will request it anyway.

But his post is old and he never revisited it