Wireless Access

last person joined: yesterday 

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

After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

This thread has been viewed 0 times

  • 1.  After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    Posted Jun 17, 2014 09:02 PM

    After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work as it did on our M3 controller. on the M3 we could use the enet1 port to attach additional pieces of equipment to draw an IP address such as a PC or networked printer. The configurations on the M3 and the 7220 are the same yet it does not work on the 7220. Any ideas?


    #7220


  • 2.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    Posted Jun 17, 2014 09:13 PM

    Check that the e1 port configuration is not shutdown 

     

    2014-06-17 21_12_14-AP Group.png


    #7220


  • 3.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    Posted Jun 17, 2014 11:10 PM

    turns out that is not the problem.  the box is not checked. Anything else you can think of? I have looked at the entire config and can't see where there may be a problem.


    #7220


  • 4.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    Posted Jun 18, 2014 05:05 AM
    Is the wired ap profile enabled ? If it is disable it
    #7220


  • 5.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    EMPLOYEE
    Posted Jun 18, 2014 05:30 AM
    @dano2015 wrote:

    turns out that is not the problem.  the box is not checked. Anything else you can think of? I have looked at the entire config and can't see where there may be a problem.

    Dano2015,

     

    What version of ArubaOS and how are you powering those AP125s?

     


    #7220


  • 6.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    Posted Jun 18, 2014 08:19 AM

    We are using ArubaOS 6.3.1.5 and an Aruba 1 Port GE 802.3at Midspan injector to power the 125 and the 225.



    #7220


  • 7.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    EMPLOYEE
    Posted Jun 18, 2014 08:21 AM

    You should:

     

    - Get a console cable and look at the AP125 bootup to see if it is enabling that second port

    - Make sure that the injector is plugged into enet0

     

     


    #7220


  • 8.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    Posted Jun 18, 2014 03:34 PM

    Enet1 does show to be enbled during the bootup but we still cannot get an ip address through that port. the injector is plugged into enet0. ???????


    #7220


  • 9.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    EMPLOYEE
    Posted Jun 18, 2014 04:29 PM

    When you plug in devices, do they even get a link?  If not, you should open a TAC case to get to the bottom of this.  We would ask for screenshots of your AP wired profile in that AP-Group for enet1..

     


    #7220


  • 10.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    Posted Jun 18, 2014 04:36 PM

    We do get a link light when the device is plugged in, just doesn't get an IP address. I just opened a TAC to see if Aruba can resolve this issue for me. Thanks for all your assistance.


    #7220


  • 11.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    EMPLOYEE
    Posted Jun 18, 2014 04:48 PM

    What you can do is turn on DHCP debugging to see why those devices are not getting an ip address:

     

    configure t
logging level debugging network process dhcpd subcat dhcp

     Plug in your device, then after a few seconds, type "show log network 50" to see if it is indeed sending out DHCP request and on what VLAN.


    #7220


  • 12.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    Posted Jun 21, 2014 11:24 PM

    following the thread to see, where it shall end.. 


    #7220


  • 13.  RE: After changing to our new 7220 controller our enet1 port on our AP-225's and AP-125's does not work.

    Posted Dec 19, 2014 02:50 AM
    @dano2015, the issue got resolved?
    #7220