Nortel Networks Sun Fire V210 (RoHS) - Manual (Page 167)

MCS 2-server Sun Fire V210 (RoHS) Solaris Installation and Commissioning Guide
167 Copyright © Nortel Networks Limited 2006
The only address in this file defines your default gateway route
(your router). If this file is empty and the machine is rebooted,
then you will not have network access to your other servers.
Verifying the database load (imssipdb) deployment
The initial deployment of the imssipdb load is command-line driven from
the MgmtSvr. Updates to the imssipdb load in future loads will be
handled through the System Management Console.
The following section describes the steps to watch the imssipdb
deployment logs as the dbdeploy.pl script executes.
The following commands are executed on the database server using
PuTTY SSH into the machine logical IP address.
Example: Open a PuTTY SSH session to 120.120.13.22
Procedure 45 Verifying the database load (imssipdb) deployment
At the management pc,
1 Log into the database server as nortel/<new nortel user
password>.
2 Execute the following command to tail (watch) the imssipdb
deploy log.
[@micromgmt] /export/home/nortel:=> tail -f /tmp/*SQL*
As the dbdeploy.pl script executes, a temporary log is created in
the /tmp directory on the database server. Note that the SQL file
in the /tmp directory will not be present until after the dbdeploy.pl
script begins.
3 While ‘tailing’ the SQL temp file, look for errors in the log file.
These errors could include statements such as ‘error’, ‘failed’,
and so on. If any error condition is encountered, do not continue.
Contact support immediately.
4 The imssipdb deployment is successful when the Server1’s
dbdeploy.pl script reports ‘deployed successfully.’
ATTENTION
If the database deployment has completed, this file will not exist.