topic Re: One host agent => OSSV not enabled in Active IQ Unified Manager Discussions

One host agent => OSSV not enabled

korns — Thu, 05 Jun 2025 07:22:50 GMT

I have an environment with 10 Linux hosts (kernel 2.6). The hosts had been running with host agents and OSSV for a few months. Agents are 2.7 and OSSV is 2.6. Some hosts have been wiped and re-installed over those months. Previously an admin host had been running/controlling these hosts with dfm 3.8. I recently completely deleted DFM 3.8 (database included), re-installedand am establishing dfm database from ground up.

New dfm has discovered all the filers and agents. All of them but one agent are working as expected. That one (lab-host-1, objID=72) has hostAgentOSSVEnabled set "no". I've tried everything I can think to correct this but can not figure out how. Can anyone see what is different about this one?

[root@admin ~]# dfm agent list
ID   Host Name                         Host Address                              Agent ID         Deleted
---- --------------------------------- ----------------------------------------- ---------------- -------
84 dr-host-1.acme.com                192.168.126.190                           603ce0c02b9e0fec No
78 dr-host-2.acme.com                192.168.126.191                           589f9bfce7337593 No
83 fl-host.acme.com                  192.168.126.201                           38bf6c618f08cc4a No
75 hq-host-1.acme.com                192.168.126.180                           4178b7b8f0be9918 No
308 hq-host-2.acme.com                192.168.126.181                           4ac519bb73bceaca No
72 lab-host-1.acme.com               192.168.126.160                           5a3d7a422697e2b5 No
73 lab-host-2.acme.com               192.168.126.161                           e9845368e40dbfcb No
80 pr-host.acme.com                  192.168.126.202                           254c0c472e9f13db No
85 se-host.acme.com                  192.168.126.203                           4155b54bb077c8dc No
81 tu-host.acme.com                  192.168.126.204                           e6d2c0f39daa039b No

[root@admin ~]# for x in `dfm agent list -q | awk '{print $1}'` ; do printf "host: $x - " ; dfm detail $x | grep -i ossv ; done
host: 84 - hostAgentOSSVEnabled               Enabled
host: 78 - hostAgentOSSVEnabled               Enabled
host: 83 - hostAgentOSSVEnabled               Enabled
host: 75 - hostAgentOSSVEnabled               Enabled
host: 308 - hostAgentOSSVEnabled               Enabled
host: 72 - hostAgentOSSVEnabled               No
host: 73 - hostAgentOSSVEnabled               Enabled
host: 80 - hostAgentOSSVEnabled               Enabled
host: 85 - hostAgentOSSVEnabled               Enabled
host: 81 - hostAgentOSSVEnabled               Enabled

In Protection Manager is says host agent is not detected BUT I'm using a known admin password which seems to work fine. The problem in PM is seen when I try to "Diagnose" this agent

click diagnose

next...

next ...

click next, then error dialogue box with:

=== CLIENT ===
Version=2.3.0.3018
Build=2.3
OS Name=Windows XP
OS Arch=x86
OS Version=5.1

=== ERROR ===
com.netapp.nmf.userinterface.error.ResourceErrorDetails

=== MESSAGE ===
The host agent must have the ossv plugin installed in order to remotely start or stop the ossv service.

=== DETAILS ===
Configuration error found on host. (Error 22328)

=== CORRECTIVE ACTION ===
No suggested corrective action is available.

=== STACK TRACE ===
The host agent must have the ossv plugin installed in order to remotely start or stop the ossv service. (name=EHOSTBADCONFIG,errno=22328,desc=Configuration error found on host.)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at netapp.sumo.toolkit.zephyr.errno.NaErrnoMapperUtil.createExceptionInstance(NaErrnoMapperUtil.java:38)
at netapp.sumo.toolkit.zephyr.errno.NaErrnoMapper.getNaErrno(NaErrnoMapper.java:353)
at netapp.sumo.toolkit.zephyr.errno.NaErrnoException.getNaErrno(NaErrnoException.java:103)
at netapp.sumo.toolkit.zephyr.errno.NaErrnoException.getNaErrno(NaErrnoException.java:162)
at com.netapp.nmf.userinterface.error.ErrorDetailsFactory.createErrorDetails(ErrorDetailsFactory.java:44)
at com.netapp.nmf.userinterface.exception.NaExceptionHandler.handleException(NaExceptionHandler.java:134)
at com.netapp.nmf.datam.hosts.ossv.wizards.OssvWizardUtilities.enableOssvAgent(OssvWizardUtilities.java:1044)
at com.netapp.nmf.datam.hosts.ossv.wizards.diagnose.OssvDisabledDescriptor.aboutToHidePanel(OssvDisabledDescriptor.java:71)
at com.netapp.nmf.userinterface.wizard.ActionController.onNext(ActionController.java:73)
at com.netapp.nmf.userinterface.wizard.ActionController.actionPerformed(ActionController.java:42)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.Dialog$1.run(Unknown Source)
at java.awt.Dialog$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Dialog.show(Unknown Source)
at java.awt.Component.show(Unknown Source)
at java.awt.Component.setVisible(Unknown Source)
at java.awt.Window.setVisible(Unknown Source)
at java.awt.Dialog.setVisible(Unknown Source)
at com.netapp.nmf.userinterface.wizard.Wizard.showModalDialog(Wizard.java:295)
at com.netapp.nmf.datam.hosts.ossv.HostsOssv.showDiagnoseOSSVHostWizard(HostsOssv.java:425)
at com.netapp.nmf.datam.hosts.ossv.HostsOssv$3.doActionCallback(HostsOssv.java:252)
at com.netapp.nmf.userinterface.actionbuilder.ActionBuilder$1.actionPerformed(ActionBuilder.java:341)
at org.bushe.swing.action.BasicAction.propogateActionEvent(BasicAction.java:269)
at org.bushe.swing.action.BasicAction.actionPerformedTemplate(BasicAction.java:243)
at org.bushe.swing.action.BasicAction.actionPerformed(BasicAction.java:224)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

Re: One host agent => OSSV not enabled

amiller_1 — Sun, 18 Oct 2009 23:37:43 GMT

Hmm....might a tcpdump from either box give some clues? (at least show if DFM is knocking on the OSSV door or vice versa)

Re: One host agent => OSSV not enabled

korns — Mon, 19 Oct 2009 15:13:30 GMT

Thanks Andrew. Sounds like a good idea.

I'm not sure I did this the bets way, but I took a tcpdump on both lab-host-1 and the dfm server host called admin. I limited the host to lab-host-1 on both sides, as in:

[root@lab-host-1 ~]# tcpdump host lab-host-1 > tcpdump_lab-host-1.out

-and-

[root@admin ~]# tcpdump host lab-host-1 > tcpdump_admin.out

And then launch Mmgt Console, when into ProtMgr, selected Setup -> Hosts -> OSSV and attempted a Diagnose on lab-host-1 as in original note (getting the same error)

I've attached the tcpdump outputs here. Not sure what to look for ... thanks in advance.

Re: One host agent => OSSV not enabled

korns — Tue, 20 Oct 2009 17:10:54 GMT

I spent a little more time trying to troubleshoot this. I focused in on two hosts, one working (ie; lab-host-2) and one not (lab-host-1). There must be something different. I've found some differences that look a little strange. Below are ps status for both the NetApp Agent and SnapVault which look different. Notice ntap_agent has "-d" vs "start". Does this give anyone a clue? I've re-installed OSSV 2.6 and NHA 2.7 and rebooted lab-host-1 but no luck. It seems like it must be some piece of configuration info on lab-host-1 that isbn't right.

[root@lab-host-1 ~]# ps -ef|egrep "snap|agent"
root      2990     1 0 10:47 ?        00:00:00 /usr/snapvault/bin/svpmgr startup
root      3220     1 0 10:47 ?        00:00:00 /opt/NTAPagent/ntap_agent -d
root      4544 4482 0 11:02 pts/0    00:00:00 egrep snap|agent
[root@lab-host-1 ~]#

[root@lab-host-2 ~]# ps -ef|egrep "snap|agent"
root     18715     1 0 Oct19 ?        00:02:16 /opt/NTAPagent/ntap_agent start
root     18722     1 0 Oct19 ?        00:00:43 /usr/snapvault/bin/svpmgr
root     10668 10621 0 10:56 pts/1    00:00:00 egrep snap|agent
[root@lab-host-2 ~]#

and netstat outputs from each host:

[root@admin ~]# for x in 1 2 ; do printf "\n==== host: lab-host-$x \n" ; ssh lab-host-$x netstat ; done

==== host: lab-host-1
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        0      0 localhost:32770             localhost:20033             ESTABLISHED
tcp        0      0 localhost:32769             localhost:20033             ESTABLISHED
tcp        0      0 localhost:20033             localhost:32770             ESTABLISHED
tcp        0      0 localhost:20033             localhost:32769             ESTABLISHED
tcp        0      0 lab-host-1.acme.com:ssh     laptop.acme.com:2425        ESTABLISHED
tcp        0      0 lab-host-1.acme.com:ssh     admin.acme.com:55443        ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags       Type       State         I-Node Path
unix 2      [ ]         DGRAM                    6721   @/var/run/hal/hotplug_socket
unix 12     [ ]         DGRAM                    5526   /dev/log
unix 2      [ ]         DGRAM                    3233   @udevd
unix 2      [ ]         DGRAM                    11259
unix 3      [ ]         STREAM     CONNECTED     11231
unix 3      [ ]         STREAM     CONNECTED     11230
unix 3      [ ]         STREAM     CONNECTED     11229
unix 3      [ ]         STREAM     CONNECTED     11228
unix 3      [ ]         STREAM     CONNECTED     6720   /var/run/dbus/system_bus_socket
unix 3      [ ]         STREAM     CONNECTED     6719
unix 3      [ ]         STREAM     CONNECTED     6697
unix 3      [ ]         STREAM     CONNECTED     6696
unix 2      [ ]         DGRAM                    6657
unix 2      [ ]         DGRAM                    6653
unix 2      [ ]         DGRAM                    6594
unix 2      [ ]         DGRAM                    6559
unix 2      [ ]         DGRAM                    6545
unix 2      [ ]         DGRAM                    6526
unix 2      [ ]         DGRAM                    6452
unix 2      [ ]         DGRAM                    6444
unix 3      [ ]         STREAM     CONNECTED     5715
unix 3      [ ]         STREAM     CONNECTED     5714
unix 2      [ ]         DGRAM                    5602
unix 2      [ ]         DGRAM                    5534

==== host: lab-host-2
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        0      0 localhost:20033             localhost:1102              ESTABLISHED
tcp        0      0 localhost:1102              localhost:20033             ESTABLISHED
tcp        0      0 localhost:1101              localhost:20033             ESTABLISHED
tcp        0      0 localhost:20033             localhost:1101              ESTABLISHED
tcp        0      0 lab-host-2.acme.com:ssh     admin.acme.com:55444        ESTABLISHED
tcp        0      0 lab-host-2.acme.com:ssh     laptop.acme.com:2426        ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags       Type       State         I-Node Path
unix 14     [ ]         DGRAM                    5720   /dev/log
unix 2      [ ]         DGRAM                    7070   @/var/run/hal/hotplug_socket
unix 2      [ ]         DGRAM                    3269   @udevd
unix 2      [ ]         DGRAM                    102918
unix 3      [ ]         STREAM     CONNECTED     102890
unix 3      [ ]         STREAM     CONNECTED     102889
unix 3      [ ]         STREAM     CONNECTED     102888
unix 3      [ ]         STREAM     CONNECTED     102887
unix 2      [ ]         DGRAM                    62507
unix 2      [ ]         DGRAM                    8214
unix 3      [ ]         STREAM     CONNECTED     7064   /var/run/dbus/system_bus_socket
unix 3      [ ]         STREAM     CONNECTED     7063
unix 3      [ ]         STREAM     CONNECTED     7041
unix 3      [ ]         STREAM     CONNECTED     7040
unix 2      [ ]         DGRAM                    6989
unix 2      [ ]         DGRAM                    6930
unix 2      [ ]         DGRAM                    6880
unix 2      [ ]         DGRAM                    6868
unix 2      [ ]         DGRAM                    6857
unix 2      [ ]         DGRAM                    6831
unix 2      [ ]         DGRAM                    6742
unix 2      [ ]         DGRAM                    6727
unix 3      [ ]         STREAM     CONNECTED     5965
unix 3      [ ]         STREAM     CONNECTED     5964
unix 2      [ ]         DGRAM                    5797
unix 2      [ ]         DGRAM                    5728
[root@admin ~]#

Re: One host agent => OSSV not enabled

korns — Sat, 24 Oct 2009 01:05:18 GMT

For what it's worth, permanently deleting the agent entry on DFM side had no impact. I deleted the agent with -f, let the system re-discovery and now have the same problem trying to 'diagnose' this thing.

[root@admin ~]# dfm agent list
ID   Host Name                         Host Address                              Agent ID         Deleted
---- --------------------------------- ----------------------------------------- ---------------- -------
84 dr-host-1.acme.com                192.168.126.190                           603ce0c02b9e0fec No
78 dr-host-2.acme.com                192.168.126.191                           589f9bfce7337593 No
83 fl-host.acme.com                  192.168.126.201                           38bf6c618f08cc4a No
75 hq-host-1.acme.com                192.168.126.180                           4178b7b8f0be9918 No
308 hq-host-2.acme.com                192.168.126.181                           4ac519bb73bceaca No
72 lab-host-1.acme.com               192.168.126.160                           c87787b56463fa46 No
73 lab-host-2.acme.com               192.168.126.161                           e9845368e40dbfcb No
80 pr-host.acme.com                  192.168.126.202                           254c0c472e9f13db No
85 se-host.acme.com                  192.168.126.203                           4155b54bb077c8dc No
81 tu-host.acme.com                  192.168.126.204                           e6d2c0f39daa039b No
[root@admin ~]#
[root@admin ~]# dfm agent delete -f lab-host-1
Error: Services "http", "eventd", "monitor", "scheduler", "server", "watchdog" are still running.
Run commands

dfm service stop
dfm service start sql

and try again.
[root@admin ~]# dfm service stop
Service: watchdog stopped.
Service: server stopped.
Service: scheduler stopped.
Service: monitor stopped.
Service: eventd stopped.
Service: http stopped.
SQL Anywhere Stop Server Utility Version 10.0.1.3830
Service: sql stopped.
[root@admin ~]# dfm service start sql
Service: sql started.
[root@admin ~]# dfm agent delete -f lab-host-1
Error while sending event host.deleted:ok:
Cannot contact the event server
Deleted host lab-host-1.acme.com (72).
[root@admin ~]# dfm service start
Service: sql started.
Not attempting to start sql because service is started already.
Service: http started.
Service: eventd started.
Service: monitor started.
Service: scheduler started.
Service: server started.
Service: watchdog started.
[root@admin ~]# dfm agent list
ID   Host Name                         Host Address                              Agent ID         Deleted
---- --------------------------------- ----------------------------------------- ---------------- -------
84 dr-host-1.acme.com                192.168.126.190                           603ce0c02b9e0fec No
78 dr-host-2.acme.com                192.168.126.191                           589f9bfce7337593 No
83 fl-host.acme.com                  192.168.126.201                           38bf6c618f08cc4a No
75 hq-host-1.acme.com                192.168.126.180                           4178b7b8f0be9918 No
308 hq-host-2.acme.com                192.168.126.181                           4ac519bb73bceaca No
73 lab-host-2.acme.com               192.168.126.161                           e9845368e40dbfcb No
80 pr-host.acme.com                  192.168.126.202                           254c0c472e9f13db No
85 se-host.acme.com                  192.168.126.203                           4155b54bb077c8dc No
81 tu-host.acme.com                  192.168.126.204                           e6d2c0f39daa039b No

... it's gone, waited 5 minutes, a new entry for it appears

[root@admin ~]# dfm agent list
ID   Host Name                         Host Address                              Agent ID         Deleted
---- --------------------------------- ----------------------------------------- ---------------- -------
84 dr-host-1.acme.com                192.168.126.190                           603ce0c02b9e0fec No
78 dr-host-2.acme.com                192.168.126.191                           589f9bfce7337593 No
83 fl-host.acme.com                  192.168.126.201                           38bf6c618f08cc4a No
75 hq-host-1.acme.com                192.168.126.180                           4178b7b8f0be9918 No
308 hq-host-2.acme.com                192.168.126.181                           4ac519bb73bceaca No
457 lab-host-1.acme.com               192.168.126.160                           c87787b56463fa46 No
73 lab-host-2.acme.com               192.168.126.161                           e9845368e40dbfcb No
80 pr-host.acme.com                  192.168.126.202                           254c0c472e9f13db No
85 se-host.acme.com                  192.168.126.203                           4155b54bb077c8dc No
81 tu-host.acme.com                  192.168.126.204                           e6d2c0f39daa039b No
[root@admin ~]#

... Went into PM to diagnose the agent and get the exact same errors as orignal above.

Re: One host agent => OSSV not enabled

michelvankessel — Fri, 16 Apr 2010 09:07:42 GMT

I have the same problem with one of our customers. DFM 3.8.1 + ontap 7.3.2P5 + OEL 5.4 OSSV. Running NHA 2.7 + OSSV 2.6.1

Kind regards

Michel van Kessel

Re: One host agent => OSSV not enabled

adaikkap — Sat, 17 Apr 2010 03:01:42 GMT

Can you install the ossv plugin?

Also can you check the following in your ossv agent ?

go to /usr/snapvault/bin

and run ./svinstallcheck.and get the output ?

[root@lnxbin]# ./svinstallcheck
SnapVault home directory: '/usr/snapvault'
SnapVault database directory: '/usr/snapvault/db'
SnapVault temporary directory: '/usr/snapvault/tmp'
SnapVault Database and Temporary directories have 13% space left (19642Mb)
SnapVault service is running
SnapVault listener is running
NDMP Server, on port 10000, details:
    Vendor     Netapp
    Product    SnapVault
    Version    2_6_1_2009APR08
    Host       lnx
    Host Id    E1ADC8FCFE184EC8A1D887F33E5782E8
    OS Type    Linux
    OS Version 2.6.9-55.ELsmp
SnapVault QSM Server is responding correctly
Validating filesystems:
   Mount point / (/dev/sda3) is suitable for backup
   Mount point /proc (none) is a special mount, unsuitable for backup
   Mount point /sys (none) is a special mount, unsuitable for backup
   Mount point /dev/pts (none) is a special mount, unsuitable for backup
   Mount point /proc/bus/usb (usbfs) is a special mount, unsuitable for backup
   Mount point /dev/vx (tmpfs) is a special mount, unsuitable for backup
   Mount point /boot (/dev/sda1) is suitable for backup
   Mount point /dev/shm (none) is a special mount, unsuitable for backup
   Mount point /proc/sys/fs/binfmt_misc (none) is a special mount, unsuitable for backup
   Mount point /var/lib/nfs/rpc_pipefs (sunrpc) is a special mount, unsuitable for backup
   Mount point /usr/local (btcinf02.eng.btc.netapp.in:/vol/local/i386-linux2.0) is a remote mount, unsuitable for backup
   Mount point /usr/local/share (btcinf02.eng.btc.netapp.in:/vol/local/share) is a remote mount, unsuitable for backup
   Mount point /usr/software (btcinf01.eng.btc.netapp.in:/vol/software/arch/x86_64-redhat-rhel4) is a remote mount, unsuitable for backup
   Mount point /u (automount(pid4646)) is a special mount, unsuitable for backup
   Mount point /x/eng (automount(pid4684)) is a special mount, unsuitable for backup
   Mount point /x/sim (automount(pid4689)) is a special mount, unsuitable for backup
   Mount point /x/eng/localtest (btcinf02.eng.btc.netapp.in:/vol/localtest) is a remote mount, unsuitable for backup
   Mount point /u/adaikkap (nbhome1.eng.btc.netapp.in:/vol/home1/adaikkap) is a remote mount, unsuitable for backup
NetApp Host Agent is installed on this system.
   Install Location : /opt/NTAPagent
   NetApp Host Agent version 2.7 (2.7.0.2203)
   Agent Core Library version 2.7 (2.7.0.2203)
   Status : Running with PID 4946

Check Succeeded

[root@lnx bin]#

Regards

adai

Re: One host agent => OSSV not enabled

michelvankessel — Tue, 20 Apr 2010 19:18:22 GMT

Dear Adai,

I can install the OSSV agent, but it is NOT making a link to the NetApp Host Agent. It should detect it OR not. It doesn't say anything! Looks like e bug? I will see if we can reinstall the OSSV agent

SnapVault home directory: '/usr/snapvault'

SnapVault database directory: '/usr/snapvault/db'

SnapVault temporary directory: '/usr/snapvault/tmp'

SnapVault Database and Temporary directories have 43% space left (1731Mb)

SnapVault service is running

SnapVault listener is running

NDMP Server, on port 10000, details:

Vendor Netapp

Product SnapVault

Version 2_6_2008MAR10

Host xxxxxxxxxxxx

Host Id 8D0AD034FD1D64B68610694025E668EE

OS Type Linux

OS Version 2.6.18-164.11.1.0.1.el5

SnapVault QSM Server is responding correctly

Validating filesystems:

Mount point / (/dev/mapper/VolGroup00-root) is suitable for backup

Mount point /proc (proc) is a special mount, unsuitable for backup

Mount point /sys (sysfs) is a special mount, unsuitable for backup

Mount point /dev/pts (devpts) is a special mount, unsuitable for backup

Mount point /tmp (/dev/mapper/VolGroup00-tmp) is suitable for backup

Mount point /var (/dev/mapper/VolGroup00-var) is suitable for backup

Mount point /home (/dev/mapper/VolGroup00-home) is suitable for backup

Mount point /opt (/dev/mapper/VolGroup00-opt) is suitable for backup

Mount point /usr (/dev/mapper/VolGroup00-usr) is suitable for backup

Mount point /boot (/dev/cciss/c0d0p1) is suitable for backup

Mount point /dev/shm (tmpfs) is a special mount, unsuitable for backup

Check Succeeded

If I do it on a test system I get:

SnapVault home directory: '/usr/snapvault'
SnapVault database directory: '/usr/snapvault/db'
SnapVault temporary directory: '/usr/snapvault/tmp'
SnapVault Database and Temporary directories have 59% space left (12077Mb)
SnapVault service is running
SnapVault listener is running
NDMP Server, on port 10000, details:
    Vendor     Netapp
    Product    SnapVault
    Version    2_6_1_2009APR08
    Host       xxxxxxxxxxxxxx
    Host Id    C34D6E241786685B409B6B426D928A8E
    OS Type    Linux
    OS Version 2.6.27.45-0.1-pae
SnapVault QSM Server is responding correctly
Validating filesystems:
   Mount point / (/dev/sda2) is suitable for backup
   Mount point /proc (/proc) is a special mount, unsuitable for backup
   Mount point /sys (sysfs) is a special mount, unsuitable for backup
   Mount point /sys/kernel/debug (debugfs) is an unsuitable mount (mounted under special, remote or excluded mount point), unsuitable for backup
   Mount point /dev (udev) is a special mount, unsuitable for backup
   Mount point /dev/pts (devpts) is a special mount, unsuitable for backup
   Mount point /home (/dev/sda3) is suitable for backup
   Mount point /sys/kernel/security (securityfs) is an unsuitable mount (mounted under special, remote or excluded mount point), unsuitable for backup
   Mount point /proc/fs/vmblock/mountPoint (none) is an unsuitable mount (mounted under special, remote or excluded mount point), unsuitable for backup
NetApp Host Agent is not installed on this system.

Check Succeeded

kind regards

Michel van Kessel

Re: One host agent => OSSV not enabled

adaikkap — Wed, 21 Apr 2010 04:19:17 GMT

Starting OSSV 2.6.1 NHA is not bundled with OSSV installer.

You will have to download and install it separately.

But until OSSV 2.6 NHA was bundled with OSSV installer and you would be asked if you like to install NHA.

Below is the snippet from the install.

Re: One host agent => OSSV not enabled

ludwig_mainguenaud — Tue, 22 Jun 2010 19:09:51 GMT

Same error ... Do you have find some solution please ?

Re: One host agent => OSSV not enabled

sysadmin — Tue, 06 Jul 2010 11:02:38 GMT

I had the very same Problem and solved it by running the command ./InstallHostAgentPlugins.sh.

Hope it helps you too.

Cheers,

Re: One host agent => OSSV not enabled

sjmontiel — Fri, 11 Mar 2011 15:43:52 GMT

hi, where is InstallHostAgentPlugins.sh located?

Re: One host agent => OSSV not enabled

jherlihy1 — Thu, 12 Apr 2012 08:26:46 GMT

Hi,

I'm seeing the same issue with trying to add a Windows 2003 OSSV host - OSSV 3.1 and agent 2.7 with OnCommand 5. I rectified an issue where the NDMP port 10000 on the host was already utilised by using port 10099 instead, but I still get stuck in this loop when trying to add this host. Svinstallcheck comes up clean, and I already have some OSSV relationships established back to the secondary FAS, they're just not visible to DFM/OnCommand as could be expected.

Anyone had any luck?

Cheers,

John

Re: One host agent => OSSV not enabled

korns — Thu, 12 Apr 2012 19:55:32 GMT

Sorry John. It has been a while and it was a lab environment. I can't remember if I ever resolved it or just deleted and re-built a new client (vm) from the ground up

Re: One host agent => OSSV not enabled

xavierpitz — Thu, 19 Jul 2012 16:27:59 GMT

Hello,

I experienced the same problem and this is what I perfomed to solve it :

Before :

<servername>:/opt/NTAPagent # ls -ali

displays the content from /opt/NTAPagent, no file "libsvmanage.so" present in the directory

<servername>:/opt/NTAPagent # /usr/snapvault/manageability/InstallHostAgentPlugins.sh

NetApp Host Agent is installed at /opt/NTAPagent

Stopping the NetApp Host Agent daemon

Starting the NetApp Host Agent daemon

After :

<servername>:/opt/NTAPagent # ls -ali

displays the content from /opt/NTAPagent, file "libsvmanage.so" present in the directory

This .so share object is the plugin and this solved my issue

Re: One host agent => OSSV not enabled

BETFAIRRSPRIDDLE — Tue, 07 Aug 2012 11:14:45 GMT

Did you manage to fix this in the end?

Re: One host agent => OSSV not enabled

opwnetapp — Thu, 14 Feb 2013 12:36:03 GMT

We had the same problem on our Solaris boxes running OSSV 3.0.1 and Host Agent 2.7:

root@SUNBOX # uname -a

SunOS SUNBOX 5.10 Generic_125100-05 sun4u sparc SUNW,Sun-Fire-V245

It looks like everything installs fine, but Protection Manager will never "see" OSSV. The only solution I was able to fine was to uninstall the Host Agent and not use it. The backups run fine enough so I am happy enough to move forward without it.

Bob Brandt