On Tue, Dec 28, 2010 at 1:08 AM, Mark Serencha <[email protected] > wrote:
> Hi Stephen, > > > > 7.1 is before my time, but here’s some exerpts from modern docs which may > or may not help you. There are a couple other VNMRC entries mentioned which > may or may not apply to 7.1 > > > > To limit the potential for false events or alarms, add the following line > to the secondary SpectroSERVER’s .vnmrc file: > > is_secondary = TRUE > > This setting allows the secondary SpectroSERVER to drop events unless > SPECTRUM’s internal mechanisms have determined that the secondary > SpectroSERVER has taken over as the primary SpectroSERVER. > > > > To establish fault tolerance > > 1. The same version of SPECTRUM with the same modeling catalog should be > installed on both the machine you want to host your primary SpectroSERVER > and the machine you want to host your secondary SpectroSERVER. Each of these > should have the same landscape handle. > > 2. Make sure both the primary and secondary SpectroSERVER machines have > entries in their .hostrc files giving the SpectroSERVERs access permissions > for each other. > > Note: If you are specifying secure users for the secondary SpectroSERVER in > the primary SpectroSERVER machine's .hostrc file, and the secondary > SpectroSERVER machine is running in the Windows environment, you must make > sure to include the user SYSTEM in the secure user list. > > 3. Make sure that the MAIN_LOCATION_HOST_NAME parameter in the secondary > SpectroSERVER machine’s .locrc file points to the same system name that the > primary SpectroSERVER is pointing to. If this is not configured properly, > the synchronization will fail. > > 4. Configure the primary and secondary SpectroSERVERs so that the user > running each SpectroSERVER is the same. If the users are not the same, the > secondary SpectroSERVER will fail or will not run properly after an Online > Backup is performed. > > 5. Make a copy of the primary SpectroSERVER’s database, either by running > Online Backup or, if the SpectroSERVER is shut down, by using the SSdbsave > utility with the -cm argument (to save the modeling catalog as well as any > models that have been created). > > 6. Using the transport method of your choice, make sure the save file > previously created is available to the machine you want to host your > secondary SpectroSERVER. > > 7. On the secondary machine, with SpectroSERVER shut down, navigate to > SPECTRUM’s SS directory and load the save file using the following command: > > ../SS-Tools/SSdbload -il -add <precedence> <savefile> > > where <precedence> is a numeric value greater than the primary’s default > value of 10 (20 is recommended), and <savefile> is the name of the save file > previously created. > > 8. If you want the secondary SpectroSERVER to function as a hot backup, add > the line secondary_polling=yes to its .vnmrc file. > > If you want the secondary SpectroSERVER to function as a warm backup, > add the line secondary_polling=no to its .vnmrc file. > > 9. Start the primary SpectroSERVER, if it is not already running. > > 10. Start the secondary SpectroSERVER. > > 11. To verify the setup, use the MapUpdate command with the view argument > to display the current landscape map. > > The secondary SpectroSERVER is now available to take over automatically in > the event the primary SpectroSERVER fails. If you previously activated > secondary polling, the secondary SpectroSERVER will be available > immediately. If not, it will begin polling as soon as it detects it has lost > contact with the primary SpectroSERVER > > When service switches from the primary SpectroSERVER to the secondary > SpectroSERVER, the Connection Status icon displays yellow to indicate the > switched condition. To view the connection status of all servers in a > landscape, click the Connection Status icon. In the Connection Status dialog > box, the Connection Status icon for each server in the landscape displays > yellow to indicate the switched condition. > > When the primary SpectroSERVER comes back online, the secondary > SpectroSERVER stops polling (unless you have set secondary_polling to yes), > and all applications switch back to the primary SpectroSERVER. However, any > edits you make to the secondary SpectroSERVER while it is active will not be > automatically copied back to the primary SpectroSERVER. You must manually > recreate these modifications on the primary SpectroSERVER. > > When you restart the primary SpectroSERVER, connections will be accepted as > soon as all models are loaded, but before all models are activated. Since it > may take a while for all the models to activate, and since the secondary > SpectroSERVER will turn off polling as soon as the primary SpectroSERVER is > restarted, there can be a gap in your network management coverage. > > To avoid this situation, you can edit the primary SpectroSERVER’s .vnmrc > file so that the wait_active resource is set to yes. This causes the server > to wait until all of the models are activated before accepting any > connections. It also causes the message area in the SPECTRUM Control Panel > to dynamically display the percentage of models activated throughout the > activation process. The SpectroSERVER may appear to take longer to come up, > but when all of the models are activated, the SpectroSERVER is ready to > manage the network. > > You can also set the wait_active resource to yes on the secondary > SpectroSERVER. That way, for a planned shutdown of the primary > SpectroSERVER, you will be able to monitor the Control Panel to see exactly > when the secondary SpectroSERVER is ready to take over. > > > > HTH, > > --Mark S > > > > > * > ------------------------------ > * > > *Mark Serencha – Inforonics LLC – (m) +1-781-439-0519 – (w) +1-978-698-7418 – > **[email protected] * > > > Thanks for the reply Mark. I have looked at the documentation for 7.1 and 9 and the fault tolerance information is almost word for word the same. So I'm still not sure what I have missed in setting this up. The only thing that I have not done that I am going to try is adding is_secondary = true to the secondary SS. Hopefully this will work. Anybody else have any additional input? It looks like FT is pretty much the same in 7.x and 9.x so has anybody else experienced this in 9.x? --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
