We are running something very very similar (8x2232 FEX) per pair of 5596UP
and so far they are doing fine. Just for fun, you might want to uprade to
N1(3):
kickstart image file is: bootflash:///n5000-uk9-kickstart.5.2.1.N1.3.bin
kickstart compile time: 12/4/2012 1:00:00 [12/04/2012 09:53:21]
system image file is:bootflash:///n5000-uk9.5.2.1.N1.3.bin
system compile time: 12/4/2012 1:00:00 [12/04/2012 11:40:13]
-pavel
On Sun, Jan 27, 2013 at 8:53 PM, Deny IP Any Any denyipany...@gmail.comwrote:
I have a pair of 5596UPs with 6 2K FEXes; I'm doing converged 10GB/FCoE to
a dozen big Dell VMWare boxes, and native FC to a SAN.
I'm experiencing frequent crashes, which TAC diagnoses as known-issues and
promises a fix will come in a future release (notice my once-every-6-months
crash got upgraded to a 'once-every-2-months-crash). Is anybody running a
setup similar to mine that could comment on what I can do to increase the
stability of this unit, or am just living too close to the bleeding edge to
expect stability?
5596UP# show system reset-reason
- reset reason for Supervisor-module 1 (from Supervisor in slot 1) ---
1) At 407317 usecs after Sat Jan 19 00:03:59 2013
Reason: Reset triggered due to HA policy of Reset
Service: port-profile hap reset
Version: 5.2(1)N1(2a)
2) At 104796 usecs after Thu Nov 15 04:53:25 2012
Reason: Reset due to upgrade
Service:
Version: 5.0(3)N2(2)
3) At 410380 usecs after Fri Sep 28 19:03:46 2012
Reason: Reset triggered due to HA policy of Reset
Service: fcpc hap reset
Version: 5.0(3)N2(2)
4) At 951524 usecs after Fri Mar 30 00:12:39 2012
Reason: Reset triggered due to HA policy of Reset
Service: fcpc hap reset
Version: 5.0(3)N2(2)
--
deny ip any any (4393649193 matches)
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
