08-19-2014 07:49 PM - edited 03-20-2019 08:16 PM
After we upgraded to 2.1(3c), the issue described in CSCuh61202 still occurs. We have logged a new bug: https://tools.cisco.com/bugsearch/bug/CSCuq40256
Has anyone else experienced the same?
