Wireless Access

last person joined: 11 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Problem with Master <-> Local Communication

This thread has been viewed 0 times
  • 1.  Problem with Master <-> Local Communication

    Posted May 22, 2012 01:02 PM

    Hi.

    I have problems getting Master and Local communicating.

    Before i type in Master address on Local, ping and trace works, but once i type in ip and PSK to Master, and reboot, All communicaton stops.

    On local i can see traffic to Master:

    (mascotaruba02) #show datapath session | include 4500
    109.247.15.82   192.168.88.1    17   4500  4500   0/0     0 0   55  local       386  FY
    192.168.88.1    109.247.15.82   17   4500  4500   0/0     0 0   0   local       386  FC

     

    But on Master i see nothing.

     

    Nothing shows up in show crypto isakmp sa either.

     

    Any ideas?



  • 2.  RE: Problem with Master <-> Local Communication

    Posted May 22, 2012 05:54 PM

    Is there any firewall in between the master and local ?

     

    As per your previous message, the local is initiating the IPSEC tunnel. However master didn't receive it. Please check the intermediate devices to allow UDP 4500. Sniff  the packets on different hops and you can find , where the 4500 traffic is being dropped. 

     

     



  • 3.  RE: Problem with Master <-> Local Communication

    Posted May 23, 2012 02:21 AM

    The two Controllers is "attached" directly to the Internet.

    The only firewalls present is on the Controllers itselves..

     

    Vegard



  • 4.  RE: Problem with Master <-> Local Communication

    Posted May 23, 2012 12:04 PM

    Did you open all of these ports for controller to controller communication? This is from the user guide.

     

    Communication Between Aruba Devices

    This section describes the network ports that need to be configured on the firewall to allow proper

    operation of the network.

    Between any two controllers:

    􀁺

    IPSec (UDP ports 500 and 4500) and ESP (protocol 50). PAPI between a master and a local controller is

    encapsulated in IPSec.

    􀁺

    IP-IP (protocol 94) and UDP port 443 if Layer-3 mobility is enabled.

    􀁺

    GRE (protocol 47) if tunneling guest traffic over GRE to DMZ controller.

    􀁺

    IKE (UDP 500).

    􀁺

    ESP (protocol 50).

    􀁺

    NAT-T (UDP 4500).



  • 5.  RE: Problem with Master <-> Local Communication

    Posted May 24, 2012 02:32 AM

    Arent these ports default open on the master controller?

    Do i need to add a firewall policy on the port?

    No fw policy is selected now..

     

    Vegard



  • 6.  RE: Problem with Master <-> Local Communication

    EMPLOYEE
    Posted May 24, 2012 04:55 AM

    You should not have to open anything up in terms of the firewall.  It looks like you are pointing one controller to a private address.  What routing path would the traffic take in that circumstance and is being blocked from the public side?

     

     



  • 7.  RE: Problem with Master <-> Local Communication

    Posted May 24, 2012 05:01 AM

    Hi, i have changed some details now but it still wont work.

    This is the session output now from the local controller...

     

    (mascotaruba02) #show datapath session | include 4500
    109.247.15.82   95.34.70.39     17   4500  10000  0/0     0 0   0   local       cf58 FNY
    95.34.70.39     109.247.15.82   17   4500  4500   0/0     0 0   0   local       cf58 FSC

     

    Vegard



  • 8.  RE: Problem with Master <-> Local Communication

    EMPLOYEE
    Posted May 24, 2012 05:06 AM

    The source IP address of the traffic coming from the local is the "switch ip" or controller address.  Type "show switch ip" to determine what ip address the ipsec connection will be sent out of on the local controller.  If you ping or do traceroute, it normally goes out the egress interface, so where a ping might succeed, a master-local connection might fail, because it would be taking a different path.

     



  • 9.  RE: Problem with Master <-> Local Communication

    Posted May 24, 2012 10:33 AM

    ALso i see the traffic is getting source natted. can you please give us the output od show ip interface br and

    show controller-ip.

     

    show runn | in localip from master 



  • 10.  RE: Problem with Master <-> Local Communication

    Posted May 24, 2012 03:08 PM

    Local

    (mascotaruba02) #show running-config | include master
    Building Configuration...
    masterip 109.247.15.82 ipsec 5293af178aaa76fcb236bcdb27648003c69b26852b66cbc5

     

    Master

    (mascotaruba01) #show running-config | include localip
    Building Configuration...
    localip 0.0.0.0 ipsec e31ac2f12426982c530fb7b0d89142b62859be52d006614f
    localip 212.251.188.222 ipsec 2bfa6072fca70c4fbeb86ee3a9731ee745ac4ec6ec5845d3

     

    But when i portscan the master port 500 and 4500 is not showing as open..

    Is that right?

     

    Vegard



  • 11.  RE: Problem with Master <-> Local Communication

    Posted May 24, 2012 03:12 PM

    Master

    (mascotaruba01) #show ip interface br

    Interface                   IP Address / IP Netmask        Admin   Protocol
    vlan 102                 109.247.15.82 / 255.255.255.240   up      up
    vlan 1                    172.18.1.101 / 255.255.255.0     up      up
    vlan 250                172.18.250.254 / 255.255.255.0     up      up
    loopback                    unassigned / unassigned        up      up
    mgmt                        unassigned / unassigned        down    down

    (mascotaruba01) #show controller-ip

    Switch IP Address: 109.247.15.82

    Switch IP is configured to be Vlan Interface: 102

    Switch IPv6 address is not configured.

     

    Local

    (mascotaruba02) #show ip interface br

    Interface                   IP Address / IP Netmask        Admin   Protocol
    vlan 100                   212.251.188.222 / 255.255.255.0     up      up
    vlan 1                    192.168.88.1 / 255.255.255.0     up      up
    vlan 8                     172.18.81.1 / 255.255.255.0     up      down
    loopback                    unassigned / unassigned        up      up
    mgmt                        unassigned / unassigned        down    down

     

    (mascotaruba02) #show controller-ip

    Switch IP Address: 212.251.188.222

    Switch IP is configured to be Vlan Interface: 1

    Switch IPv6 address is not configured.

     



  • 12.  RE: Problem with Master <-> Local Communication

    EMPLOYEE
    Posted May 24, 2012 03:14 PM

    When you do a "show ip route" is the default gateway next hop a public address?

     



  • 13.  RE: Problem with Master <-> Local Communication

    Posted May 24, 2012 05:05 PM

    Also can you tell me what is this 95.34.70.39 Ip is ?

     

     


    (mascotaruba02) #show datapath session | include 4500
    109.247.15.82   95.34.70.39     17   4500  10000  0/0     0 0   0   local       cf58 FNY
    95.34.70.39     109.247.15.82   17   4500  4500   0/0     0 0   0   local       cf58 FSC