I am having difficulties to get documentation specified for version 2.4
all the docs on StarTAC are for 2.2 but i got this thingie working
what are your experiences?

Hi! We have had Unicenter 2.4 with multiple dsm in one core and now we have upgraded to Unicenter NSM 3.0 0211. What are your considerations?

Regards Marcus

Hi Marcus

i have some problems with understanding the need for aws_wvgate and parameters in this case
i have aws_wvgate running on the core-dsm and the remote dsm's with default parameters. What special parameters and settings do u use on those remote DSMs.
Maybe you could pass me some "installation checklists" if it isn't confidential.
thanks

Valeri

P.S. How is the remote DSM deployment with the new 3.x version? Same or different?

Hi Valeri

We have installed the Remote DSM's with the default settings, the only thing that we change is that the Remote DSM shall forward its events to the Core-DSM and if you have good connection you could use the central Enterprise database for the Remote DSM as well.

The only difference between the 2.X version and the 3.X version is the Global catalog server, which should be located on the Core.

How many servers are you going to monitor with Unicenter?
How many DSM are you going to use?

We are monitoring about 200 servers (soon to be 300+) with 5 DSM's and one Core-DSM.

The wvgate connects the DSM to the Core, so this would be the same for all DSM's.
TNG / TND is designed for precisely the configuration you want - multiple DSM's with 1 core, so there will be no problem.

You just need to tell each DSM which subnets or machines it should be monitoring - so that they are not all monitoring your entire network (which may result in duplicate messages).
You set this in the gwipflt.dat file, located in tnd\services\config\aws_wvgate
EG:
set DSM1 to monitor the 169.17.1.* subnet
set DSM2 to monitor the 169.17.2.* subnet

Then run clean_nsm on each DSM server.
Then after discovering the objects in your core, run setdsmname on each DSM.