HPE Aruba Networking & ProVision-based
1847497 Members
6207 Online
110265 Solutions
New Discussion

2510(B/G)-24 problem with protected-ports (Am I missing something?)

 
maniac777
New Member

2510(B/G)-24 problem with protected-ports (Am I missing something?)

Hi,

 

I have some problems with protected-ports feature of 2510B-24 and 2510G-24. In the problematic part of network there is 2510G-24. In first port there is uplink to core of the network, ports 2-20 are "protected". In some of this ports I have microwave links where on the far end there is 2510B-24 with devices that use broadcast to discover each other. Microwave link on 2510B-24 is in port 24, and ports 1-23 are also "protected". Let say 2510G-24 is site "A", and 2510B-24 are sites B and C 

 

Problem:

I do not know why and how, but devices from site B on theirs auto-discovery list have devices from site C, but devices from site C know nothing about devices from site B. Autodiscovery list includes mac address of other devices. I've checked mac-address table of switch on site A and confirmed that devices are behind two different microwave links. I believe that somehow protected ports feature is allowing to pass broadcast in one direction and not by other. Is there any configuration option to allow/disallow that behavior?

 

Strange problem 2 (solved?):

For some time devices on site B also have on their auto-discovery list other devices from site B in other ports of 2510B-24. I checked few times and protected ports feature was on for all of them except one (uplink). Day before I noticed it I've changed some vlans and removed trunk. The problem is for me solved by doing:

no protected-ports 1-23

protected-ports 1-23

Bug in firmware? Or common (documented?) behavior?

 

Strange problem no 3 (solved?)

I've noticed before that protected-ports feature doesn't work on other 2510G-24. Port 25 and 26 were "protected", this ports there were configured 9 vlans, one untagged. One of the ports is downlink to Procurve 2626, and other to Procurve 2510G-24 (the one from site A in first, and my current problem). After a few hours of fighting with this switch I've changed all vlans to tagged, and problem disappeared

 

PS: All switches have newest firmware.