After some script scanning and testing the way to get it working is:
- After installing Storage Foundation Manager 2.1 start the configuration accessing to https://
yourhost:5634 and go through the default settings after giving the root password.
- This page will stall at the 'Discovering host details' but will create a database with the related vxsfcmsdb service. The service goes into maintenance however:
# svcs vxsfmcsdb
maintenance 10:55:58 svc:/system/vxsfmcsdb:default
Disable this service:
# svcadm disable vxsfmcsdb
/var/svc/log/system-vxsfmcsdb:default.log shows:
[ Jan 26 10:56:14 Leaving maintenance because disable requested. ]
[ Jan 26 10:56:14 Disabled. ]
But the port 14182 (the one used by the db) still remains open:
# netstat -an | grep 14182
*.14182 Idle
*.14182 *.* 0 0 400000 0 LISTEN
The port belongs to the process (check with pfiles 14252):
USER GROUP PID PPID STIME %CPU %MEM COMMAND
root root 14252 1 10:53:54 0.1 0.4 dbsrv9 -n SFM_upgdes -xtcpip(port=14182) -ct+ -gd DBA -gk DBA -gl DBA -gp 8192
Tracking down the scripts used by the vxsfmcsdb service, you'll get to this one. Execute it:
# /opt/VRTSsfmcs/config/adm/db_stop.sh
Adaptive Server Anywhere Stop Engine Utility Version 9.0.2.3743
- Now there is no port 14182 open anymore:
# netstat -an | grep 14182
- Enable the service vxsfmcsdb:
# svcadm enable vxsfmcsdb
/var/svc/log/system-vxsfmcsdb:default.log shows:
[ Jan 26 10:57:29 Enabled. ]
[ Jan 26 10:57:29 Executing start method ("/opt/VRTSsfmcs/config/adm/vxsfmcsdb start") ]
Starting SFMdb...
New process id is 14813
[ Jan 26 10:57:39 Method "start" exited with status 0 ]
That looks better....
- Check the vxsfmcsdb service
# svcs vxsfmcsdb
online 10:57:39 svc:/system/vxsfmcsdb:default
- Now go back to the web config in https://
yourhost:5634 and configure the Storage Foundation Manager as before.
You'll get through the 'Discovering host details' hick-up and you will be ready to use the manager!
During the execution /var/svc/log/system-vxsfmcsdb:default.log shows:
[ Jan 26 10:58:39 Rereading configuration. ]
[ Jan 26 10:58:40 No 'refresh' method defined. Treating as :true. ]
[ Jan 26 10:58:40 Rereading configuration. ]
[ Jan 26 10:58:40 No 'refresh' method defined. Treating as :true. ]
- You can now enter the management application at https://yourhost:14161/sm/Login
- For some reason the database manager may start listening on port 14183 which gives you the message 'Cannot connect to the database' (or something similar, I didn't write down that one) in the main screen of Storage Foundation Manager. Exiting and entering seems to resolve the problem.
Some work is still to be done there for the Veritas Engineers!!! :(