UNSOLVED

superhmc

updated

20 years ago

S

superhmc

7 Posts

0

11497

April 20th, 2006 23:00

Isolate ports.....for PowerConnect 5324

My problem:
 
We have a Powerconnect 5324 and I need to partition the ports so that HALF are on their own network and the other half is on another, but they cannot directly interact with each other.
 
I would like to make it so they are operating as if they are on two entirely separate switches even though they are physically not.
 
How do I do that?
 
Any help would be appreciated. Thanks in advance.
 
 
  • Adam N

    2 Intern

    128 Posts

    874

    0

    Posted April 21st, 2006 08:00

    Hi

    I think what your referring to is a feature called Private VLAN Edge, which is a feature available on the PC6024 switches, but not on the 5324. With the Private VLAN feature you can configure protected ports. A protected port does not forward any traffic (unicast, multicast, or broadcast) to any other port that is also a protected port in the same switch. Traffic cannot be forwarded between protected ports at Layer 2, all traffic passing between protected ports must be forwarded through a Layer 3 (L3) device.

    Now, as I said unfortunately this feature is not available on the PC5324 but depending on what you want you could do the following:

    1. Assign ports 1-12 into VLAN10
    2. Assign ports 13-24 into VLAN20


    This would effectively split the switch into 2 networks, and if you do not have any Layer3 device routing between these vlans they are isolated from each other, but maybe this is not what your looking for, if you could provide a little more detail I might be able to help further.

    Hope this helps
  • superhmc

    7 Posts

    874

    0

    Posted April 21st, 2006 13:00

    "1. Assign ports 1-12 into VLAN10
    2. Assign ports 13-24 into VLAN20"
     
    Ill see if I can elaborate better. Thanks for the input =-).
     
    We have two networks. 10.1.1.x and 10.100.1.x
     
    One of our other 5324 is FULL of 10.1.1.x traffic, all 24 ports are being used for 10.1.1.x
    I would like to take the runover and only use PART of the second 5324 for 10.1.1.x traffic, but also start entirely NEW traffic on it of 10.100.1.x for the other 12 ports.
     
    Assumptions
    1. We only have 5324 switches.
    2. Traffic is coming from a watchguard box.
    3. 10.1.1.x traffic should not be able to ping or flow to 10.100.1.x
     
    Example:
    So 10.1.1.x traffic would be on 1 1/2 - 5324 switches. 36 ports
    and 10.100.1.x would be on 1/2 - 5324 switches. 12 ports
     
    Thank you.
  • Adam N

    2 Intern

    128 Posts

    874

    0

    Posted April 24th, 2006 08:00

    Hi

    I think your idea will work as long as you do not want any of your clients in the 10.100.1.x subnet to be able to communicate to any other subnet. So for example, lets assume your existing PC5324 is configured in the following way:-

    PC5324-1 - VLAN100 - 10.1.1.x


    Now on the second PC5324, you only need to do the following:-

    1. Create VLAN100
    2. Assign ports 1-12 to VLAN100
    3. Create the L3 VLAN100 interface and assign an IP address in the 10.1.1.x range.
    4. Leave ports 13-24 in VLAN1 these can be used for your 10.100.1.x subnet.
    5. Connect your PC5324-2 switch to the first switch using a port which is a member of VLAN100.

    And that should be it, any client in the 10.1.1.x subnet on either switch should be able to communicate. Anything in the 10.100.1.0 subnet will be able to communicate within the VLAN but not to any other subnet.

    Hope this helps.