Wireless Access

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

Controller Possible Routing Issue

This thread has been viewed 2 times

  • 1.  Controller Possible Routing Issue

    Posted Dec 07, 2016 06:48 AM

     We have a master controller that has two interfaces enabled one goes to the LAN and one is connected to a DMZ for Guest access and RAPs this has worked great for the past couple of years but in the past couple of weeks we've started getting issues with RAPs tasking 20 minutes to connect to the controller and clients unable to connect to the SSIDs broadcast by the RAPs, this is intermittant.

    Also our Guest access intermittantly slows to a crawl and can take the best part of 5 minutes to open a web page on a client or timesout altogether.

    There's no errors as far as we can see in the logs but going through various different troubleshooting steps we noticed the routing table on the controller has two default gateways and lots of statics and would like to know if this could be causing the issues we're seeing, the 172 networks are on the DMZ and the 10 and 192 are on the LAN.

     

     

    Codes: C - connected, O - OSPF, R - RIP, S - static
    M - mgmt, U - route usable, * - candidate default, V - RAPNG VPN/Branch

    Gateway of last resort is Imported from DHCP to network 0.0.0.0 at cost 10
    Gateway of last resort is Imported from CELL to network 0.0.0.0 at cost 10
    Gateway of last resort is Imported from PPPOE to network 0.0.0.0 at cost 10
    Gateway of last resort is 172.16.0.1 to network 0.0.0.0 at cost 1
    Gateway of last resort is 10.169.231.1 to network 0.0.0.0 at cost 1
    S* 0.0.0.0/0 [1/0] via 10.169.231.1*
    [1/0] via 172.16.0.1
    S 10.103.12.0/23 [1/0] via 10.169.231.1*
    S 10.169.192.0/19 [1/0] via 10.169.231.1*
    S 10.169.224.0/21 [1/0] via 10.169.231.1*
    S 10.169.232.0/21 [1/0] via 10.169.231.1*
    S 10.169.240.0/20 [1/0] via 10.169.231.1*
    S 10.170.0.0/19 [1/0] via 10.169.231.1*
    S 10.170.32.0/21 [1/0] via 10.169.231.1*
    S 10.170.64.0/19 [1/0] via 10.169.231.1*
    S 10.170.96.0/19 [1/0] via 10.169.231.1*
    S 10.231.216.0/21 [1/0] via 10.169.231.1*
    S 192.168.0.0/16 [1/0] via 10.169.231.1*
    C 10.169.231.0/24 is directly connected, VLAN7
    C 10.170.100.0/22 is directly connected, VLAN250
    C 10.169.230.0/25 is directly connected, VLAN202
    C 172.30.0.0/22 is directly connected, VLAN66
    C 192.168.68.0/22 is directly connected, VLAN205
    C 10.170.108.0/22 is directly connected, VLAN206
    C 10.170.106.0/25 is directly connected, VLAN303
    C 172.16.0.0/25 is directly connected, VLAN4000
    C 172.30.30.0/23 is directly connected, VLAN1000
    C 172.30.32.0/23 is directly connected, VLAN1001
    C 172.30.34.0/23 is directly connected, VLAN900

    Any help would be much appreciated.

     

    Thanks

     

    Jon

     



  • 2.  RE: Controller Possible Routing Issue

    EMPLOYEE
    Posted Dec 07, 2016 06:50 AM

    If you haven't already, please open a TAC case.  Intermittent issues are very complicated and require looking at a great deal of data.  To answer the question, having a large routing table typically does not slow down the controller.