Restarting NOM after upgrading to OpsCenter on Windows

Article:HOWTO43407  |  Created: 2011-03-06  |  Updated: 2011-03-06  |  Article URL http://www.symantec.com/docs/HOWTO43407
Article Type
How To

Product(s)

Environment

Subject

Languages

Restarting NOM after upgrading to OpsCenter on Windows

After you upgrade from NOM to OpsCenter 7.1 on Windows, the NOM processes are stopped. In case you want to reuse NOM after upgrading to OpsCenter 7.1, the following steps help you to restart NOM.

To restart NOM services after upgrading to OpsCenter 7.1 on Windows

  1. Run the following command to enable VxPBX.

    C:\Program Files\Veritas\Security\Authentication\bin>vssat setispbxexchflag -enable

  2. Run the following command to delete the domain NOM_MACHINES from the system.

    C:\Program Files\Veritas\Security\Authentication\bin>vssat deletepd --pdrtype ab --domain NOM_MACHINES@<system name>

  3. Run the following command to delete the broker domain vx:domain name.

    C:\Program Files\Veritas\Security\Authentication\bin>vssat deletebrokerdomain --domain vx:NOM_MACHINES@<system name> --broker <system name>:2821

    Note:

    If the NOM services are still not up, restart the pbx services and vxat services. Restarting the services helps in restarting the NOM manager. Once the NOM manager is up, you can start the NOM GUI.

See Upgrading from NetBackup Operations Manager to Symantec OpsCenter 7.1 on Windows

Legacy ID



v51502409_v51189657


Article URL http://www.symantec.com/docs/HOWTO43407


Terms of use for this information are found in Legal Notices

Please Sign In

Login using SymAccount.

Knowledge Base Search

Knowledge Base Search

Rate this Article

Help us improve your support experience.

MySymantec

MySymantec

Contacting Support

Contacting Support