I ran into a lot of issues after upgrading my CCR1009 from R.47rc2 to v7.0 Beta 8 and had to downgrade back to R.47 to have a functional network. Here are the issues:
I expected the upgrade would use the same configuration as R.47 but it didn’t. It used the default configuration as if I had reset the router. Therefore none of my access points were configured via capsman.
Connecting a netbook to an ethernet port and trying to log into the router, I found out I had to get a new version of winbox.
Once I got a new winbox, it could only log in via the mac address. I then restored a backed up R.47 configuration.
Following configuration restore, winbox showed the router and the access points but I could not connect to any of them. In addition, no wifi client could see the SSIDs of the access points. The only way I could log into the router was by resetting it back to the original configuration with the default admin credentials.
After several attempts to get the network functional, and winbox to be able to log into APs and the router with the proper configuration, I downgraded back to R.47. It took some research to figure out how to do that.
In short, upgrading to the v7 beta was a complete failure and disappointment. Any insight as to what went wrong and how to resolve these issues?
From my testing, CAPs running 7.0beta8 can be managed by 6.47 CAPsMAN, but not the other way around. In other words, if you are running 7.0beta8 CAPsMAN, any 6.47 CAPs will not function.
The config structure is pretty much the same as 6.47, except for routing protocols (OSPF, BGP).
Not all of the config conversion software is written for the upgrade process, so you should export .rsc beforehand to get your important config back in afterwards.
Thanks for the info. I was able to leave the router at 6.47 and upgrade 5 of my 7 APs to 7.0 beta8. However, my two wAP ac APs became inoperable after upgrade. I have other MIPSBE APs that upgraded OK though. Outdoor APs with POE are not the easiest to work with but I was able to see that one was flashing the CAP led, probably looking for a 7.0 capsman. I was able to reset it back to the default configuration of AP with two open SSIDs, connect winbox through one of those and downgrade to 6.47. It then got properly configured by 6.47 capsman. Following the same steps, the other wAP reset the default configuration to CAP, rather than AP. I had to use the ethernet connection and default IP address to get into it and downgrade it. It looks like there is an issue with 7.0 beta8 wAP’s being managed by a 6.47 capsman. There also seems to be an issue with what default configuration they use when reset.
I ran into another MIPSBE problem on a hAP ac running 7.0 beta 8. It has a virtual AP configured by capsman for use by my main printer. The printer associated with the virtual AP and got an IP address but nothing could communicate with it. The router couldn’t even ping it. I had to downgrade the AP to 6.47 to get the printer to work. Is there a better way to document these issues other than this thread?