Every time I add the management VLANs to the "monitor vlans" list, I loose access the the management via port 11 of switch 20 but, switch can ping each other when I connect to those via console port. When I removed the vlan 1 from the "monitored vlans" list, it taked a long time until the switch pinged again via port 11, possibly until the WTR timer expired. I can see WTR time configuration via the "show erps" command but not the time remaining so it's hard to confirm if I loose access to the GUI.
I need to do more test but I think that when a VLAN is added to "monitor vlans" list, this VLAN is block on every ports except ports part of the rings (est and west ports).
Edit: I can still access switch 22 while vlan 1 is still part of "monitored vlans" list so last présumption seem a little more to be the case.
Edit 2: a switch (21) rebooted while I was applying a change (removing vlan 1 from "monitor vlans" list) but I think it's because a loop happened. Any way to know why a switch reboot ? Seem like some kind of hardware watchdog.
v1.4.8rcX Bug reports and comments
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: v1.4.8rcX Bug reports and comments
mike99 wrote:Every time I add the management VLANs to the "monitor vlans" list, I loose access the the management via port 11 of switch 20 but, switch can ping each other when I connect to those via console port. When I removed the vlan 1 from the "monitored vlans" list, it taked a long time until the switch pinged again via port 11, possibly until the WTR timer expired. I can see WTR time configuration via the "show erps" command but not the time remaining so it's hard to confirm if I loose access to the GUI.
I confirm it's happen on tagged and on non management vlan too. The problem won't happen exacty when adding the vlan to "monitor vlans" list, the're a delay until it stop communicating but once it does, removing it from the "monitor vlans" will give access back without delay. It's not a ARP problem since deleting the switch ip address from the arp table of the PC will not make loss access to the switch. I can stop pinging, delete arp entry, verify arp entry and start pinging again and it will still ping but it will eventually stop.
Also, lot of reboot happen that seem to be related to loop when working on ERPS like if the config was flush and push back again with loop happening while config is flushed. It may be short but seem like it's enough to create problematic loop that will lead to reboot.
A recommandation, ERPS instance 1 should include all VLANs except those of other instances, just like MSTP CIST, else, loop happen easily.
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: v1.4.8rcX Bug reports and comments
I also tested MSTP since I have a setup ready to test it.
First thing I observe, changing root switch priority change it for all instance. I change it on instance 2 will also change it also changed it for instance 1 and CIST. By default, switch 20 is choose as root switch but if I set a lower global priority for instance 2 of switch 22, all instance are affected, not only instance 2. It's look like the same for name.
From Cisco doc (http://www.cisco.com/c/en/us/td/docs/sw ... wmstp.html)
Instance priority seem to don't have any effect.
To finish, sometime just won't work. I had MSTP configured and working fine. I was testing priority and cost on instance and it result in a loop. Here the interface status, vlan config and stp status while the loop was happening on the 3 switchs (port 13 and 14 all in forwarding status). Sadly, we can't see which port is enable or not via CLI, at less not with the "show stp" command, but STP is enable on port 13 and 14 for every switch and the global enable parameter is also enabled. ERPS instace and MEP have been delete on all switch.
I plugged back SFP with same result. Set priority on a port and it was fine again. Now, I can't reproduce it by setting all switch to default priority like when it's happened.
Per port priority and cost won't work in MSTP (CIST or any instance). Changing to RSTP, with same parameter as CIST, work fine but if I change back to MSTP, cost and priority don't affect the port choosen for discarding paquets.
First thing I observe, changing root switch priority change it for all instance. I change it on instance 2 will also change it also changed it for instance 1 and CIST. By default, switch 20 is choose as root switch but if I set a lower global priority for instance 2 of switch 22, all instance are affected, not only instance 2. It's look like the same for name.
From Cisco doc (http://www.cisco.com/c/en/us/td/docs/sw ... wmstp.html)
All MST instances within the same region share the same protocol timers, but each MST instance has its own topology parameters, such as root switch ID, root path cost, and so forth. By default, all VLANs are assigned to the IST.
Instance priority seem to don't have any effect.
To finish, sometime just won't work. I had MSTP configured and working fine. I was testing priority and cost on instance and it result in a loop. Here the interface status, vlan config and stp status while the loop was happening on the 3 switchs (port 13 and 14 all in forwarding status). Sadly, we can't see which port is enable or not via CLI, at less not with the "show stp" command, but STP is enable on port 13 and 14 for every switch and the global enable parameter is also enabled. ERPS instace and MEP have been delete on all switch.
- Code: Select all
20# show interface status
Port Link PoE Watts Port Name
---- -------- ---- ----- ---------
1 Disabled Off 0.0 Port 1
2 Disabled Off 0.0 Port 2
3 Disabled Off 0.0 Port 3
4 Disabled Off 0.0 Port 4
5 Disabled Off 0.0 Port 5
6 Disabled Off 0.0 Port 6
7 Disabled Off 0.0 Port 7
8 Disabled Off 0.0 Port 8
9 Disabled Off 0.0 Port 9
10 Disabled Off 0.0 Port 10
11 1G Off 0.0 Port 11
12 Disabled Off 0.0 Port 12
13 1G 13-Switch22
14 1G 14-Switch21
20#
20# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
5 true Management E E E E E E E E E E U E U U
10 true E E E E E E E E E E E E T T
20 true E E E E E E E E E E E E T T
30 true E E E E E E E E E E E E T T
40 true E E E E E E E E E E E E T T
50 true E E E E E E E E E E E E T T
4080 true E E E E E E E E E E E E T T
VLAN 5 IPv4 Address: 192.168.1.20/255.255.255.0
VLAN 40 IPv4 Address: 192.168.219.20/255.255.255.0
VLAN 50 IPv4 Address: 192.168.220.20/255.255.255.0
20#
20# show st
status Show temperatures, CPU usage, memory usage, etc
stp Spanning Tree Protocol configuration/status
20# show stp
Bridge ID : 32768.EC-13-B2-61-13-F6
Instance: CIST
Root Bridge ID: 32768.EC-13-B2-61-13-F6
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding Designated
14 Forwarding Designated
Instance: 1
Root Bridge ID: 32769.EC-13-B2-61-13-F6
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding Designated
14 Forwarding Designated
Instance: 2
Root Bridge ID: 32770.EC-13-B2-61-13-F6
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding Designated
14 Forwarding Designated
Instance: 3
Root Bridge ID: 32771.EC-13-B2-61-13-F6
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 4
Root Bridge ID: 32772.EC-13-B2-61-13-F6
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 5
Root Bridge ID: 32772.EC-13-B2-61-13-F6
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 6
Root Bridge ID: 32772.EC-13-B2-61-13-F6
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 7
Root Bridge ID: 32772.EC-13-B2-61-13-F6
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
20#
20#
21#
21#
21# show interface status
Port Link PoE Watts Port Name
---- -------- ---- ----- ---------
1 Disabled Off 0.0 Port 1
2 Disabled Off 0.0 Port 2
3 Disabled Off 0.0 Port 3
4 Disabled Off 0.0 Port 4
5 Disabled Off 0.0 Port 5
6 Disabled Off 0.0 Port 6
7 Disabled Off 0.0 Port 7
8 Disabled Off 0.0 Port 8
9 Disabled Off 0.0 Port 9
10 Disabled Off 0.0 Port 10
11 1G Off 0.0 Port 11
12 Disabled Off 0.0 Port 12
13 1G 13-Switch20
14 1G 14-Switch22
21#
21# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
5 true Management E E E E E E E E E E U E U U
10 true E E E E E E E E E E E E T T
20 true E E E E E E E E E E E E T T
30 true E E E E E E E E E E E E T T
40 true E E E E E E E E E E E E T T
50 true E E E E E E E E E E T E T T
4080 true E E E E E E E E E E E E T T
VLAN 5 IPv4 Address: 192.168.1.21/255.255.255.0
VLAN 40 IPv4 Address: 192.168.219.21/255.255.255.0
VLAN 50 IPv4 Address: 192.168.220.21/255.255.255.0
21#
21# show stp
Bridge ID : 32768.EC-13-B2-61-B4-5C
Instance: CIST
Root Bridge ID: 32768.EC-13-B2-61-13-F6
Root Path Cost: 20000
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding Root
14 Forwarding Designated
Instance: 1
Root Bridge ID: 32769.EC-13-B2-61-B4-5C
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding Master
14 Forwarding Designated
Instance: 2
Root Bridge ID: 32770.EC-13-B2-61-B4-5C
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding Master
14 Forwarding Designated
Instance: 3
Root Bridge ID: 32771.EC-13-B2-61-B4-5C
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 4
Root Bridge ID: 32772.EC-13-B2-61-B4-5C
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 5
Root Bridge ID: 32772.EC-13-B2-61-B4-5C
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 6
Root Bridge ID: 32772.EC-13-B2-61-B4-5C
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 7
Root Bridge ID: 32772.EC-13-B2-61-B4-5C
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
21#
21#
22#
22# show interface status
Port Link PoE Watts Port Name
---- -------- ---- ----- ---------
1 Disabled Off 0.0 Port 1
2 Disabled Off 0.0 Port 2
3 Disabled Off 0.0 Port 3
4 Disabled Off 0.0 Port 4
5 Disabled Off 0.0 Port 5
6 Disabled Off 0.0 Port 6
7 Disabled Off 0.0 Port 7
8 Disabled Off 0.0 Port 8
9 Disabled Off 0.0 Port 9
10 Disabled Off 0.0 Port 10
11 Down Off 0.0 Port 11
12 Disabled Off 0.0 Port 12
13 1G 13-Swtich21
14 1G 14-Switch20
22#
22# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
5 true Management E E E E E E E E E E E E U U
10 true E E E E E E E E E E E E T T
20 true E E E E E E E E E E E E T T
30 true E E E E E E E E E E E E T T
40 true E E E E E E E E E E U E T T
50 true E E E E E E E E E E T E T T
4080 true Control_Message E E E E E E E E E E E E T T
VLAN 5 IPv4 Address: 192.168.1.22/255.255.255.0
VLAN 40 IPv4 Address: 192.168.219.22/255.255.255.0
VLAN 50 IPv4 Address: 192.168.220.22/255.255.255.0
22#
22# show stp
Bridge ID : 32768.EC-13-B2-61-43-36
Instance: CIST
Root Bridge ID: 32768.EC-13-B2-61-13-F6
Root Path Cost: 2147483647
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding Root
Instance: 1
Root Bridge ID: 32769.EC-13-B2-61-43-36
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding Master
Instance: 2
Root Bridge ID: 32770.EC-13-B2-61-43-36
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding Master
Instance: 3
Root Bridge ID: 32770.EC-13-B2-61-43-36
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 4
Root Bridge ID: 32770.EC-13-B2-61-43-36
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 5
Root Bridge ID: 32770.EC-13-B2-61-43-36
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 6
Root Bridge ID: 32770.EC-13-B2-61-43-36
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
Instance: 7
Root Bridge ID: 32770.EC-13-B2-61-43-36
Root Path Cost: 0
Port Status Role
---- ----------- -----------
1 Forwarding
2 Forwarding
3 Forwarding
4 Forwarding
5 Forwarding
6 Forwarding
7 Forwarding
8 Forwarding
9 Forwarding
10 Forwarding
11 Forwarding
12 Forwarding
13 Forwarding
14 Forwarding
I plugged back SFP with same result. Set priority on a port and it was fine again. Now, I can't reproduce it by setting all switch to default priority like when it's happened.
Per port priority and cost won't work in MSTP (CIST or any instance). Changing to RSTP, with same parameter as CIST, work fine but if I change back to MSTP, cost and priority don't affect the port choosen for discarding paquets.
-
mike99 - Associate
- Posts: 837
- Joined: Tue Nov 25, 2014 10:53 am
- Location: Quebec, Canada
- Has thanked: 95 times
- Been thanked: 245 times
Re: v1.4.8rcX Bug reports and comments
I was thinking about this and remember that I should add that while the loop happen with MSTP, it taked some minutes to check every switch via console port and the switchs didn't reboot like with ERPS enabled. The switch where having a loop for 5 to 10 minutes.
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: v1.4.8rcX Bug reports and comments
Mike99,
Eric is in the process of moving to a new place to live.
Says he will get with you soon as he can in the next couple days.
We really appreciate all the hard work you are putting into testing this.
Eric is in the process of moving to a new place to live.
Says he will get with you soon as he can in the next couple days.
We really appreciate all the hard work you are putting into testing this.
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.
- IntL-Daniel
- Experienced Member
- Posts: 170
- Joined: Mon Nov 02, 2015 5:07 pm
- Location: Czech Republic
- Has thanked: 7 times
- Been thanked: 9 times
Re: v1.4.8rcX Bug reports and comments
Just a note: there is an old link description for RC3 - there is still RC2
Feature request - is it possible to allow longer port description that 26 chars (maybe 32)? I can see enough space for that on dashboard. Thanks.
Feature request - is it possible to allow longer port description that 26 chars (maybe 32)? I can see enough space for that on dashboard. Thanks.
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: v1.4.8rcX Bug reports and comments
IntL-Daniel wrote:Feature request - is it possible to allow longer port description that 26 chars (maybe 32)? I can see enough space for that on dashboard. Thanks.
We set this length a long time ago, changing this now could cause issues
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.
- IntL-Daniel
- Experienced Member
- Posts: 170
- Joined: Mon Nov 02, 2015 5:07 pm
- Location: Czech Republic
- Has thanked: 7 times
- Been thanked: 9 times
Re: v1.4.8rcX Bug reports and comments
here, curently only wrong release date :-)
v1.4.8rcX
Click HERE to download firmware v1.4.8rc3 - Released 5/11/2017
Click HERE to go to the thread on v1.4.8rcX to read other people's comments and questions.
About the length of port name - Ah I did not expect any issue about that... :-(
v1.4.8rcX
Click HERE to download firmware v1.4.8rc3 - Released 5/11/2017
Click HERE to go to the thread on v1.4.8rcX to read other people's comments and questions.
About the length of port name - Ah I did not expect any issue about that... :-(
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
v1.4.8rc4 Released
This version now has the long awaited calibration for DC switches to calibrate our voltage reading in dc input voltage.
v1.4.8rcX wrote:NOTE: MSTP is still being tested so use MSTP at your own risk.
FIXED/CHANGED
- Changed temp sensor readings on DC models to effect fan speeds - RC2
- Grey out unavailable bulk poe options - RC3
- Upper out of voltage range for IDC is now 54V - RC4
ENHANCEMENTS
- Added ERPS protocol implementation is g.8032v2 - Ring Protection - RC1
- Added BETA note to ERPS - RC3
- Added port name to "show interface status" CLI command - RC3
- ADD an input voltage calibration for DC models - RC4
KNOWN ISSUES
- Some language templates need help - please private message Eric Stern to help
v1.4.8rc1 Released 5/9/2017
v1.4.8rc2 Released 5/11/2017
v1.4.8rc3 Released 5/15/2017
v1.4.8rc4 Released 5/23/2017
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.
-
mayheart - Experienced Member
- Posts: 166
- Joined: Thu Jan 15, 2015 1:42 pm
- Location: Canada
- Has thanked: 43 times
- Been thanked: 40 times
Re: v1.4.8rcX Bug reports and comments
Not sure if this is a bug or just as intended from the hardware.
I had a laptop plugged into a mirror port, unfortunately the laptop got unplugged. After the battery drained, throughput went to almost nothing on the port that was mirrored. High latency as well to both the switch's management and device.
Removing the mirroring restored everything to normal operation.
I've been able to reproduce this on another switch running 1.4.7.
I had a laptop plugged into a mirror port, unfortunately the laptop got unplugged. After the battery drained, throughput went to almost nothing on the port that was mirrored. High latency as well to both the switch's management and device.
Removing the mirroring restored everything to normal operation.
I've been able to reproduce this on another switch running 1.4.7.
Who is online
Users browsing this forum: No registered users and 21 guests