Wireless Access

last person joined: 22 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Trunked port vs each vlan on its own port

This thread has been viewed 0 times

  • 1.  Trunked port vs each vlan on its own port

    Posted Nov 28, 2011 05:31 PM

    Hello everyone, 

     

    We have 4 vlans on our network,  and a 3400 controller,  so 4 ports total.     Is it better as far as performance is concerned to trunk all 4 vlans to one port,   or to put each vlan on its own port?     I assume each to its own port would help remove a bottleneck,  but i'm wrong quite often! 

     

    Thanks

     

    Brandon


    #3400


  • 2.  RE: Trunked port vs each vlan on its own port

    EMPLOYEE
    Posted Nov 28, 2011 09:39 PM

    Measure the utilization on that port and you would be suprised at the answer.



  • 3.  RE: Trunked port vs each vlan on its own port

    Posted Nov 29, 2011 03:11 AM

    I'd recommend both assuming your switches are of a good new and solid type. Assuming your switches support it, create a port-channel, aggregate all four ports together and trunk/vlan-tag the connection as a whole. Best of both plus resilient to port failure!

     



  • 4.  RE: Trunked port vs each vlan on its own port

    Posted Nov 29, 2011 08:38 AM

    Switch should support just about anything,  its a HP procurve 5406_zl.    Does the aruba 3400 controller support link aggregation?   Didn't see any options for it.   



  • 5.  RE: Trunked port vs each vlan on its own port

    EMPLOYEE
    Posted Nov 29, 2011 08:42 AM

    Yes.  Please search the user guide for link aggregation.

     

     

     



  • 6.  RE: Trunked port vs each vlan on its own port

    Posted Nov 29, 2011 10:18 PM

    See the Appendix in campus VRD availabel at www.arubanteworks.com/vrd