Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

14150

August 30th, 2010 03:00

dell 5224 vlan segmentation

Hello,

at work we use dell powerconnect 5224 and have 2 class C networks in one big broadcast domain.

We need to make segmentation on the broadcast domain. But as i read im not sure do 5224 can make this segmentation inside it without to reconfigure our router because alot of our costumers have static network settings.

Do the pvlan is the only one solution to make this segmentaton and do our 5224 support it. Our firmware version is 3.1.0.16.

The idea is for example 20 port's that can look and communicate with router port but cant communicate with each other directly. I cant make separate vlan with different gateway for every vlan inside our router because the network ip range is public and static.

Any other sulutions are welcome.

Thanks in advance

Marko

909 Posts

September 1st, 2010 10:00

what you want is the private vlan feature.   THis switch does not have this feature. 

If you want a hack, look at this for an example.

http://en.community.dell.com/support-forums/network-switches/f/866/p/19336276/19711446.aspx#19711446

 

2 Posts

September 6th, 2010 00:00

Thanks bh for your direction for private vlans and your example, i represent it and for me it work in another way.

vlan database
 vlan 1 name DefaultVlan media ethernet state active
 vlan 100 name priv100 media ethernet state active
 vlan 102 name priv102 media ethernet state active
 vlan 103 name priv103 media ethernet state active
 vlan 104 name priv104 media ethernet state active
 vlan 105 name priv105 media ethernet state active
 vlan 106 name priv106 media ethernet state active
 vlan 107 name priv107 media ethernet state active
 vlan 108 name priv108 media ethernet state active
 vlan 109 name priv109 media ethernet state active
 vlan 110 name priv110 media ethernet state active
 vlan 111 name priv111 media ethernet state active
 vlan 112 name priv112 media ethernet state active
 vlan 113 name priv113 media ethernet state active
 vlan 114 name priv114 media ethernet state active

!
interface ethernet 1/1
 switchport allowed vlan add 100 untagged
 switchport native vlan 100
 switchport allowed vlan remove 1
!
interface ethernet 1/2
 switchport allowed vlan add 100,102 untagged
 switchport native vlan 102
 switchport allowed vlan remove 1
!
interface ethernet 1/3
 switchport allowed vlan add 100,103 untagged
 switchport native vlan 103
 switchport allowed vlan remove 1
!
interface ethernet 1/4
 switchport allowed vlan add 100,104 untagged
 switchport native vlan 104
 switchport allowed vlan remove 1
!
interface ethernet 1/5
 switchport allowed vlan add 100,105 untagged
 switchport native vlan 105
 switchport allowed vlan remove 1
!
interface ethernet 1/6
 switchport allowed vlan add 100,106 untagged
 switchport native vlan 106
 switchport allowed vlan remove 1
!
interface ethernet 1/7
 switchport allowed vlan add 100,107 untagged
 switchport native vlan 107
 switchport allowed vlan remove 1
!
interface ethernet 1/8
 switchport allowed vlan add 100,108 untagged
 switchport native vlan 108
 switchport allowed vlan remove 1
!
interface ethernet 1/9
 switchport allowed vlan add 100,109 untagged
 switchport native vlan 109
 switchport allowed vlan remove 1
!
interface ethernet 1/10
 switchport allowed vlan add 100,110 untagged
 switchport native vlan 110
 switchport allowed vlan remove 1
!
interface ethernet 1/11
 switchport allowed vlan add 100,111 untagged
 switchport native vlan 111
 switchport allowed vlan remove 1
!
interface ethernet 1/12
 switchport allowed vlan add 100,112 untagged
 switchport native vlan 112
 switchport allowed vlan remove 1
!
interface ethernet 1/13
 switchport allowed vlan add 100,113 untagged
 switchport native vlan 113
 switchport allowed vlan remove 1
!
interface ethernet 1/14
 switchport allowed vlan add 100,114 untagged
 switchport native vlan 114
 switchport allowed vlan remove 1
!
interface ethernet 1/15
 switchport allowed vlan add 100 untagged
 switchport native vlan 100
 switchport allowed vlan remove 1
!
interface ethernet 1/16
 switchport allowed vlan add 100,102-114 untagged
 switchport native vlan 100
 switchport allowed vlan remove 1
!
interface ethernet 1/17
 switchport allowed vlan add 1 untagged
 switchport native vlan 1
!
interface ethernet 1/18
 switchport allowed vlan add 1 untagged
 switchport native vlan 1
!
interface ethernet 1/19
 switchport allowed vlan add 1 untagged
 switchport native vlan 1
!
interface ethernet 1/20
 switchport allowed vlan add 1 untagged
 switchport native vlan 1
!
interface ethernet 1/21
 switchport allowed vlan add 1 untagged
 switchport native vlan 1
!
interface ethernet 1/22
 switchport allowed vlan add 1 untagged
 switchport native vlan 1
!
interface ethernet 1/23
 switchport allowed vlan add 1 untagged
 switchport native vlan 1
!
interface ethernet 1/24
 switchport allowed vlan add 1 untagged
 switchport native vlan 1
!
!
!
interface vlan 1
 ip address 192.168.1.2 255.255.255.0

port 1 - server port

port 15-16 with cable interconnected

in this situation i cant see computers in ports 2-14

If i remove cross cable from port 15-16 and put server on port 16 i can see (ping) all ports 2-14

can all computers work normal if server port is on 16 and in one direction information from computers come on individual vlan with server and server reply on vlan 100 ?

909 Posts

September 7th, 2010 08:00

If the behaviour is what you want, then this will work (and it saves you 2 ports).

The behaviour is:

port g16: broadcast traffic goes to ports 1-15, server MAC is learned on native vlan (VLAN 100)

ports 1-15: broadcst traffic from each port only goes to port g16, MAC is learned on native vlan for that port.

 The only downside here is that the switch does per vlan learning.  So this means that if you had multiple ports configured like port g16, these ports would always see all the traffic in all the vlans. 

The loopback between g15 and g16 was supposed to avoid this, but I do not think the example is correct as it creates a loop in vlan 100.  For you implementation, port 15 and 1 should have been an access port in some other vlan, say 101.  Also, you would have to turn off spanning tree on ports g15 and g16.

No Events found!

Top