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

MM managed MD don't follows default gateway

This thread has been viewed 7 times

  • 1.  MM managed MD don't follows default gateway

    Posted Oct 23, 2020 07:21 AM

    Hey!

     

    I had an intresting problem today, which I observed the first time.

    A customer owns a mobilty master deployment with 3x 7030 controllers as cluster.
    Code: 8.6.0.6

     

    We got one controller from our distributor on 8.3.x code.
    After the initial setup, the controller was online and rechable over L3 (routed from another network via TCP/22).

     

    After this, we upgraded the controller directly to 8.6.0.6.
    Since this action, the controller was not able to follow the default gateway.
    The default gateway was configured properly.
    (ctrl)# ip default-gateway 10.x.x.x

     

    We do not get the controller to use the default gw as next hop until we set the default gw with the command 

    "(MM) [folder] (config) #ip route 0.0.0.0 0.0.0.0 x.x.x.x"

     

    Obviously, there is also a GUI bug in this release which marks the destination network mask "0.0.0.0" as invalid.
    You are forced to use the cli at this point to add a default rout....
    GUI_BUG_defaultroute.JPG
    If you set the default route over cli, the route will show up with the wildcard mask in GUI.

     

    Does anybody observe this behaviour before?

    I would have to check other installations, but I think in the past controllers followed the default gateway if there was no expicit route set to another GW....

     

     



  • 2.  RE: MM managed MD don't follows default gateway

    EMPLOYEE
    Posted Oct 23, 2020 09:10 AM

    I have never used anything besides the ip default-gateway command and it has worked.  "show ip route" on the cli might give you an idea what is going on here.



  • 3.  RE: MM managed MD don't follows default gateway

    Posted Oct 23, 2020 10:25 AM

    I agree with you!

     

    Before we added the default route (ip route 0.0.0.0 0.0.0.0 x.x.x.x),
    the "show ip route" command, only throw out the local connected route and the ipsac map to the MM.
    In spite of correct default-gateway config....

     

    A support case might be good.

     



  • 4.  RE: MM managed MD don't follows default gateway
    Best Answer

    Posted Oct 31, 2020 04:31 PM

    Update ....

    We have decided not to investigate the issue any further...

    I think this was an individual issue in connection with the update step that we took and the existing configuraiton..

    Our solution was to set a default route wit the command #ip route 0.0.0.0 0.0.0.0 x.x.x.x.

    Thats fine for us.


    Regards



    ------------------------------
    Matthias Moritz
    ------------------------------

    Original Message