Wireless Access

Update on situation:

We ran a show run in the CLI of both controllers and compared their configurations and shared keys. We found that the IKE Shared Key was mismatched from one controller to another. Once fixing that, we also noticed in our VIA Connection Profile we did not have the VIA Authentication Profile defined. After completing that and saving the config, we were able to get this to work.

Problem is solved.

Our current problem is that we cannot change VIA connection profiles and succesfully connect. 

Background information:

Active-Master & Backup-Master configured with VRRP redundnacy at main location. All VIA profiles and configurations are done. Can successfully connect to VIA  if using vpn1.via.org and connecting to this network.

Standalone Master configured at remote site. All VIA profiles and configuratoins are done and match configuration at main location. Can successfully connect to VIA if using vpn2.via.org and connecting to this network.

If successfully connected to the profile at either location, but then hitting disconnect and changing to the other location, it fails to establish connection. 

Configurations are virtually identical (minus IP addresses and some VLANs). Are there any special options or configurations needed in order to allow this to happen or are they any configuration options that would prevent this from  happening.

We have reset the VIA client and re-downloaded the profiles multiple times and still unsuccessful.

Thanks.