Thanks for the post. We had also seen this issue and fixed it in release 13.2. Please upgrade to the latest 13.2.1 release or let us know if you are still seeing the issue on 13.2.1.
I'm running 13.3. We needed the 5 ms frame size to co-locate with 320s until we can get all the 320 SMs replaced. That's true on all our other towers that aren't showing this error as well.
It hasn't caused any problems that I know of, but we haven't been using 450s long and we have very small numbers of people on them. Most of the 450s we have up are replacements for 320s with serious stability problems, so even if there are issues it's still an improvement and customers won't contact me about it.
We have to use 5 ms frames for 320 colocation, so rolling back isn't viable.
I would love to try the beta software. We're essentially the worst case scenario; tons of noise, trees everywhere, and hilly terrain. I spent a lot of time working with John Mehling dealing with 320 problems, and there were quite a few things we learned about the 320s that he hadn't seen anywhere else. I suspect we're an excellent test environment; If it works here, it will work anywhere.
Can you send me an email to get started with the beta, or is there a more formal application I need to fill out?