cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1175
Views
0
Helpful
7
Replies

2.1(3c) does not fix CSCuh61202

ekerdman88
Level 1
Level 1

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?

7 Replies 7

caseygordon
Level 1
Level 1

We started upgrading our different domains to 2.1(3c) from 2.1(1a) to apply the patched fnic driver that was supposed to fix the issue. Seeing fnic aborts now and it's very similar to CSCuh61202 but the impact looks to be different. In one of our UCS domains, we didn't see any issues for 2+ weeks after upgrading. We got reports of high disk latency on VMs and we started digging. On another UCS domain upgrade, we saw the aborts start right after the upgrade was UCS completed but have not seen any signs of disk latency yet. We have four other UCS domains that were upgraded from 2.1(1a) to 2.1(3c) and do not see the issue in any of those domains.