I still do not know why the MM's are treating the controllers at Location - C differently.
1. Is it a firewall problem, even though the firewall at 'Locaiton A' sees communication passign through from the local controllers at Locaiton C trying to go to the MM Virtual V.I.P.?
a. Do we need to enter license keys for the new 7010 controller to communicate with the Mobility Master?
2. Maybe we can trace the 4500 traffic from the local controllers after they arrive at the Locaiton A office.
3. Does the Mobility Master disable a local controller if they are disconnected after a specific periof of time?
a. Keep in mind Locaiton C was disconnected for hours and then reconnected after teh Firewall reboot.
b. I have seen similar security measures happen with other applications that require devices to be manually re-enabled.
4,. Why is it when I execute >show datapath session table MM_V.I.P. | include 4500<enter> from the controllers in Location - C I see packets going to the MM_V.I.P. but the Destination field is shown as 'local'.
When I execute the same command from the other local controllers (at other sites) the Destination field is shown as '0/0/0'. Why is the festination different and showing up as 'local' instead of 0/0/0?
Source IP | Destination IP | Prot | SPort | DPort | Cntr | Prio | ToS | Age | Destination | TAge | Packets | Bytes | Flags | CPU ID
5. Can there be something at the Mobility Master end that is required to allow 4500 traffic to communicate again? Ironically just a few days ago (after the 4500 traffic problem) the MMs were restarted by mistake and the backup MM is now the main MM. A restart of the MM's did not cure the problem. I am wondering if I should restart teh backup MM so I can get the main MM back as primary?
6. Might this have anyhting to do with connecting Access Point Ap 345 to the Wireless Controller VLan? These 345 booted up and automatically updated themselves to the same versrion as the controller (8.3.0.3).
a. I was abel to see the bootup and update process while I was connectged to the AP's thorugh a lcoal SSH connection. I beleive the AP's came with verison 8.0 and then recognized the controller had version 8.3 and initiated an update automatically.
b. At the other sites we used IAP - 325 that came with version 6.4 and I needed to manually update to version 6.5 and then manually convert the IAP to campus mode.
c. This is prbably a non-issue; but, I did not bring it up in the past.
d. Should we un-plug the AP-345 to see if that helps?
e. Model: AP-345, SNs: CNFZK5110Y, CNFZK5114C, CNFZK51134, CNFZK5112M, more of the same.
7. Is tehre any licensing that needs to be entered on the MM end to work correctly with the new Local Controllers at Location C?
8. Quite simply the communcation with the MMs from Locaiton C was working before the Firewall problem and now it does not. I even did a 'write erase' on 1 of the controllers and that controller now does not even see the inherited configuraiton that the other Location C controller already downloaded. Because communication with the MMs is down. This proves teh problem is not with teh configuration on the local controller.
a. Why would the MM not receive port 4500 communication from the local controllers at a diffeent site?
b. Is there any configuration that is required on the MM besides the MAC address and its PSK (verified with >show local-peer-mac<enter>
c. Does the MM require licesing information to work correctly with the new Local controlers and its Access Points?