Wireless Access

Reply
Guru Elite

Re: Configure Controllers from 1 Location and move to a different Location

Again, please reach out to your Aruba Sales Engineer so that you can deploy your network in the most efficient manner.  At this point, the strategy to deploy should be fully understood so that deployments at remote sites would be fairly straightforward.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
Regular Contributor I

Re: Configure Controllers from 1 Location and move to a different Location

I like that idea of pushing the configuration to the folder.

 

Some of the required configuration will be done on the MM - MN - Folder/Group - MD level (Such as assigning an IP address for a VLan to this specific MD and a different IP address to another MD in that fsame older).

 

But a lot can be done from the folder level. 

 

Then I can bring up the Controllers in stand alone mode instead of MD and upgrade the OS that way.  Then do a >write erase<enter> and >halt<enter>

 

I still want to add the local user accounts on the controller ahead of time and tht is why I thk the >write erase<enter> may work better fo me instead of >write erase all<enter>. 

 

This has been a very usefull and benefitial question.

Guru Elite

Re: Configure Controllers from 1 Location and move to a different Location

What local user accounts?

 


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
Guru Elite

Re: Configure Controllers from 1 Location and move to a different Location

Please contact your Aruba SE or a VAR to help you.  I am afraid that I am giving you advice without context that could be harmful instead of helpful in the long run.

 

You really should ship the controller to the site and provision/upgrade it there.  No need to configure the MD as standalone.  No need to do a wirte erase all. You can add a MD to an MM as long as the MM has newer code than the MD.  You would then upgrade the firmware on the MD and then you would be fine at the remote site.  You would typically add the licenses/license pools to the MM so that another MD would automatically take licenses from the pool on the MD, so no need to install those.  

 

There is no advantage to staging the MD at HQ.  I apologize for giving you that advice.

 

 


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
Highlighted
Regular Contributor I

Re: Configure Controllers from 1 Location and move to a different Location

You have been helpful Cjoseph,

 

1.  The user accounts to be used are regarding the 2-factor Authentication that we use with MAC addresses. 

    a.  We have a few deives that are specific to the location and we want to use MAC Authetication in addition to a password.  

    b.  It is working well with our already deployed Aruba wireless sites and it was in place with the previous Wireless system.

 

2.  If we have limited time to get things done at a location having the controllers already upgrded before hand will help.

     a.  Also having the MAC addresses entered ahead of time will help as well.

 

3.  My manager is insisting I do this and I do not want to disspoint in my preparation.

Regular Contributor I

Re: Configure Controllers from 1 Location and move to a different Location

This was a valuable discussion and helpful in preparing for the setup.  I will try to verify my plan with a more experience ARuba Engineer that has actually done this before.

 

Thank you for your time.  My plan now is:

 

 


1. It is stated that it would be best not to update the AP's before you arrive at the location.
a. At another lcoation the AP-345's came with version 8.0 and when they connected they were already in Campus mode (not Instant mode) and tehyupdated automatically to the version teh controlelr was on (8.3).

b.  It took about 2 minutes adn 50 seconds per AP.

c.  Only connect the new AP's to the network after the new controllers are on-line on that VLan.


2. Connect each new local Controller and set it up in a Standalone Mode with a temporary IP address when at the HQ Site.
a. Update the version of the MD operating system.
b. I would image that I can use the web UI to do this as well.

 

3. Setup any local user accounts on the Standalone local controllers that are necessary
a. Setup the guest local user account.
b. Verify that it can boot up correctly and be accessible from the web UI and putty.


4. Document the Aruba controller MAC addresses Assocaited with the HOSTNAME.
a. One will need to refer to that later.


5. Create the appropriate MD-Groups in the MM, below the Manged Network section.
a. Add the necessary onfiguraitons on teh group level.
b. I will not be able to do everything but it wil lbe a good start before arriving at the final location.

 

6. Then, disconnect the controllers from HQ network and connect to the controller from console connection.
a. Execute>wite erase<enter> from the local controllers.
b. Then execute >reload<enter>.
c. Now enter the Destination Hostname and IP and information.
d. Make sure you have a good record of the Hostname and its MAC address.
e. Verify that all of the local user accounts are still there after the write erase.


7. Then ship the controllers to their final destination.
a. Then when on site, connect to the controller via console port.
b. Power on the controller to verify the IP information or setup the information.
b. Then start continuous pings and plug in the controller to the network and verify lnetwork communciation.
c. Verify that communication works and that you can login locally via putty and web ui.


8. Then navigate to the MM's Web UI - MM - Configuration - Controllers and add the new controllers IPsec tunnel information.
a. Try restarting the MD and verify the communications works as expected.
b. Then add the controller to the correct MD Group.
c. The MM will try to propagate the configurations that were in place earlier.
d. Monitor the progress.



 

 

Regular Contributor I

Re: Configure Controllers from 1 Location and move to a different Location

The plan of setting up the controllers initially in 'StandAlone' mode worked very well.

 

That allowed me to upgrade the firmware version and then I was able to assign the final destination IP address and gateway for teh remote site.

 

I eventually shipped the controllers to the final desination and verified the IP address while on-site and then racked and connected the controllers while I was on site.

 

The controllers were immidately on-line and I then configured the MM to synch with the new controllers.  After the MM recongized and was abel to communicate with the local controllers I added the new local controllers to the MD groups from the Mobility Master Web UI.

 

Then all of the inhertited configurations from the MD grop were saved to the new local controlelrs and I was abel to maek new configuraiton changes to those controllers. 

 

The above mentione plan provided by Cjospeh worked like a champ and saved some inital setup time when it really mattered.  The main time saved was from updating the firmate on the controllers.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: