cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1249
Views
0
Helpful
2
Replies

BE3000 reimage problem

Ilya Shilov
Level 1
Level 1

Hello!

So the story begins with initial setup of BE3000 8.6.3.10000-12 on client side.

Triyng to install last available russian country pack for 8.6.3 during First Time Setup Wizard had no luck.

I got "Installation failed for..." with no additional info. Tried with Chrome, with Firefox... downloading by http and from directly connected USB... same thing.

I made decision to reimage be3k with dowloaded 8.6.4 non-bootable version... but before this I made it bootable (boot.bif hack). After about an hour of process, installation stops with critical error.

I tried to reimage appliance from DVD that comes in package (8.6.3). Media check test successfully passed. Process stops at the same moment with the same error.

By booting with prepared CD I made tests of RAM and HDD drive - no errors detected.

So for now I have completely nonfunctional BE3000 and no ideas how to bring it into live.

Last part of /common/log/install/install.log:

---------------------------------

10/05/2012 05:22:05 component_install|(CAPTURE) Fri Oct  5 05:22:02 2012 dblinit-plugin.initializeIDS  ERROR:  Error Initializing IDS ["Error executing [su -c 'source /usr/local/cm/db/informix/local/ids.env ;  /usr/local/cm/bin/cmoninit -wivy' - informix] returned [256]"]|<LVL::Debug>

10/05/2012 05:22:05 component_install|(CAPTURE) Fri Oct  5 05:22:02 2012 dblinit-plugin.run  ERROR:  ERROR: 'CCMLOG'|<LVL::Debug>

10/05/2012 05:22:05 component_install|(CAPTURE) Fri Oct  5 05:22:02 2012 dblinit-plugin.initializeIDS  DEBUG:  <--|<LVL::Debug>

10/05/2012 05:22:05 component_install|(CAPTURE) Fri Oct  5 05:22:02 2012 dblinit-plugin.run  DEBUG:  <--|<LVL::Debug>

10/05/2012 05:22:05 component_install|(CAPTURE) Fri Oct  5 05:22:02 2012 cm-dbms-install  ERROR:  Install Post Failed|<LVL::Debug>

10/05/2012 05:22:05 component_install|(CAPTURE) Fri Oct  5 05:22:02 2012 cm-dbms-install  DEBUG:  >>> cm-dbms-install [1]|<LVL::Debug>

10/05/2012 05:22:05 component_install|(CAPTURE) Fri Oct  5 05:22:02 2012 cm-dbms-install  DEBUG:  <--|<LVL::Debug>

10/05/2012 05:22:05 component_install|File:/opt/cisco/install/bin/component_install:743, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>

10/05/2012 05:22:05 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:147, Function: install(), failed to install infrastructure_post components|<LVL::Critical>

10/05/2012 05:22:05 post_install|File:/opt/cisco/install/bin/post_install:910, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -install failed (1)|<LVL::Error>

10/05/2012 05:22:05 post_install|Exiting with result 1|<LVL::Info>

10/05/2012 05:22:05 post_install|INSTALL_TYPE="Basic Install"|<LVL::Debug>

10/05/2012 05:22:05 post_install|File:/opt/cisco/install/bin/post_install:611, Function: check_for_critical_error(), check_for_critical_error, found /common/log/install/critical.log, exiting|<LVL::Error>

10/05/2012 05:22:05 post_install|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]|<LVL::Debug>

10/05/2012 05:22:05 display_screen|Arguments: "Critical Error" "The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.

"/usr/local/cm/script/cm-dbms-install install PostInstall 8.6.3.10000-12 8.6.3.10000-12 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt " failed (1)

The system will now halt.

---------------------------------

Any help will be appreciated!

1 Accepted Solution

Accepted Solutions

Hello Ilya,

Goot to know you were able to address this with the assistance from TAC. Please mark this question as answered.

View solution in original post

2 Replies 2

Ilya Shilov
Level 1
Level 1

After two weeks consulting with TAC problem was solved.

Installation succeeded with disconnected network interface.

As TAC wrote:

"Root cause is linux networking script detects the duplicate IP and downs the interface eth0.

Hence, arping command not received IP address as argument and thrown error. No issue with arping.

...

10/05/2012 05:03:27 IPM|(CAPTURE) Bringing up interface eth0:  Error, some other host already uses address 192.168.1.250.|

"

Hello Ilya,

Goot to know you were able to address this with the assistance from TAC. Please mark this question as answered.