Wireless Access

last person joined: 19 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

Aruba Controller Physical Connection and Network Latency/ Saturation

This thread has been viewed 4 times

  • 1.  Aruba Controller Physical Connection and Network Latency/ Saturation

    Posted Jul 31, 2012 10:37 AM

    Hi,

     

    We have a 6000 controller with an M3 card. As of now, 1 gigabit port is connected to our wired network through a trunk port. The controller is a master and there are about 30 APs currently terminated to it. We are planning to place 100+ more APs. We are planning to use the 10Gb port in the future but I am wondering what commands or paramters should we be looking at to see if the 1 Gb port we have is currently functioning properly without saturation or dropping packets? Thanks.

     

     



  • 2.  RE: Aruba Controller Physical Connection and Network Latency/ Saturation

    Posted Jul 31, 2012 11:03 AM
    show interface gigabitethernet <slot/port>
    show port link-event


  • 3.  RE: Aruba Controller Physical Connection and Network Latency/ Saturation

    Posted Aug 17, 2012 01:18 AM

    We will have about 150 APs in a campus deployment with a master controller. We are wondering how many 10GB or 1GB ports should be use as members of a port channel to trunk to our switch to avoid any congestion. How do you guys usually connect the controller to your switch/ router. Do you usually use a port channel and add all ports to this port channel? Or do you only use a few ports added to the port channel?



  • 4.  RE: Aruba Controller Physical Connection and Network Latency/ Saturation

    Posted Aug 17, 2012 01:44 AM

    I typically (as in 95% of the time)  run with two 1Gbps interfaces in aggregation mode.

     

    That provides, under normal conditions, up to 2 Gbps of throughput... and also resiliancy against any one port/SFP/Cable issue.

     

    Haven't seen this 'bottle neck' a deployment yet... e.g. haven't found the need to light up other ports in aggregation mode in the vast majority of deployments.