Wireless Access

 View Only

  • 1.  AP 635 vlan

    Posted Sep 03, 2025 03:09 PM
    Edited by Russ_Altorfer Sep 03, 2025 03:29 PM

    Hey all, 

    So this is probably going to be a simple question and answer, and I am probably going to have a face palm moment once I figure it out. 

    I have 19 635 APs not getting the right vlan configuration. The way that we have our network setup is the 3rd octet is designated for the vlan, ie: 10.80.<vlan>.<host> .  The vlan that we are using is 32 for our AP vlan. These APs are connected to a switch that in the past has been a L2 switch. My boss has done the provisioning of the APs but he is telling me that they are not getting the right network or vlan. We want them to get an ip address of 10.80.32.xx and they are only getting a 10.151.89.xx . I have been trying to troubleshoot this and he is saying that with 99% accuracy that it is an issue between whether or not the ports are setup as access ports or trunk ports.

    The port in the MDF that my provisioning switch is connected to is setup as an access port, and then through a trunked LAG back into the network. The ports on the provisioning switch are all set to the default. 

    I do not know if I need to extend the access configuration to the ports on the provisioning switch? My other option is to change the port on the MDF to a trunk port and then the ports on the provisioning switch to access. Am I on the right track? Is there something I am missing?

    I have tried to extend the access vlan to the provisioning switch. When I plug my computer into the switch the computer still gets a 10.151.89.xx ip address. I apply a static IP address to the ethernet port on my computer within the network and try to ping the gateway of 10.80.32.1 and I get a host unreachable. Is this because I have no routing on the ports and that is blocking it?



    -------------------------------------------



  • 2.  RE: AP 635 vlan

    Posted Sep 03, 2025 06:44 PM

    generally the switch ports that APs connect to should be a trunk port and the native VLAN is the VLAN that the APs will get their IP addresses from. So in your case the switch port should be configured as VLAN trunk and the native VLAN should be VLAN 32.

    then the access switch switch should also have a uplink VLAN trunk port to the core switch , etc.



    ------------------------------
    If my post was useful accept solution and/or give kudos.
    Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
    ------------------------------



  • 3.  RE: AP 635 vlan

    Posted Sep 04, 2025 09:27 AM

    Ok, if I am understanding you correctly this is how things should be configured. This is going to be in on an Aruba 6300, and 6410 for the MDF.

    PROVISIONING SWITCH
    All ports have vlan access 32

    MDF SWITCH
    Port for provisioning switch with;
    vlan trunk native 32
    vlan trunk allowed <all, or any vlans that we need>

    Is this correct?

    -------------------------------------------

    Original Message


  • 4.  RE: AP 635 vlan

    Posted Sep 05, 2025 01:00 AM

    not exactly, if the APs are connected to CX6300 switch then the switch ports that connect to the APs should be in trunk mode.

    here is the sample

    ===6300====

    interface 1/1/1
        description access-point
        no shutdown
        no routing
        vlan trunk native 32
        vlan trunk allowed all

    interface 1/1/48
        description uplink
        no shutdown
        no routing
        vlan trunk native 32
        vlan trunk allowed all



    ------------------------------
    If my post was useful accept solution and/or give kudos.
    Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
    ------------------------------

    Original Message


  • 5.  RE: AP 635 vlan

    Posted Nov 21, 2025 01:01 PM

    I know it is a bit late, but I figured out the issue. Our documentation was wrong and I was using the wrong wall port. After I used a toner I figured out that it was the wrong port. Once I got connected to the correct port things got to working.

    -------------------------------------------

    Original Message


Related Content