Couple of quirky DFM Issues that I need help with.

[storage_ergo]

I have a customer for which I installed DFM 3.8 on Linux and did a database backup and restore from their old 3.5 Solaris environment. The title bar on the Web browser for DFM still reflects their old host name. Is there something I need to change in DFM for this to be updated?

Also when we test some of the alarms in the new DFM server, the message contents still reflect the  old hostname and links to the old server. At first I thought the old host was still up and running, but that is not the case as per the customer.

Any help would be greatly appreciated.

Thanks!

Kev

[storage_ergo]

Well....I've figured it out.

It was this option

dfm options set localHostName=<new host>

For some reason it carried the old DFM hostname into its options, even though we did a backup and restore.

Is this normal behavior ?

[adaikkap]

This is because in your old dfm server you have set it to a specify name.

By default the option is empty and pick up the hostname.If you set it to a specify value then that is used.

Below is the example.

[root@lnx ~]# dfm options list | grep -i localHostName
localHostName
[root@lnx ~]#

[root@lnx~]#  dfm options list localHostName
Option          Value
--------------- ------------------------------
localHostName
[root@lnx~]#

This wouldnt have been in your case.Hope it explains why .

Regards

adai