Wireless Access

How do I change the default gateway on the managed controller?

I tried local-config and it doesn't take the change.

Thank you

You would have to use disaster recovery mode:  https://www.arubanetworks.com/techdocs/ArubaOS_83_Web_Help/Web_Help_Index.htm#ArubaFrameStyles/1CommandList/disaster-recovery.htm

Of course if the config on the MM for that MD has the incorrect default gateway, it will be pushed back to the MD and you will lose connection again, so ensure the configuration for that MD is correct on the MM.

...aand turn of disaster recovery when it connects back again, so that it will sync with the MM.  Honestly, if you have console access to the MD, you should just do a factory reset (write erase all) and just reconnect using the full setup.  It will avoid you of having to deal with the quirks of disaster recovery.

I tried in disaster recovery and get an "Error: Deleting Default Route" and the change doesn't take.

Try adding the correct default gateway.

Has the controller ever connected to the MM?  If not, just do a write erase all and run the mini setup again. Disaster recovery mode has quite a few drawbacks.

I tried adding the correct default gateway and it doesn't take.  This is a new migration from 6.4.4.116 on a 7210 Mobility Controller to 8.3.0.1 and adding it to a new Virtual Mobility Master.  The migration got to 90% and then failed due to no connectivity.  

Not sure ho to run the mini setup and i don't know if the MM has all the config to pass down or how to initiate that if it does.

Is this a lab or production network?

The MM should have the entire configuration for that MD.  Please SSH into the MM and type "show configuration node-hierarchy" and see if there is an entry for the mac address of that MD.  Type cd <path to that md>  <enter>and then type "show configuration committed" to see the MD-specific configuration that MD would receive.  If that information is there, you could "write erase all" on the MD and run the full-setup to re-connect it to the MM.

There isn't anything that displays if I run "show configuration committed" for the file path of the controller.

Is there just an entry for that controller and no configuration?  At that level there should be minimum ip and interface configuration.

Does your MD that you can SSH into have any configuration?

I re-tried the command and here is what I got.  If I SSH into the MD it has full config from the migration.

(ArubaMM) *[PDPHE] #cd /md/Aruba/PDPHE/00:1a:1e:04:9b:b0
(ArubaMM) *[00:1a:1e:04:9b:b0] #show configuration committed
location "PDPHE 1st Flr MDF"
ip access-list eth validuserethacl
permit any
!
ip nat pool dynamic-srcnat 0.0.0.0 0.0.0.0
controller-ip vlan 1000
interface mgmt
shutdown
!
vlan 2
!
vlan 1000
!
ip default-gateway 10.100.0.1 1
kernel coredump
firewall
cp-bandwidth-contract trusted-ucast 65535
cp-bandwidth-contract trusted-mcast 3906
cp-bandwidth-contract untrusted-ucast 9765
cp-bandwidth-contract untrusted-mcast 3906
cp-bandwidth-contract route 976
cp-bandwidth-contract sessmirr 976
cp-bandwidth-contract vrrp 512
cp-bandwidth-contract auth 976
cp-bandwidth-contract arp-traffic 3906
cp-bandwidth-contract l2-other 1953
!

hostname "PDPHE 7210 Controller"
clock timezone MST -7

Is that default gateway correct?

Yes, it is.

So did the MD obtain an incorrect default gateway?

Not sure what happened in the migration.  The config came from a 3200xm controller that is going to be replaced by the 7210 and MM.  The 7210 on 6.4.4.16 was communicating just fine and the Migration Tool and worked correctly until the re-boot of the 7210 from 6.4.4.16 to 8.3.0.1.

Can you type "show switches" on the MM to see if that MD checked in correctly?

Also, if you SSH into the MD, see if the interface configuration is correct.  the 3200 has different interface naming than the 7210.

It only shows itself 

(ArubaMM) *[mynode] #show switches

All Switches
------------
IP Address IPv6 Address Name Location Type Model Version Status Configuration State Config Sync Time (sec) Config ID
---------- ------------ ---- -------- ---- ----- ------- ------ ------------------- ---------------------- ---------
10.110.1.115 None ArubaMM Building1.floor1 master ArubaMM-VA 8.3.0.1_65474 up UPDATE SUCCESSFUL 0 15

Total Switches:1
(ArubaMM) *[mynode] #

So that means that the md never successfully connected to the MM.

Is this a production network or a lab?  If it is a lab, we can try connecting the MD to the MM.

Lab only, at this point.  Won't migrate licenses until new AP's are installed and config for wireless is changed.

Do you have a large network and complicated configuration?  Some configurations do not survive the migration tool and it is suggested that the configuration be created manually.

Thank you for all the help!

I worked with TAC and was able to get the default-gateway changed.  Connectivity now works.

Sometimes its the simplest things.  I didn't realize i needed to write mem to get the gateway to change.  Who knew :)