[cisco-voip] Hardware identification glitch

[Mike Armstrong]

We upgraded from 3.3(3) to 4.1(2) yesterday, going 3.3(3)->4.0(2a)->4.1(2) 
on the Publisher.  We wanted to build a new, from-scratch Publisher AND 
subscriber to eliminate what I call "bit rot" -- the tendency of a 
many-times-upgraded or just plain old, system to develop weird behavior. 
However, we couldn't do that to the Publisher because you can't restore a 
BARS backup file from one version to another.  But, we figured the 
subscriber would be no problem, and planned to build a new subscriber on a 
staging machine in parallel with the Publisher upgrade.  We have a spare 
DL380-G2 we use for testing and staging which was purchased late in the G2's 
life, and came with 2 1400MHz processors.  When I started the clean install, 
CD1 identified it as an MCS7835 OK, but CD2 (apparently because of the 
1400MHz processors (not the presence of the 2nd processor -- this works OK 
on a dual-processor 1266MHz system)) decided it was an MCS 7845, and called 
for CD10 rather than CD9 to install the OS.  Since we did not have a 2nd 
mirrored drive pair, the install script failed looking for the 2nd drive. 
Sure would be nice if the installer were a little less picky.  Or, better 
yet, if Cisco would come up with a way to install CCM in a virtual machine 
(VMware preferred) for testing purposes only.  OTOH, this may be a way to 
expand hard-drive space while working within the confines of Cisco 
procedures -- I'm sure you could build a "7845" on the 1400MHz machine and 
move the 4 drives to a 1266MHz machine and it would work fine.

Mike Armstrong
UF/IFAS CREC
Lake Alfred, Warm, sunny Florida