restarting vtss appl

[Michael Day]

What does this mean?
Dec 11 13:17:33 monitor: restarting vtss_appl

And why did it happen?

[Eric Stern]

That is the process that handles many functions of the switch. It crashed and was automatically restarted by the monitoring service. There isn't really a way to tell why. If it happens frequently it may indicate a hardware issue with the switch.

[Michael Day]

Thank you. I do have pre-programmed spares if needed.

[skapur]

We have experienced similar issue with one of our Netonix switches where adding 4 VLANs resulted in a restart of this module and dropped a physical interface as seen in the below logs:

Code: Select all

 


Sep 17 11:31:48 UI: VLANs: added 'VLAN17'
Sep 17 11:31:48 UI: VLANs: added 'VLAN18'
Sep 17 11:31:48 UI: VLANs: added 'VLAN19'
Sep 17 11:31:48 UI: VLANs: added 'VLAN20'
[b]Sep 17 11:31:57 monitor: restarting vtss_appl[/b]
Sep 17 11:31:59 LACP: starting negotiation with partner E4-8D-8C-35-72-82
Sep 17 11:31:59 Port: link state changed to 'up' (1G) on port 13
Sep 17 11:32:00 Port: link state changed to 'up' (1G) on port 13
Sep 17 11:32:00 Port: link state changed to 'down' on port 14
Sep 17 11:32:00 LACP: starting negotiation with partner E4-8D-8C-35-72-82
Sep 17 11:32:00 Port: link state changed to 'up' (1G) on port 14
Sep 17 11:32:02 LACP: LACP changed state to Active on port 13 (key 1)
Sep 17 11:32:04 LACP: LACP changed state to Active on port 14 (key 1)
Sep 17 11:32:04 STP: set port 15 to discarding
Sep 17 11:32:04 STP: set port 13 to discarding
Sep 17 11:32:04 STP: set port 14 to discarding
Sep 17 11:32:06 STP: set port 15 to learning
Sep 17 11:32:06 STP: set port 13 to learning
Sep 17 11:32:06 STP: set port 14 to learning
Sep 17 11:32:06 STP: set port 15 to forwarding
Sep 17 11:32:06 STP: set port 13 to forwarding
Sep 17 11:32:06 STP: set port 14 to forwarding
Sep 17 11:32:13 UI: Error occured during TFTP auto backup: tftp: timeout

 

The switch is running on firmware version 1.4.9

Do you think this is because of hardware fault on this switch?

[sirhc]

The switch is running on firmware version 1.4.9

Do you think this is because of hardware fault on this switch?

NO.

Upgrade your firmware and see if the problem is still there.

We are on v1.5.1rc4

v1.4.9 is 10 months old.

[airlinkrb]

We are seeing this problem as well. We are on 1.5.0 ... going to upgrade to the latest RC and see what happens.

[airlinkrb]

No Luck, sirhC.

Still seeing this in the logs.

Jan 1 00:00:12 netonix: 1.5.1rc5 on WS-12-250-DC

Jan 1 00:00:15 system: Setting MAC address from flash configuration: EC:13:B2:82:CA:C6

Jan 1 00:00:19 admin: adding lan (eth0) to firewall zone lan

Dec 31 18:00:35 admin: removing lan (eth0.99) from firewall zone lan

Dec 31 18:00:39 admin: adding lan (eth0.99) to firewall zone lan

Dec 31 18:00:45 admin: adding lan (eth0.99) to firewall zone lan

Dec 31 18:00:48 system: starting ntpclient

Dec 31 18:00:53 switch[1413]: Detected warm boot

Dec 31 18:00:55 system: starting ntpclient

Sep 18 16:59:54 system: time set by NTP server

Sep 18 17:00:15 monitor: restarting vtss_appl

Sep 18 17:01:22 monitor: restarting vtss_appl

Sep 18 17:01:35 monitor: restarting vtss_appl

[airlinkrb]

When the vtss_app1 line shows up in the log, we see a couple of packets lost when pinging customers beyond the switch. We also see a dip in traffic throughput all happen for a bit at the same time.

- Casey

[sirhc]

Then there are 2 things possibly occurring:

1) The config is corrupted, a power on factory default then manually set the switch up.
How do do a power on default is explained here: viewtopic.php?f=6&t=409#p2398

2) As Eric said above your switch is damaged and need repaired.

RMA instructions are located here: viewtopic.php?f=6&t=1259#p9343

You could also bench test it as explained in detail here: viewtopic.php?f=6&t=2780#p19221

[nroufus]

I recently just started experiencing this error. Every time it occurs, we see a latency spike/packet loss across the switch itself and all connected devices, throughput dropping, as well as port errors incrementing. We've tried two different switches and experiencing the same on both. WS-12-250-AC (original, first occurred here) and WS-12-250-DC (new replacement), both running 1.5.0. Did try a hard reset and configuring by hand (as suggested above). Same symptoms. Any ideas?

(EDIT) I was finally able to get it to stop by disabling the Discovery Tab. Updating to 1.5.1rc7 alone did not fix my issue. After re-enabling it, the logs display the "restarting vtss appl" error every minute, almost on the dot. Disabled again, and haven't had an issue since.