Hi there. I've got a CU with a Nexus 5000, he sent me a log. I didn't find in Cisco web page information about it. could you help me????
arcnopes31# sh ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS: version 1.2.0
loader: version N/A
kickstart: version 5.0(2)N1(1)
system: version 5.0(2)N1(1)
power-seq: version v1.2
BIOS compile time: 06/19/08
kickstart image file is: bootflash:/n5000-uk9-kickstart.5.0.2.N1.1.bin
kickstart compile time: 10/15/2010 0:00:00 [10/15/2010 05:00:43]
system image file is: bootflash:/n5000-uk9.5.0.2.N1.1.bin
system compile time: 10/15/2010 0:00:00 [10/15/2010 06:34:05]
Hardware
cisco Nexus5010 Chassis ("20x10GE/Supervisor")
Intel(R) Celeron(R) M CPU with 2073416 kB of memory.
Processor Board ID JAF1428BMFR
Device name: arcnopes31
bootflash: 0 kB
Kernel uptime is 31 day(s), 19 hour(s), 1 minute(s), 0 second(s)
Last reset at 470715 usecs after Thu May 5 16:29:44 2011
Reason: Reset by installer
System version: 4.1(3)N1(1)
Service:
2011 Jun 6 01:42:30 arcnopes31 Jun 6 01:42:30 %KERN-3-SYSTEM_MSG: e1000: eth0:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:32 arcnopes31 Jun 6 01:42:32 %KERN-3-SYSTEM_MSG: e1000: eth0:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:32 arcnopes31 Jun 6 01:42:32 %KERN-3-SYSTEM_MSG: e1000: eth4:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:34 arcnopes31 Jun 6 01:42:34 %KERN-3-SYSTEM_MSG: e1000: eth0:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:34 arcnopes31 Jun 6 01:42:34 %KERN-3-SYSTEM_MSG: e1000: eth4:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:35 arcnopes31 %IM-5-IM_INTF_STATE: mgmt0 is DOWN in vdc 1
2011 Jun 6 01:42:36 arcnopes31 Jun 6 01:42:36 %KERN-3-SYSTEM_MSG: e1000: eth4:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:38 arcnopes31 Jun 6 01:42:38 %KERN-3-SYSTEM_MSG: e1000: eth4:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:38 arcnopes31 %IM-5-IM_INTF_STATE: mgmt0 is UP in vdc 1
2011 Jun 6 01:42:30 arcnopes31 Jun 6 01:42:30 %KERN-3-SYSTEM_MSG: e1000: eth0:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:32 arcnopes31 Jun 6 01:42:32 %KERN-3-SYSTEM_MSG: e1000: eth0:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:32 arcnopes31 Jun 6 01:42:32 %KERN-3-SYSTEM_MSG: e1000: eth4:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:34 arcnopes31 Jun 6 01:42:34 %KERN-3-SYSTEM_MSG: e1000: eth0:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:34 arcnopes31 Jun 6 01:42:34 %KERN-3-SYSTEM_MSG: e1000: eth4:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:35 arcnopes31 %IM-5-IM_INTF_STATE: mgmt0 is DOWN in vdc 1
2011 Jun 6 01:42:36 arcnopes31 Jun 6 01:42:36 %KERN-3-SYSTEM_MSG: e1000: eth4:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:38 arcnopes31 Jun 6 01:42:38 %KERN-3-SYSTEM_MSG: e1000: eth4:
e1000_clean_tx_irq: Detected Tx Unit Hang - kernel
2011 Jun 6 01:42:38 arcnopes31 %IM-5-IM_INTF_STATE: mgmt0 is UP in vdc 1
