Daniel
I just found out that the VIP2 is a VIP2-40 so I don't think
that memory is the issue.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Daniel Cotts
Sent: Wednesday, February 06, 2002 9:48 AM
To: [EMAIL PROTECTED]
Subject: RE: VIP2 microcode [7:34511]
Long reply coming back: The following is a cut from a "show diag". Note
the
Controller Memory Size line. In this case it most likely is a VIP2-10.
Do a
search on CCO for "Mandatory Memory Upgrade" - here is one of the finds:
http://www.cisco.com/warp/public/770/fn4489_05141999.html
TGN_7507>sh diagbus
Slot 0:
Physical slot 0, ~physical slot 0xF, logical slot 0, CBus 0
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: None
EEPROM format version 1
VIP2 controller, HW rev 2.04, board revision D0
Serial number: 04378695 Part number: 73-1684-03
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 15 02 04 00 42 D0 47 49 06 94 03 00 00 00 00
0x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0xFF4 (7w3d ago)
Controller Memory Size: 8 MBytes DRAM, 512 KBytes SRAM
PA Bay 0 Information:
Ethernet PA, 8 ports
EEPROM format version 1
HW rev 1.14, Board revision A0
Serial number: 15355261 Part number: 73-1391-08
PA Bay 1 Information:
Ethernet PA, 8 ports
EEPROM format version 1
HW rev 1.12, Board revision A0
Serial number: 06632776 Part number: 73-1391-07
--Boot log begin--
Cisco Internetwork Operating System Software
IOS (tm) VIP Software (SVIP-DW-M), Version 11.3(11a), RELEASE SOFTWARE
(fc1)
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Mon 20-Sep-99 07:31 by jjgreen
Image text-base: 0x60010910, data-base: 0x6016E000
--Boot log end--
> -----Original Message-----
> From: Joseph Carr [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 06, 2002 12:56 AM
> To: [EMAIL PROTECTED]
> Subject: Re: VIP2 microcode [7:34511]
>
> ***END CUT FROM CONSOLE***
>
> We also did a sh diag and saw that the "board is disabled
> wedged" and the
> memory amount is unknown (like before), and this time, it
> doesn't say the sw
> version (under sh cont cbus) and the microcode status is 0x5.
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=34666&t=34511
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]