HP Servicecontrol Manager 3.0 Troubleshooting Guide

Servicecontrol Manager Issues
SCM 2.5 Daemons Not Running During SCM 3.0 Upgrade
Chapter 3
33
SCM 2.5 Daemons Not Running During SCM 3.0 Upgrade
Symptom Data from SCM 2.5 is not available in SCM 3.0 after an upgrade is performed.
Verification The command mxnode -ld only shows the local hostname.
Fix This fix requires that the backup files you created from the upgrade procedure are
available. See the HP Servicecontrol Manager 3.0 User’s Guide for details.
1. Convert the backup files to XML files:
/opt/mx/lbin/def2xml -a mxnode.scm25 mxnode.xml
/opt/mx/lbin/def2xml -g mxgroup.scm25 mxngroup.xml
/opt/mx/lbin/def2xml -a mxuser.scm25 mxuser.xml
/opt/mx/lbin/def2xml -a mxrole.scm25 mxrole.xml
/opt/mx/lbin/def2xml -a mxtool.scm25 mxtool.xml
/opt/mx/lbin/def2xml -a mxauth.scm25 mxauth.xml
2. Add the XML data to SCM:
NOTE Order matters. The mxauth command must be executed last.
mxnode -a -f mxnode.xml
mxngroup -a -f mxngroup.xml
mxuser -a -f mxuser.xml
mxrole -a -f mxrole.xml
mxtool -a -f mxtool.xml
mxauth -a -f mxauth.xml