Thank you for sharing your experience. It appears the process for Solaris is very much like Linux. To clarify Step 7, the only input is ./resizeDSN. The values in parenthesis ( ) are just a reference as to what values will be used once prompted after the WARNING message. It’s true that once you start Broadworks and it says all services have been started, it still takes time for the server to be functional. Typical complaints from Healthmon are the SNMP service is not running (server not reachable on 127.0.0.1), the server is locked and needs to be unlocked, or the execution server is not running. Running Healthmon too quickly after startup can cause these warning to be reported when running Helathmon. Best practice is to wait 5 minutes before doing anything.

–

Here’s a few comments from our experience:

1. We run Broadworks on Solaris so checking the available memory can be achieved using:

bash-2.05$ prtconf | grep Mem
Memory size: 2048 Megabytes

So our servers have 2GB of memory. Of course your guide does state to check but someone else might gain some use for this if they also run under Solaris.

2. Step 6 on both as1 and as2 was the following for us:

./timesten.pl unload

I would put this down to OS choice etc

3. On step 7 we found the following to be better by itself:

./resizeDSN

This then provides for checking what the allocations are, making interactive changes, and checking before implementing the change.

–

We also had issues running the replication so also had to use the manual backup and restore procedure.

Finally, when completing the changes on as1 we recieved errors regarding the “execution server not running” and the “replication service not running”. It seems this was down to the speed we went through the commands and the server eventually ‘fixed itself’ since Broadworks sent out broadcast messages that it was starting itself.

We learnt that:

healthmon -l

… is your friend and to take your time.

Again, thanks for posting this since it proved to be a lifesaver for us.