We have now tested the firmware upgrade on 1.1.0 / 1.1.1 / 1.2.0rc4 and 1.2.0rc5 all with the same result
If we after firmware upgrade do "Default" then "manual configuration or configuration restore" we can do reboot from web, but if we after do a power unplug the switch is unstable again and do not answer to ping from routed network or from another switch connected ping only work to equipment direct connected in 1 line to the switch.
Firmware 1.2.0rc4 comments
-
sirhc - Employee
- Posts: 7490
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1643 times
- Been thanked: 1336 times
Re: Firmware 1.2.0rc4 comments
Hightech wrote:We have now tested the firmware upgrade on 1.1.0 / 1.1.1 / 1.2.0rc4 and 1.2.0rc5 all with the same result
If we after firmware upgrade do "Default" then "manual configuration or configuration restore" we can do reboot from web, but if we after do a power unplug the switch is unstable again and do not answer to ping from routed network or from another switch connected ping only work to equipment direct connected in 1 line to the switch.
Please start with the switch "when it is working" as you expect and post up your config Tabs as it is at that point.
Then please give a step by step to recreate the problem.
Step 1) All is working at this point on v1.X.X and here are the config Tabs at this point
Step 2) Upgrade from x to x
Step 3) ...
If we can recreate the problem we can fix it.
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
sirhc - Employee
- Posts: 7490
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1643 times
- Been thanked: 1336 times
Re: Firmware 1.2.0rc4 comments
NOTE: There was a reported bug affecting the switch if you renumbered the DEFAULT VLAN, this was not fixed until v1.1.1 and/or v1.2.0rc5
I think you have the default VLAN renumbered so you should do this.
Upgrade switch to v1.1.1 or v1.2.0rc5
Factory default the switch.
Manually upgrade configure the switch.
At this point it should be working.
At this point do NOT downgrade below these versions as you KNOW that v1.1.0 and v1.2.0rc4 BOTH have issues with renumbering the "default" VLAN.
So if you want to try and recreate this just upgrade to the same version and try it DO NOT DOWN GRADE TO v1.1.0 or v1.2.0rc4 OR BELOW or you will have issues if you have the default VLAN renumbered.
I think you have the default VLAN renumbered so you should do this.
Upgrade switch to v1.1.1 or v1.2.0rc5
Factory default the switch.
Manually upgrade configure the switch.
At this point it should be working.
At this point do NOT downgrade below these versions as you KNOW that v1.1.0 and v1.2.0rc4 BOTH have issues with renumbering the "default" VLAN.
So if you want to try and recreate this just upgrade to the same version and try it DO NOT DOWN GRADE TO v1.1.0 or v1.2.0rc4 OR BELOW or you will have issues if you have the default VLAN renumbered.
V1.1.1 and v1.2.0rc5 wrote:
Fixed bugs reported in v1.1.0 & v1.2.0rc5 and would be present in all previous versions
- Fixed detecting switch IP address if not on default VLAN
- Fixed problem with DHCP when not using the default VLAN or changing default VLAN ID
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
Hightech - Member
- Posts: 36
- Joined: Wed Mar 11, 2015 3:15 pm
- Has thanked: 3 times
- Been thanked: 5 times
Re: Firmware 1.2.0rc4 comments
We have now tested the switch for the last 3 hours, with firmware and reboots etc.
And our conclusions is it not the firmware as we thougt was the problem.
But the NIC/port negotiation after reboot or power unplug that fails, when the switch get back from reboot and dosent answer on ping we unplug lan cable and connect again and the link is online and answer to ping, we have tryed to lock the nic link to 1G FD it works only 4 out of 5 times!
Our connected equipment is Ubuquiti (RocketM5/RocketM5ti/NanoBeamM5-400/AirFiber24/PowerBeamAC-500)
Any suggestion or do you think it's a nic driver in the switch that can be changed?
Br.
Carsten
And our conclusions is it not the firmware as we thougt was the problem.
But the NIC/port negotiation after reboot or power unplug that fails, when the switch get back from reboot and dosent answer on ping we unplug lan cable and connect again and the link is online and answer to ping, we have tryed to lock the nic link to 1G FD it works only 4 out of 5 times!
Our connected equipment is Ubuquiti (RocketM5/RocketM5ti/NanoBeamM5-400/AirFiber24/PowerBeamAC-500)
Any suggestion or do you think it's a nic driver in the switch that can be changed?
Br.
Carsten
-
sirhc - Employee
- Posts: 7490
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1643 times
- Been thanked: 1336 times
Re: Firmware 1.2.0rc4 comments
When you do this reboot and you think there is a problem how long have you left it sit (done nothing) to see if it corrects itself when set to AUTO?
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
Hightech - Member
- Posts: 36
- Joined: Wed Mar 11, 2015 3:15 pm
- Has thanked: 3 times
- Been thanked: 5 times
Re: Firmware 1.2.0rc4 comments
On this test 1-5 min.
On the switches we all ready have in production network 30-45 min the time it takes to get to the tower.
On the switches we all ready have in production network 30-45 min the time it takes to get to the tower.
-
Mola9850 - Member
- Posts: 78
- Joined: Thu Feb 19, 2015 3:47 pm
- Location: Denmark
- Has thanked: 14 times
- Been thanked: 14 times
Re: Firmware 1.2.0rc4 comments
just wanted to say that I have tested with Hightech.
It has probably been in port for 5-6 min without coming back with ping,
but as soon as we switch port or just disconnect the cable and reconnect it then comes ping immediately.
our setup is as follows
Ip 10.106.100.217
Sup 255.255.255.0
Gw 10.106.100.254
P DNS 10.10.10.10
S DNS 10.10.10.11
And VLANs as the picture,
it's this setup we have used to test with.
It has probably been in port for 5-6 min without coming back with ping,
but as soon as we switch port or just disconnect the cable and reconnect it then comes ping immediately.
our setup is as follows
Ip 10.106.100.217
Sup 255.255.255.0
Gw 10.106.100.254
P DNS 10.10.10.10
S DNS 10.10.10.11
And VLANs as the picture,
it's this setup we have used to test with.
- Attachments
-
- Skærmbillede 2015-03-16 22.53.59.png (191.65 KiB) Viewed 6412 times
Med venlig hilsen / Yours sincerely
Morten Lauritsen
Salg & Service
D: +45 9393 7040
M: [url=mailto:Morten@wified.dk]Morten@wified.dk[/url]
Morten Lauritsen
Salg & Service
D: +45 9393 7040
M: [url=mailto:Morten@wified.dk]Morten@wified.dk[/url]
-
Dave - Employee
- Posts: 726
- Joined: Tue Apr 08, 2014 6:28 pm
- Has thanked: 1 time
- Been thanked: 158 times
Re: Firmware 1.2.0rc4 comments
thanks Morten/Hightech, we are trying to reproduce to see what has happened....
-
sirhc - Employee
- Posts: 7490
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1643 times
- Been thanked: 1336 times
Re: Firmware 1.2.0rc4 comments
It would help if Hightech gave us screen grabs of all the Tabs and a list of what equipment is plugged into each port and a step by step of do this and it happens.
Once we get the screen grabs, list of everything plugged into each port and his do this then this and bang you get this we will attempt to re-create this in a lab.
There is no nic driver, the switch core is a stand alone unit provided but the chip maker just like any switch core rather it is Vitesse that we use or Broadcam that Ubiquiti uses.
We just write the UI that configures the switch core same as any switch manufacturer based on a switch core, not a soft switch like you do with linux on a computer with a whole bunch of nics which is not what you get when you buy a Layer 2 or 3 switch as it would be way to slow and not non-blocking line speed like you get with dedicated hardware like a switch core.
However with all that being said this could be caused by the way we are rebooting the switch and re-configuring the switch core on a reboot which Hightechs unique configurations or combination of equipment used has issues with?
It may also have something to do with the modifications we did to allow the renumbering of the default VLAN, who knows as this issue is not reported by anyone else to my knowledge?
This is the FUN part of making equipment like this as not everybody will use the equipment is the exact same way with the exact same configuration with who knows what other equipment. This also makes it IMPOSSIBLE to test every possible configuration that your equipment will encounter until a bug is reported and then it is not always possible to duplicate it. - FUN STUFF!
I am powering all sorts of UBNT gear with my config and I do not have any problem like this so it has to be something related to his configuration I would think or maybe there is some other piece of equipment as of yet unknown that he is using that is not working well with is?
Once we get the screen grabs, list of everything plugged into each port and his do this then this and bang you get this we will attempt to re-create this in a lab.
There is no nic driver, the switch core is a stand alone unit provided but the chip maker just like any switch core rather it is Vitesse that we use or Broadcam that Ubiquiti uses.
We just write the UI that configures the switch core same as any switch manufacturer based on a switch core, not a soft switch like you do with linux on a computer with a whole bunch of nics which is not what you get when you buy a Layer 2 or 3 switch as it would be way to slow and not non-blocking line speed like you get with dedicated hardware like a switch core.
However with all that being said this could be caused by the way we are rebooting the switch and re-configuring the switch core on a reboot which Hightechs unique configurations or combination of equipment used has issues with?
It may also have something to do with the modifications we did to allow the renumbering of the default VLAN, who knows as this issue is not reported by anyone else to my knowledge?
This is the FUN part of making equipment like this as not everybody will use the equipment is the exact same way with the exact same configuration with who knows what other equipment. This also makes it IMPOSSIBLE to test every possible configuration that your equipment will encounter until a bug is reported and then it is not always possible to duplicate it. - FUN STUFF!
I am powering all sorts of UBNT gear with my config and I do not have any problem like this so it has to be something related to his configuration I would think or maybe there is some other piece of equipment as of yet unknown that he is using that is not working well with is?
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
Hightech - Member
- Posts: 36
- Joined: Wed Mar 11, 2015 3:15 pm
- Has thanked: 3 times
- Been thanked: 5 times
Re: Firmware 1.2.0rc4 comments
This is the test setup only ToughSwitch 8 and Netonix WS-8-250-AC is needed, just reboot the switch and see the resoult with ping to netonix switch from the 2 computeres.
the computer on Netonix switch get answers from netonix trunked mgt ip interface, the computer on ToughSwitch 8 fails on reboot's of Netonix switch
Test:
1). Reboot Netonix from webinterface menu, wait... when it's online again wait 4-5 min Reboot again...
2). After 3 reboots do a unplug of power cable wait 30 sec, plug-in power cable.
3). if not unstable begin from 1). again
After max: 4 reboots the switch got unstabel in our test.
/Carsten
the computer on Netonix switch get answers from netonix trunked mgt ip interface, the computer on ToughSwitch 8 fails on reboot's of Netonix switch
Test:
1). Reboot Netonix from webinterface menu, wait... when it's online again wait 4-5 min Reboot again...
2). After 3 reboots do a unplug of power cable wait 30 sec, plug-in power cable.
3). if not unstable begin from 1). again
After max: 4 reboots the switch got unstabel in our test.
/Carsten
- Netonix_test.jpg (35.35 KiB) Viewed 6394 times
Who is online
Users browsing this forum: No registered users and 35 guests