NSM 3.1.1 agent

When trying the upgrade to NSM agent 3.1.1 on SLES 10 Sp4 x64 servers, I receive the following:
error: Failed dependencies:
libxml2.so.2(LIBXML2_2.4.30)(64bit) is needed by novell-storagemanager-agent-3.1.1-17.x86_64
libxml2.so.2(LIBXML2_2.5.2)(64bit) is needed by novell-storagemanager-agent-3.1.1-17.x86_64
libxml2.so.2(LIBXML2_2.6.0)(64bit) is needed by novell-storagemanager-agent-3.1.1-17.x86_64
I checked and both libxml2 and libxml2-32bit (version 2.6.23) are installed. The Engine and Event installed without issue.
The version upgrading from is 3.0.3-18.

Issue resolved. I contacted NSM support and it turns out that the ISO I downloaded was an older version that exhibited this issue. Downloaded the updated ISO and no more issues.

Similar Messages

NSM 3.0.4 Agent Not Starting

Hi,
I've just installed NSM 3.0.4 Agents (from the 3.0.4 iso) on OES11 (with all updates), and the agent is failing to start properly.
Here's what nsmagentd.log says:
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 Initializing Logger, re-opening existing log file "/var/opt/novell/storagemanager/agent/log/nsmagentd-20
120709-154311.log".
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 This Logger class instance [0xa0b0f0] was initialized at 2012:07:09:16:57:44 in Process ID # 1408.
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 OS Version Info = "Kernel Name: Linux, Architecture: x86_64, Kernel Release: 2.6.32.59-0.3-default, Kern
el Version: #1 SMP 2012-04-27 11:14:44 +0200, Machine HW Name: x86_64", OS Bits = 64, Application binary file spec = "/opt/novell/storagemanager/agent/bin/ns
magentd", Application Bits = 64, Application Version = "v3.0.4.11".
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 This is the first time that a Logger thread has been started for this class instance.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Thread has started.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting Operational Data [Phase I]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent's instance name = "".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is getting configuration path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed getting configuration path information, Result = 0, bOK = 1, path = "/etc/opt/novel
l/storagemanager/agent/config".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is getting program path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed getting program path information, bOK = 1, path = "/opt/novell/storagemanager/agent
/bin".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed getting Operational Data [Phase I], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Initializing the Configuration...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Validating data path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed validating data path information, Data Path = "/var/opt/novell/storagemanager/agent/data"
, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Configuring the Logging subsystem [Phase II]...
82 2012-07-09 16:57:44 3600 0 ff04 1408 7f180acb5700 <CONFIG><LOGPATH>/var/opt/novell/storagemanager/agent/log</LOGPATH></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff05 1408 7f180acb5700 <CONFIG><LOGFILEBASENAME/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff05 1408 7f180acb5700 <CONFIG><LOGFILEBASENAME>nsmagentd</LOGFILEBASENAME></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff07 1408 7f180acb5700 <CONFIG><ROLLOVERTYPE>2</ROLLOVERTYPE><FILESTORETAIN>10</FILESTORETAIN><FILESIZEMAX>10485760</FILESIZEMA
X></CONFIG>
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed configuring the Logging subsystem [Phase II], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting Operational Data [Phase II]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Setting the XML Message Signature object...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed setting the XML Message Signature object, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Setting the SSL/TLS certificate file...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed setting the SSL/TLS certificate file, sCertFileSpec = "/etc/opt/novell/storagemanager/age
nt/config/server.pem", bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is determining its own FQDN node name...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed determining its own FQDN node name, Result = 0, bOK = 1, Name = "zeus".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is getting O.S. version information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed getting O.S. version information, Result = 0, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is getting file version information for itself ["/opt/novell/storagemanager/agent/bin/nsmagen
td"]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed getting file version information for itself ["/opt/novell/storagemanager/agent/bin/
nsmagentd"], Version = "3.0.4.11", Result = 0, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed getting Operational Data [Phase II], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loading saved state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loading the Salt state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loaded the Salt state information, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed loading saved state information, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting Operational Data [Phase III]...
01 2012-07-09 16:57:44 3600 2 0001 1408 7f180b4b6700 ML: Completed getting Operational Data [Phase III], bOK = 0.
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff09 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2012-07-09 16:57:44 3600 3 0001 1408 7f180b4b6700 ML: Called LoadStorageResourcesFromCache(), Result = 53.
01 2012-07-09 16:57:44 3600 1 0001 1408 7f180b4b6700 ML: Failed to initialize 1 or more components and/or subsystems. Agent is switching to stop-pending st
ate.
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff09 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is shutting down...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saving state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saving the Salt state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saved the Salt state information, bResult = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed saving state information, bOK = 1.
01 2012-07-09 16:57:44 3600 2 0001 1408 7f180b4b6700 ML: Agent has shut down. Thread is terminating...
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 Shutting down the Logger. Closing log file "/var/opt/novell/storagemanager/agent/log/nsmagentd-20120709
-154311.log".
81 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 <LOGFILECLOSE/>
Hope you can help!
Anthony

Did you run the agent-config? With 3.0.4 you need to generate a new server security certificate.
NSM Support
>>> psc<[email protected]> 7/9/2012 12:06 PM >>>
Hi,
I've just installed NSM 3.0.4 Agents (from the 3.0.4 iso) on OES11
(with all updates), and the agent is failing to start properly.
Here's what nsmagentd.log says:
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 Initializing
Logger, re-opening existing log file
"/var/opt/novell/storagemanager/agent/log/nsmagentd-20
120709-154311.log".
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 This Logger class
instance [0xa0b0f0] was initialized at 2012:07:09:16:57:44 in Process ID
# 1408.
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 OS Version Info =
"Kernel Name: Linux, Architecture: x86_64, Kernel Release:
2.6.32.59-0.3-default, Kern
el Version: #1 SMP 2012-04-27 11:14:44 +0200, Machine HW Name: x86_64",
OS Bits = 64, Application binary file spec =
"/opt/novell/storagemanager/agent/bin/ns
magentd", Application Bits = 64, Application Version = "v3.0.4.11".
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 This is the first
time that a Logger thread has been started for this class instance.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Thread has
started.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting
Operational Data [Phase I]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent's
instance name = "".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
getting configuration path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed getting configuration path information, Result = 0, bOK = 1,
path = "/etc/opt/novel
l/storagemanager/agent/config".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
getting program path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed getting program path information, bOK = 1, path =
"/opt/novell/storagemanager/agent
/bin".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
getting Operational Data [Phase I], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Initializing
the Configuration...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Validating
data path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
validating data path information, Data Path =
"/var/opt/novell/storagemanager/agent/data"
, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Configuring
the Logging subsystem [Phase II]...
82 2012-07-09 16:57:44 3600 0 ff04 1408 7f180acb5700
<CONFIG><LOGPATH>/var/opt/novell/storagemanager/agent/log</LOGPATH></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff05 1408 7f180acb5700
<CONFIG><LOGFILEBASENAME/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff05 1408 7f180acb5700
<CONFIG><LOGFILEBASENAME>nsmagentd</LOGFILEBASENAME></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff07 1408 7f180acb5700
<CONFIG><ROLLOVERTYPE>2</ROLLOVERTYPE><FILESTORETAIN>10</FILESTORETAIN><FILESIZEMAX>10485760</FILESIZEMA
X></CONFIG>
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
configuring the Logging subsystem [Phase II], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting
Operational Data [Phase II]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Setting the
XML Message Signature object...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
setting the XML Message Signature object, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Setting the
SSL/TLS certificate file...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
setting the SSL/TLS certificate file, sCertFileSpec =
"/etc/opt/novell/storagemanager/age
nt/config/server.pem", bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
determining its own FQDN node name...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed determining its own FQDN node name, Result = 0, bOK = 1, Name
= "zeus".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
getting O.S. version information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed getting O.S. version information, Result = 0, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
getting file version information for itself
["/opt/novell/storagemanager/agent/bin/nsmagen
td"]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed getting file version information for itself
["/opt/novell/storagemanager/agent/bin/
nsmagentd"], Version = "3.0.4.11", Result = 0, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
getting Operational Data [Phase II], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loading saved
state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loading the
Salt state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loaded the
Salt state information, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
loading saved state information, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting
Operational Data [Phase III]...
01 2012-07-09 16:57:44 3600 2 0001 1408 7f180b4b6700 ML: Completed
getting Operational Data [Phase III], bOK = 0.
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff09 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2012-07-09 16:57:44 3600 3 0001 1408 7f180b4b6700 ML: Called
LoadStorageResourcesFromCache(), Result = 53.
01 2012-07-09 16:57:44 3600 1 0001 1408 7f180b4b6700 ML: Failed to
initialize 1 or more components and/or subsystems. Agent is switching
to stop-pending st
ate.
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff09 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
shutting down...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saving state
information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saving the
Salt state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saved the
Salt state information, bResult = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
saving state information, bOK = 1.
01 2012-07-09 16:57:44 3600 2 0001 1408 7f180b4b6700 ML: Agent has
shut down. Thread is terminating...
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 Shutting down the
Logger. Closing log file
"/var/opt/novell/storagemanager/agent/log/nsmagentd-20120709
-154311.log".
81 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 <LOGFILECLOSE/>
Hope you can help!
Anthony
psc
psc's Profile: http://forums.novell.com/member.php?userid=6819
View this thread: http://forums.novell.com/showthread.php?t=457694

NSM does not create homedirs in an OES2-Linux-Cluster

Our situation:
The NSM Engine 2.5.1.1 (Jan 12 2010 15:30:55) is running under Netware6.5SP8, on the same server are also a NSM Event Monitor and a NSM Agent. We have a second server under SLES10SP3/OES2a with the Agent and Event Monitor running. While both Event servers can be seen with the NSM-Admin appliction the agent server configuration window displays only the Netware server, and the "eligible agent server" list consists only of Netware boxes.
The Netware and the Linux server contain both the complete replica of all partitions of our NDS-tree. Because we are on transition from Netware to Linux we deploy both Netware and Linux clusters (NCS)
The problem:
On our Netware-cluster (NW6.5SP8) NSM is able to perform all operations (create homedir, move homedir, delete, browse with the Path Analysis tool). Neither does the Linux cluster. No homedirs are created. While the clustered volumes occure in the volume list, with the Path Analysis tool it isn't possible to browse these volumes. No directory tree of these clustered volumes is displayed, but an error message instead: "Policy paths are unreachable". Non clustered volumes on the Linux boxes (including NSS-Volumes SYS and VOL1) can be browsed with the Path Analysis tool.

Hello,
I applied the last updates (no more warning signs in NSM-Admin-Tool) and after this the agent hosted on the linux box is visible in the Admin-Tool.
While rebuilding the volume list the following two kinds of messages appear:
For Netware-Cluster Volumes
01/06 16:13:52 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWKS.C2.UKJ) doesn't exist; Result = -603.
01/06 16:14:02 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWP03V.C2.UKJ) doesn't exist; Result = -603.
01/06 16:14:11 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWP04V.C2.UKJ) doesn't exist; Result = -603.
01/06 16:14:21 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWP05V.C2.UKJ) doesn't exist; Result = -603.
01/06 16:14:30 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C2_NWP06V.C2.UKJ) doesn't exist; Result = -603.
For Linux-Cluster Volumes
01/06 16:15:53 3: GetSERVERObjectsFromDSContainer: Failed to get the product version information for server (C3_NL3A01S.C3.UKJ); Result = 35073.
01/06 16:15:53 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C3_NL3A02S.C3.UKJ) exists (NSS /media/nss/NL3A02S); Result = 0.
01/06 16:15:56 4: GetServerConnection: open connection rc=35073 <C3_NL3A02P_SERVER>
01/06 16:16:00 4: GetServerConnection: open connection rc=35073 <C3_NL3A02P_SERVER>
01/06 16:16:00 3: GetSERVERObjectsFromDSContainer: Failed to get the product version information for server (C3_NL3A02S.C3.UKJ); Result = 35073.
01/06 16:16:01 4: GetVolumeFSTypeAndMountPointPath: The linuxNCPMountPoint attribute for volume FDN (C3_NL3G01S.C3.UKJ) exists (NSS /media/nss/NL3G01S); Result = 0.
01/06 16:16:03 4: GetServerConnection: open connection rc=35073 <C3_NL3G01P_SERVER>
Any suggestions?
Greetings
M.

Cross-Empire Data Migration - DST?

We are still evaluating NSM 3.0.4 Cross-Empire Data Migration....
It looks like the migration doesn't work with Dynamic Shadow Technology (DST) shadow volumes....
I thought that seeing as the NSM Engine and/or Agent doing the migration has to have the Novell client installed that it would be able to migrate from both the primary and shadow volumes...
However, our initial testing shows that it is ignoring the shadow based data...
Is this an oversight? Use of incorrect/outdated API?
Has anyone else any experience of this? We have rather a larger amount of data in our shadow volumes....!
Cheers
David

djbrightman,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

NSM Event Agent for AD location - Best practice

Hello,
We are currently designing our NSM 3.1 for AD implementation and would like some guidance with regard to installing the NSM Event Agent. We have come up with two options:
The first option is to install the NSM Event Agent on a Domain Controller where new user accounts are provisioned.
The second option is to install the NSM Event Agent on a server with the other NSM components.
The argument for option 1 is that NSM will be notified as soon as an account is created.
The argument for option 2 is that MS best practice is that no other software should be installed on a DC and that the NSM Event Agent will perform a network request to talk to the nearest domain controller to obtain a list of changes since it last connected.
Is there any preferred option, or does it not matter?
Regards,
Jonathan

On 10/28/2013 7:16 AM, JonathanCox wrote:
>
> Hello,
>
> We are currently designing our NSM 3.1 for AD implementation and would
> like some guidance with regard to installing the NSM Event Agent. We
> have come up with two options:
>
>
> - The first option is to install the NSM Event Agent on a Domain
> Controller where new user accounts are provisioned.
> - The second option is to install the NSM Event Agent on a server with
> the other NSM components.
>
>
>
> The argument for option 1 is that NSM will be notified as soon as an
> account is created.
> The argument for option 2 is that MS best practice is that no other
> software should be installed on a DC and that the NSM Event Agent will
> perform a network request to talk to the nearest domain controller to
> obtain a list of changes since it last connected.
>
> Is there any preferred option, or does it not matter?
>
> Regards,
>
> Jonathan
>
>
Jonathan,
Unlike eDirectory event monitoring, Active Directory event monitoring is
accomplished with a polling mechanism. Therefore putting your Event
Monitor on the domain controller will not significantly increase
performance. As long as the Event Monitor is in a site with a domain
controller, it should pick up events as quickly as it can.
For further reading on AD sites and domain/forest topology we recommend
reviewing http://technet.microsoft.com/en-us/l.../cc755294.aspx.
Remember that for AD, NSM requires only one Event Monitor per domain
(and in fact you'll only be able to authorize one Event Monitor per
domain through the NSM Admin client.) However, deploying a second Event
Monitor as a backup may be helpful. When the AD Event Monitor is
installed and configured for the first time, it first has to build a
locally-cached replica of the domain it resides in. In a large domain
this can take a long time, so having a second EM already running, which
can be authorized immediately if the primary EM goes down, will ensure
that you catch up with events in AD more quickly.
-- NFMS Support Team

NSM Agent (MS Hotfix)

Hello,
Im looking at preparing our file servers for the NSM agent (NSM 3.1 for AD) and the documentation states that MS HotFix 973278 needs to be installed on Windows Server 2008/2008 SP1/2008 R2.
When Ive look at the hotfix, it is only for Vista/Server 2008. Additionally, if you try to install this hotfix on 2008 R2, I give a message that The update is not applicable to your computer. is there a different hotfix for 2008R2 or is the an error in the documentation?
Regards,
Jonathan

On 10/1/2013 5:06 AM, JonathanCox wrote:
>
> Hello,
>
> I�m looking at preparing our file servers for the NSM agent (NSM 3.1 for
> AD) and the documentation states that MS HotFix 973278 needs to be
> installed on Windows Server 2008/2008 SP1/2008 R2.
>
> When I�ve look at the hotfix, it is only for Vista/Server 2008.
> Additionally, if you try to install this hotfix on 2008 R2, I give a
> message that �The update is not applicable to your computer.� � is there
> a different hotfix for 2008R2 or is the an error in the documentation?
>
> Regards,
>
> Jonathan
>
>
Jonathan,
This documentation is incorrect; the hotfix is required for Server 2008,
but not for Server 2008 R2 (and as you said, it won't install on R2
anyway.) The change applied by that Microsoft hotfix was included in
Server 2008 R2 and later.
-- NFMS Support Team

NSM 3.1 Agent Heartbeat

Hello,
i'm testing a new install of NSM 3.1 on a new Windows 2008 R2 installation to see if we can migrate from 3.0.3 to 3.1
But as soon as i Authorize the (local) agent i get a "Warning: A heartbeat has not been received for more then 5 minutes."
i have put login on the agent en engine to debug but the only usefull info is from the agent log:
Successfully performed a heartbeat communication
Received a "ACK" HB response
Received an "Authorized" HB response, nStatus = 0.
there is noting in the engine log.
Hope you can help me,
Niels van de Haar

On 4/24/2013 6:26 AM, nvdhaar wrote:
>
> Hello,
>
> i'm testing a new install of NSM 3.1 on a new Windows 2008 R2
> installation to see if we can migrate from 3.0.3 to 3.1
>
> But as soon as i Authorize the (local) agent i get a "Warning: A
> heartbeat has not been received for more then 5 minutes."
>
> i have put login on the agent en engine to debug but the only usefull
> info is from the agent log:
>
> Successfully performed a heartbeat communication
> Received a "ACK" HB response
> Received an "Authorized" HB response, nStatus = 0.
>
>
> there is noting in the engine log.
>
> Hope you can help me,
>
> Niels van de Haar
>
>
Niels,
This is a cosmetic UI issue we recently discovered in NSM 3.1 (and in
Novell File Reporter 2.0.0 as well.) The Agent is actually heartbeating
just fine and will work without issue. However, when the Engine and
Agent are in timezones between UTC+1 and UTC+14, the UI incorrectly
calculates the time between heartbeats and displays this error.
A fix for this problem has already been implemented for forthcoming
releases of Storage Manager and File Reporter. Our apologies for the
confusion it creates!
- NFMS Support Team

Needing to migrate/upgrade NSM 3.02.76 from OES2 to OES11

Currently running on OES2 SP2a server. NSM version 3.0.2.76
Need to upgrade to new server. New server is OES11 SP1. Also would like to upgrade to latest NSM version.
Do I need to upgrade in place now and then move to new server? Can OES2 SP2a even run NSM 3.1?
Looked at documentation some, but don't see clear process on moving NSM to new server.
I didn't find any tips in the Discussion forum.
You've given me tips in the past and they have always worked great.
Can you point me to documentation and give best practices in making this upgrade and change.
Any assistance is greatly appreciated.
thanks,
Lin

For the benefit of others doing the same, I'd migrate then upgrade. Here's how I migrated Storage Manager Engine from OES2 to OES11:
1 - Unload old Engine and disable from starting on server boot.
2 - Install NSM Engine on new server, open firewall port 3009, and configure the engine using nsmengine-config, but don't start the engine.
3 - On the new server, rename /var/opt/novell/storagemanager/engine/data to data-original
4 - Copy /var/opt/novell/storagemanager/engine/data from old server to new server, then fire-up the new Engine
5 - Run NSMAdmin against the new server and next your way through the wizard. I had to create a new NSMProxy user, but you can use the existing NSMAdmins group.
6 - Reconfigure Event and Agent servers to point to the new Engine.
Regards,
Anthony

Agent on SLES 10 stops responding

We are running NSM Agent version 2.5.2.1 on a SLES 10 server. Moving student accounts (in the thousdands), the agent stops responding. After unloading and re-loading the agent, it will run for a few minutes, then stop again. Any ideas on how to correct this?
Thanks!
Jos

More information:
I removed the agent from the SLES server. With the engine handling all the moves, all moves complete successfully. It's a bit slower, but definitely more reliable when moving ~16,000 student accounts.
We have two other SLES servers running the agent, and those are fine. However, they are staff and teacher home directories, and when we move accounts it's only a one or two at a time, not thousands.
Hope this information helps.
Originally Posted by NSRDevelopment
Thanks for these added details. We appreciate your help.
NSM Development
>>> jromero<[email protected]> 8/17/2010 3:24 PM >>>
More on this...
Here's the log entry when the engine stops responding:
Aug 17 08:25:24 [SERVER] Agent[24807]: DS: Unable to login to
eDirectory as the proxy object. rc=FFFFFD63
(ERR_FAILED_AUTHENTICATION).
What doesn't make sense is that the engine IS authenticating because a
handful of moves are completed.
Jose
NSRDevelopment;2011197 Wrote:
> Jose,
>
> We have seen that behavior in a couple of installations. We are
> working on finding a cause and a fix as soon as possible.
>
> NSM Development
>
>
> >>> jromero<[email protected]> 8/16/2010 12:06 PM >>>
>
>
> We are running NSM Agent version 2.5.2.1 on a SLES 10 server. Moving
> student accounts (in the thousdands), the agent stops responding.
> After
> unloading and re-loading the agent, it will run for a few minutes,
> then
> stop again. Any ideas on how to correct this?
>
> Thanks!
>
> JosÃ©
>
>
> --
> jromero
> ------------------------------------------------------------------------
> jromero's Profile: 'NOVELL FORUMS - View Profile: jromero'
> (NOVELL FORUMS - View Profile: jromero)
> View this thread: 'Agent on SLES 10 stops responding - NOVELL FORUMS'
> (Agent on SLES 10 stops responding - NOVELL FORUMS)
jromero
jromero's Profile: NOVELL FORUMS - View Profile: jromero
View this thread: Agent on SLES 10 stops responding - NOVELL FORUMS

Agent Communication Fails

$(UI've installed NSM on Netware 6.5 SP7 and NFR on OES2 SP2 64bit in an eDirectory
Environment. I've installed the NFR agent on an OES2 SP2 64bit system. The agent is correctly configured with the IP address of the NFR engine server. The Agent shows up in the NFR Admin Console with a current heartbeat time. I have scheduled a scan of the server, but it always fails.
When I right-click the resource in the resource list and choose "Scan
now" I get the following error message:
Agent Not Available
The agent for APPS/APPS: does not appear to be active.
Check the agent status and try running again.

Chip,
1. You need to upgrade your NSM to version 3.0.2.
2. On your OES servers verify that the alternate server name in the
agent is a case sensitive match to the ncpserver name, and not FDN of
the server.
thanks,
NFR Development
On 8/18/2011 10:46 AM, carneyc wrote:
>
> I am having this same issue.
>
> I have Storage manager and File reporter 3.0.0.129 and File Report
> 1.0.2.99 running on OES2 sp2a. The file reporter agents installled on
> our Netware 6.5 sp7 servers scan fine. The first OES sp3 64 bit server
> that has the file reporter agent for NCP installed fine and displays
> running. I have stopped and started, disabled and enabled the agent and
> I am still getting this Agent Not Available error.
>
> The agent for server_name/volume_name: does not appear to be active.
> Check the agent status and try running the scan again.
>
> Any assistance on this would be greatly appreciated.
>
> Chip
>
>

NSM 3.0.3 Pending Events

Just noticed 32 pending events of which the majority are Event Type (Action):
101:Evaluating Remove Member, and Current State: 2:evaluating user policy.
I'm not sure how to clear those or complete those. 30 of these events are
from user deletes. Two of them are for create user and the action state on
those two are Action: 1: create user, and 10: Verifying paths or waiting
for more paths defined for the poli... Some of the try counts for these events
are in the thousands.
I was running 3.0.2 when I noticed the pending events. I noticed 3.0.3 was
available so I upgraded. I checked that all three NSM services were running
on my SLES10/SP3 box after the upgrade. Server has been restarted. NSM Admin
client was upgraded as well. We are a small school district and have all
three services running on one SLES box (engine, agent, event). I'm not able
to find any errors in places where I know how to look.
All of my user storage (Home directories) are still on one NetWare 6.5SP8
server.
Angie

Angie,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Custom clearing agent payment issue

Dear experts
Purchase order was created and the material was received on port (imports).
custom clearing agent has cleared the goods.
now custom clearing agent needs his charges.
the inv from vendor with reference to PO is not received.
any solution to settle the custom clearing agent payments.
till the inv. from vendor not received custom agent payment is is pending.
what should be done to resolve this issue.

Hi,
Copy one of your freight condition types and create a new condition type as custom clearing charges, please ensure that condition category is Delivery charges (B). In calculation schema enter this condition type at the appropriate position. Now when creating the PO, enter this condition type put the value, then select this condition type and go to details, here you will have a field to enter the vendor code, there key in the vendor code of custom clearing agent.
Now in MIRO enter PO no. and choose layout for Planned delivery cost, you can now enter the value for your agent and pay him.
Note: Please use this to pay only for service charge for the agent, for payment of custom duty you should use the condition type for custom duty and key in the vendor code for the customs clearing office there so that its easy to differentiate between custom duty and the service charges charged by clearing agent.
Regards
Chandra Shekhar

Follow up in IC Agent

HI experts,
I have a requirement where i need to create a follow up of business activity in IC agent ( BZ ROLE : UTIL_IC ). I have developed objects and even getting correct follow up transaction in pop up. When I select the follwo up from POP UP , it should open the view of transaction selected. But nothing is happening on selection.
Can anyone suggest.
Thank you.
Regards,
Vishal

Hi ,
I solved it myself.
Thank you.
Regards,
Vishal

Getting error while running Agent in obiee 11g

Hi,
We are using external table authentication in our application. We created 10 user in the table, when we are logging to the application we are able to log in.
After log in when we are creating Agent and click on run, it is showing error as [nQSError: 13024] Successful completion of init block 'security1' is required. (08004)
Security1 is our initialization block for authentication. But when I create one user in console and give admin priviledges to that user and try to run same agent, it is running fine.
Please let me know if I miss something or anything else need to configure.
Thanks
Anirban

Hope you have strictly followed the steps mentioned in the document:
http://docs.oracle.com/cd/E21764_01/bi.1111/e10543/legacy.htm#BABGEHJJ
Specifically note : Oracle BI Scheduler Server runs Delivers jobs for users without accessing or storing their passwords. Using a process called impersonation, Oracle BI Scheduler uses one user name and password with Oracle Business Intelligence administrative privileges that can act on behalf of other users. Oracle BI Scheduler initiates an Agent by logging on to Oracle BI Presentation Services with the Oracle Business Intelligence administrative name and password.
For Delivers to work, all database authentication must be performed in only one connection pool, and that connection pool can only be selected in an initialization block for the USER system session variable. This is typically called the Authentication Initialization Block. When impersonation is used, this initialization block is skipped. All other initialization blocks must use connection pools that do not use database authentication.
Hope this helps.
Thanks and regards,
Debarati.

Error While executing a SSIS package which contains a script task through SQL Server Agent job

Hi,
I have a SQL Server 2012 SSIS package with a script task along with other tasks [data flow, execute sql tasks ]. When I manually executed the job through BIDS, its completed successfully.
Then I have automated the execution of the package through SQL Server Agent Job. But when I executed the package through SQL Agent job, it runs successfully for all the tasks except script task. When it comes to execute the Script Task, it is getting failed
with the below error message.
"Error: 2012-08-29 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
I have installed the SSIS on the 64-bit environment and SSIS service is running. Also I tried to run the job through 32 bit [job option] but I am getting the above error in all cases.
Any help will be greatly appreaciated !
Thanks,
Navin
- naveen.reddy

Hi Arthur,
My script task access the excel files in a network share, refresh them all and save them. When I execute the ETL manually or thru DTEXEC, it is executing successfully. I am facing the issue when I am executing thru SQL Agent Job only. Logging also showing
the same error.
"Error: 2012-08-23 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
- naveen.reddy

NSM 3.1.1 agent

Similar Messages

Maybe you are looking for