Wireless Access

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

Configuring the MM port as an access or trunk port

This thread has been viewed 6 times

  • 1.  Configuring the MM port as an access or trunk port

    Posted Jan 03, 2020 02:05 PM

    My customer installing MM-VA-500 on two different esxi hosts. He followed the video on ABC, but on that video, Herman states that when going through the inital set up of the MM, to make the interface a trunk instead of access. Since the MM is only managing the controllers, should we just make the port on the MM an access port? What would be the reason to make it a trunk port? The MM will be managing a pair of 7205 controller initially.

     

    Thanks,

    Steve



  • 2.  RE: Configuring the MM port as an access or trunk port

    MVP EXPERT
    Posted Jan 03, 2020 02:50 PM

    Only one access interface should be fine. Allmost all of my mm-va configuration iam using only a access interfaces for the mobility master.

     

    One reason for create a trunk with vlan tagging could be thats more easy to add vlans when its needed, but so far in non of my setups i had to add an extra vlan for the mobilty master.