Filter
Top Products
Netcool/Precision for Transmission Networks 5.5 Administration Guide54
There is one further Oracle requirement. The default tablespace of the Oracle connection
created by the primary server must be the same as the one created by the secondary. This
will be the case if both servers are using the same precisiontn.xml file.
Configuring the Netcool/Precision TN servers
The primary and secondary instances of the Netcool/Precision TN server should run on
different machines. It is recommended that the two installations are identical.
!!
Attention: The minimum requirement is for the precisiontn.xml and
oracle_config.xml files to be identical between the two instances.
Running failover
This section describes how to start and stop failover.
Starting the servers
To start the servers:
1. Start the database. See your Oracle documentation for information about starting the
database you are using.
2. Start the servers using the command:
./precisiontn
The first instance you start will come up as the primary server. Start a second instance
of Netcool/Precision TN as your secondary server.
3. Start Network Pilot. To monitor the primary server, follow the instructions in "Step 3 –
starting Network Pilot" on page 32 to start Network Pilot. You cannot monitor the
secondary server.
Switching the state of a server
To force the instances of the server to switch state, you must shut down the primary server.
To shut it down gracefully from Network Pilot, click the Shutdown button on the Admin
tab. The secondary will detect that it has been shut down and become the primary. After
the initial secondary has finished the switchover, you can start another secondary instance
from the command line, as described above.
Stopping servers running in failover configuration
Although it is unusual to go from running servers in a failover configuration to running just
one server, you might want to do this at some point. To stop the servers:
1. Shut down the primary server gracefully from Network Pilot by clicking the
Shutdown button on the Admin tab.
2. Because you cannot use Network Pilot with the secondary server, you can shut down
the secondary server manually using the kill command.