+ Reply to Thread
Results 1 to 2 of 2
  1. Junior Member Registered Member
    Join Date
    Jun 2013
    Posts
    2
    #1

    Default ap-manager i/f and management i/f on same port - why?

    Hello all,
    I have the following connected: http://i.imgur.com/boombMV.jpg
    Note that ds port 1 is connected. ds port 2 is disconnected.

    If I place the ap-manager interface on port 1 and the management interface on port 2, the LAP does NOT join the controller.
    Commands on the LAP were:
    capwap ap ip address 172.16.10.99 255.255.255.0
    capwap ap controller ip address 172.16.10.6
    I can ping from LAP to the controller (ping 172.16.10.6) and it works fine.

    When I place the management interface on port 1 and ap-manager on port 2, again, ap cannot join the wlc. I typed the following commands in the AP.
    capwap ap ip address 172.16.10.99 255.255.255.0
    capwap ap controller ip address 172.16.10.5 <-- note that I put the management ip address!
    When I type the above configuration, the ap is still looking for 172.16.10.6 - ap manager interface. Why?
    *Apr 29 00:05:39.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.6
    However, if I place both the manager interface and the ap-manager on the same interface (port 1) and type the above command:
    capwap ap ip address 172.16.10.99 255.255.255.0
    capwap ap controller ip address 172.16.10.6
    the LAP joins the controller. I think I am missing something fundamental. Any help would be appreciated.

    Reply With Quote Quote  

  2. Cisco R00t Clan Member NOC-Ninja's Avatar
    Join Date
    Feb 2011
    Location
    R00t
    Posts
    1,332

    Certifications
    CCIE-Wireless, CCIE-RS (written), CCNP-Wireless, CCNP, CCNA-Wireless, CCNA-Security, CCNA, CEH, CHFI
    #2
    What does debug say?
    MSISA
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks