Netonix Forums

Posted: **Wed May 10, 2017 1:28 pm**

Please post any questions or issues in this thread.

v1.4.8rcX now has ERPS. We do not suggest you use this in production until you have fully tested in in the lab and are satisfied with it.
The ERPS tab has online help (the question mark in the top right) which should give you all the information you need to get it configured and running.
The protocol implementation is g.8032v2.
I have done interop testing in my lab using a Juniper EX switch.

v1.4.7 wrote:NOTE: MSTP is still being tested so use MSTP at your own risk.

FIXED/CHANGED
- Fixed temp sensors showing crazy values in very cold environments
- Fixed getting "unexpected link change" messages due to port bounce, watchdogs, etc
- Fixed port bounce being 1 hour off after daylight savings time changes
- Fixed VLAN tab layout getting messed up when you delete a VLAN
- Fixed mac table refresh button causing entire page to reload
- Fixed problem with QinQ when using untagged VLANs
- Fixed fan control handling negative temperatures
- Fixed input voltage graph labels
- Fixed Apply/Save becoming active when looking at MSTP configuration even though nothing changed
- Fixed port number in log messages
- Fixed issue when importing config from a RevE board to a RevF with different POE port options. Affected WS-6 and WS-12
- Fixed the support for WS-8-150-AC
- Fixed console login
- Fixed/Force powerdown/powerup limits on WS-8-150-DC to help prevent switch lock up when draining battery to 9V
- Fixed DC2DC-500 detection for WS-26-500-DC
- Fixed voltage range on dumb DC models
- Fixed QinQ
- Fixed VLAN trunking
- Fixed Access Controls not honouring the Enable setting
- Fixed switch rebooting if multiple ports lose link too quickly
- Fixed multiple ports not turning off at the same time when they have the same shutdown voltage
- Fixed unexpected link change speed message
- Fixed port selection Tabs
- Fixed slight glitch in Input Current graph
- Fixed STP tab on 12 port models
- Fixes for WS-26-500-DC
- Fixed bulk editing Flow Control on Ports tab
- Fixed updating Watchdog description if port name is changed
- Fixed bulk editing on Power tab
- Allow QinQ and Double Tagging to be used with Trunk ports
- Changed UI layout on QOS tab
- Changed dumb DC models to temporarily disable POE when input voltage falls too low instead of disabling POE in the configuration
- Changed valid DC input voltage range to 9-72V in GUI for newer board revs
- Changed valid upper range for dc output voltage from 51V to 53V
- Changed input voltage graph to auto-scale
- Changed fan control to also use CPU and PHY temp
- Changed valid temp range on Status page meters
- Changed input voltage threshold where it forgets the configured Wake up voltage and defaults to 10V Wake up on WS-12-250-DC

ENHANCEMENTS
- Added MSTP
- Automatically disable flow control on ports using QOS bandwidth limits to prevent packet locks
- Added restart timer to DC power supply to help in very cold environments with cold starts
- Added log message when time is set by NTP after boot is finished
- Added logging when STP selects new root port
- Added POE startup delay option on Power tab
- Added root path cost on STP tab
- Added portDuplex SNMP stat from CISCO-STACK-MIB
- Added ifAdminStatus to SNMP stats
- Added support for new WS-26 models
- Added Double Tagged to VLAN configuration
- Added IP Protocol to QoS rules
- Added CIDR notation in QoS Source IP rules
- Added option to log web and ssh logins
- Added LLDP-MIB and CISCO-CDP-MIB to SNMP
- Added option to change MAC aging time
- Added "Disable Power" action to watchdog

KNOWN ISSUES
- Some language templates need help - please private message Eric Stern to help

Released 5/7/2017

v1.4.8rcX wrote:NOTE: MSTP is still being tested so use MSTP at your own risk.

FIXED/CHANGED
- Fixed input voltage reading on SMART DC models that may cause false ;pw input reading if voltage momentarily drop - RC12
- Fixed Changed temp sensor readings on SMART DC models to effect fan speeds - RC2
- Fixed SNMP support for Q-SWITCH-MIB, LLDP and CDP - RC7
- Fixed IGMP snooping with multiple VLANs - RC9
- Fixed DC calibration restarting POE - RC10
- Fixed problem with DHCP snooping affecting fragmented UDP packets - RC10
- Fixed problem with ERPS enabling forwarding a failed port - RC10
- Fixed problem with MSTP setting priority and path cost - RC10
- Fixed SSH login with RADIUS when the password contains special characters - RC11
- Fixed scheduled port bounce - RC11
- Fixed VLAN drag/drop being too sensitive - RC12
- 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
- Added an input voltage calibration for DC models - RC4
- Improved Q-BRIDGE-MIB support - RC5
- Improved fan control on DC models - RC6
- Improved stability of ERPS- RC6
- Added "Enable Power" action to watchdog - RC8
- Added ifMtu to IF-MIB - RC10
- Added dot3StatsDuplexStatus from EtherLike-MIB - RC10
- Added the time counters were cleared to port detail - RC10
- Added watchdog description to email notification - RC10
- Added terminal length option to CLI - RC10
- Added ability to re-order VLANs using drag and drop - RC10
- Enabled IGMP proxy for IGMP snooping - RC11
- Added "show igmp" CLI command - RC11

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
v1.4.8rc5 Released 5/26/2017
v1.4.8rc6 Released 6/7/2017
v1.4.8rc7 Released 6/17/2017
v1.4.8rc10 Released 9/10/2017
v1.4.8rc11 Released 9/22/2017
v1.4.8rc12 Released 10/18/2017

Posted: **Thu May 11, 2017 2:50 pm**

v1.4.8rc2 has been released to fix an issue for WS-8-150-DC units with temperature relating to power supply controller chip.
This could also affect WS-12-250-DC and WS-26-500-DC although never has been reported.

Posted: **Fri May 12, 2017 8:35 am**

Same PEM ID is accecpted if using same PEM ID on 2 PEM config, the status of the PEM is broken on one of the PEM configuration since it will show the PEM status of the other PEM config.

Also, is the're any way to configure a PIM if we don't want the port to be a end point ?

Posted: **Fri May 12, 2017 8:43 am**

Will also accept 2 MEP config on the same port that also break a little the status by reporting a Peer ID while CCM status is down.

Posted: **Fri May 12, 2017 10:03 am**

mike99 wrote:Also, is the're any way to configure a PIM if we don't want the port to be a end point ?

No, only MEPs are supported.

Posted: **Mon May 15, 2017 3:00 pm**

First, I'm not so familiar with ERPS but readed a lot about CMF an ERPS and also tryed several time.

My test are not conclusive at all. It's totally unreliable. If it work, I just have to unplug and plug back SFP and soon enough (2 or 3 trys), loop will happen and switchs reboot :-/ I started with a MEP instance but removed it to try if it would be more reliable. One good thing, even without MEP, it still converge really fast, ping won't even see a paquet lost.

My config is really simple:

VLAN 10, 20, 30, 40 and 4080 in monitor, management vlan 1 is exclude between 20 and 22 since it was worst when I tryed to include it. Often, switch will not even be reachable, even after a reboot.
Sometime, after change in VLAN or ERPS, the switch are not reachable at all, even after rebooting the switch. I'm not able to see any error, ERPS and STP (disable anyway) are in forwarding state but switch connected to it won't ping until I remove erps via the console port.

Exemple:

21# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
1 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 E E T T
4080 true E E E E E E E E E E E E T T
VLAN 1 IPv4 Address: 192.168.1.21/255.255.255.0
21# show erps
Instance 1
Level: 5
Control VLAN: 4080
Monitor VLANs: 10-4080
WTR Time: 1
Hold Off Time: 5
Guard Time: 500
RPL: West - Neighbor - Revertive
State: Protection
Priority Request: Signal Fail
Timer: None
East Peer (Port 14) State: Discarding
West Peer (Port 13) State: Forwarding
21# show st
status Show temperatures, CPU usage, memory usage, etc
stp Spanning Tree Protocol configuration/status
21# show interface status
Port Link PoE Watts
---- -------- ---- -----
1 Disabled Off 0.0
2 Disabled Off 0.0
3 Disabled Off 0.0
4 Disabled Off 0.0
5 Disabled Off 0.0
6 Disabled Off 0.0
7 Disabled Off 0.0
8 Disabled Off 0.0
9 Disabled Off 0.0
10 Disabled Off 0.0
11 Disabled Off 0.0
12 Disabled Off 0.0
13 1G
14 Down
21# show st
status Show temperatures, CPU usage, memory usage, etc
stp Spanning Tree Protocol configuration/status
21# show stp
Bridge ID : 32768.EC-13-B2-61-B4-5C
Instance: CIST
Root Bridge ID: 32768.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: 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
14 Forwarding
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
14 Forwarding
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# ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20): 56 data bytes
^C
--- 192.168.1.20 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
21# configure
21(config)# no erps instance 1
21(config)# exit
% Applying configuration...
Press ENTER to confirm configuration change. If you do not hit enter within 60 seconds the switch will revert to the previous configuration.
21# ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20): 56 data bytes
64 bytes from 192.168.1.20: seq=0 ttl=64 time=3.713 ms
64 bytes from 192.168.1.20: seq=1 ttl=64 time=1.018 ms
64 bytes from 192.168.1.20: seq=2 ttl=64 time=1.045 ms
^C
--- 192.168.1.20 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.018/1.925/3.713 ms
21# show mac
table MAC table entries/configuration
<cr> Press enter to execute the command.
21# show mac table
<cr> Press enter to execute the command.

21# show mac table
MAC Port VLAN Manufacturer Last IP
----------------- ---- ---- ------------ ---------------
00-0a-cd-2c-4c-a0 13 1 Sunrich Technology Limited Unknown
ec-13-b2-61-13-f6 13 1 Netonix Unknown
ec-13-b2-61-43-36 14 1 Netonix 192.168.1.22
ec-13-b2-61-43-4f 14 1 Netonix Unknown
21# show vlans
ID Enable Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14
---- ------ ----------- -- -- -- -- -- -- -- -- -- -- -- -- -- --
1 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
4080 true E E E E E E E E E E E E T T
VLAN 1 IPv4 Address: 192.168.1.20/255.255.255.0
20# show
accesscontrols Access Control entries
bounces Port bounces
config Show the currently running configuration
erps ERPS status
interface Interface status and configuration
lag Aggregation configuration/status
log Display system log
mac Mac Address Table information
qos QoS
status Show temperatures, CPU usage, memory usage, etc
stp Spanning Tree Protocol configuration/status
vlans VLANs
watchdogs Watchdogs
20# cmdline

BusyBox v1.19.4 (2017-03-07 13:42:37 EST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
admin@20:/www# ifconfig
eth0 Link encap:Ethernet HWaddr EC:13:B2:61:13:F6
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::ee13:b2ff:fe61:13f6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1309 errors:0 dropped:0 overruns:0 frame:0
TX packets:1650 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:102743 (100.3 KiB) TX bytes:1471623 (1.4 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
admin@20:/www#

Unrechable switch happen a lot on config change. ERPS even blocked the port 11 my PC is connected through while ERPS is not configured on this port :-/ Loop also happen a lot and crash switch that will reboot and be fine again until I plug and unplug the ports again. Not sure if it's happen only if the WTR timer is on. I will probably test this out.

Posted: **Mon May 15, 2017 4:23 pm**

Eric Stern wrote:
mike99 wrote:Also, is the're any way to configure a PIM if we don't want the port to be a end point ?

No, only MEPs are supported.

Would not be better to add MIP. From my reading, MIP should be use between nodes of same level while MEP should be use between nodes of differents levels or non CFM nodes. Seem like MIP need less planning since those don't seem to need a unique MPID like the MEP (MEPID).

Posted: **Mon May 15, 2017 5:07 pm**

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

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

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

Posted: **Tue May 16, 2017 9:32 am**

Infinite "config change reload interface" still happen on RC1. Had it at less 2 times will testing ERPS. Doing any change like change a port name and reload will fix it but without change, to reload interface will be ask every X seconds. Have seen this on Windows 7, Windows 10 and Linux Mint with Firefox and Chrome.

Posted: **Tue May 16, 2017 9:48 am**

I'm connected to switch 20 and can still access switch 22, connected through switch 21 (SFP between 20 and 22 disconnect), while 21 show west port (RPL neighbor) show discarding mode status.

You can view previous schema to understand better.

After I plug SFP between 20 and 22, everything status are shown fine with RPL owner (sw20 port 14 - est) and RPL neighbor (sw21 port 13 - west) showing discarding status).

Netonix Forums

v1.4.8rcX Bug reports and comments

v1.4.8rcX Bug reports and comments

v1.4.8rc2 Released

Re: v1.4.8rcX Bug reports and comments

Re: v1.4.8rcX Bug reports and comments

Re: v1.4.8rcX Bug reports and comments

Re: v1.4.8rcX Bug reports and comments

Re: v1.4.8rcX Bug reports and comments

v1.4.8rc3 Released

Re: v1.4.8rcX Bug reports and comments

Re: v1.4.8rcX Bug reports and comments