Manually starting autofs means through initializeNPS.ovpl right, is there any other step if yes please suggest.
No, I mean manually starting the autofs service, outside of anything to do with NPS. Check to see if autofs is set to auto-start (use chkconfig), and start it with "service autofs start". See if it starts up properly, and if it doesn't, look around at your logs to see if you can figure out why.
Then try actually using the autofs service, by running "ls /net/<NNMi_Server_FQDN>/", and see if automount is working properly.
I'm wondering a bit why you're having so many problems with the NPS though - have you double-checked that all pre-requisite packages are installed, all config is OK, no disk space issues, etc?
All the pre-requisite packages were installed and now all the services are showing success but report menu is not showing all the menu, I have restarted all NPS services and checked but still the same problem, I have not tried restarting nnmi services probably that will work.
Secondly when I executed the enablement script it did not ask me to provide username and password, but it is mentioned in the iSPI installation document in linux environment.
I dont know what is wrong, can you suggest will it ask for username and password in enablementscript or not for linux environment
Sorry for the delay in replying, I've been on leave.
I just took a look at that doc - that looks like a typo. It seems to have come from the Windows installation guide, where you do need to create a new user. If you're using NFS with Linux, you don't need to create a new user, so don't worry about not being asked for a username/password.
Could you please give more details about the setup?
From the notes, I think NNMi and Metrics SPI are on separate linux boxes, correct?
If yes, paste the output of "initializeNPS.ovpl", and the output of the "nnmenableperfspi.ovpl" scripts here (please remove FQNDs and other environment specific info when you paste the output here).
Let me break this down in simple terms, so that you will know what will be impacted:
-->NNMi collects stats like InOctets/OutOctets/CPUUtilization/MemUtilization etc from various devices which you have configured for performance polling
-->NNMi will dump all that data in csv gzip files, at /var/opt/OV/shared/perfSpi/datafiles/metric/final/ (on the same NNMi server)
-->because the nnmenableperfspi.ovpl script enables file sharing, the above folder will be accessible to the Metrics SPI server when you cd to /net/<NNMiFQDN>/ on the Metrics SPI server:
Example output from enablement script:
Install NNM iSPI Performance Server on host NPSHost.domain.com. Use the iSPI Performance Configuration Utility to: - set <Path to iSPI Performance datafile folder> to: /net/NNMHost.Domain.com/var/opt/OV/shared/perfSpi/datafiles
-->Metrics SPI ETL (E for Extract, T for Transform, L for Load) processes will copy over the raw csv gz files from the final folder of NNMi server, and process the data locally on the Metrics SPI server
So when the problem points to failure in enabling file sharing, it is as good as having no reporting at all.
Second, coming to your point that you are not able to see all reporting options, what exactly do you mean, could you substantiate with a screenshot?
Finally, please visit the following link for more info on how to troubleshoot this, and many other Metrics SPI related problems: