You could also have the source DSM "tag" it when forwarding the message; use the overrides tab on the FORWARD action to insert data into either the source or category fields...
Alternately, you could use a variable... use the EXPORT action to set &MSGRECEIVED to 1 when you send the SENDOPER. At the beginning of the action sequence, test if &MSGRECEIVED = 1 before SENOPERing...
There's a few answers to this question, so experiment with each and see which fits your needs.
First, agents can be configured to retain trap history - that is, a copy of each trap it has sent to its DSM - for x number of traps. That number is configurable, and on some agents you can configure...
Look here: http://supportconnectw.ca.com/premium/unicenter30/manuals/nsm-docman.asp
Make sure to hit the first link, above the SDKs and Reference Guide...
It's not gonna happen... CCI maintains a constant connection, and only performs a DNS lookup when the connection is first formed (ie, at agent/manager startup).
The only way to handle failover here is with a cautil script that alter's the station name field in a search/replace manner...
I'm not familiar with the Workload agents in particular, but for CCI & name resolution I've chased my tail a few times...
Before you switched the name in the station record, did you create a CCI connection to the alias name in the EM Connection Manager app (or manually edited the cci files)...
First thing to try is to edit d:\blat\script.bat and add
exit
at the end...
If that doesn't help, log in with the nsm_admin account and try running the script from a cmd session with
start d:\blat\script.bat dummyhost "text.."
This will allow you to see if it is failing, or having problems...
are you sure your messages are being sent? Check blat's logs (and the mailserver's logs) to make sure.
The extra cmd's in the process list are running in another context besides the desktop - most likely, caunint's context (if that's the account Event Management runs under). On the view menu of...
awservices status will show you the status of all agentworks services - including the agents, the dsm, common services, and the related services to the dsm.
if you want to see a particular agent, you can type the name of the agent followed by status - like this:
caiW2kOs status
If it's...
When you say you deleted the ca_appsw folder, I assume you did that as part of the reinstall and not post-install?
Try running the following commands:
awservices stop
awservices start -m
aws_orb start
aws_sadmin start
caiw2kos start -l 4
then look in %agentworks_dir%\agents\logs\caiw2kos.log...
Unicenter Explorer uses a metadata system known as a "catalog" to locate and collect information sources. During installation of UE, you should have had to answer a prompt identifying your global catalog server; did you enter the appropriate server?
The typical installation houses the GC on the...
Issues specific to Win2K3? No.
Issues specific to ServiceDesk or NSM? Sure, plenty - mainly because we were new to the products, and hadn't been to training yet...
Someone's feeding you a line...
I've been using W2k3 since release on my entire NSM and USD infrastructure globally - it is by far more stable than Win2K.
We've seen cases where some agents don't write their configuration back to the local sadmin store without either a mkconfig being issued against it or cycling of the agent. As such, we've made it standard procedure to both mkconfig and cycle the agent after tuning...
Since we instituted the...
Yep - CA has a decent guide for it. Look in supportconnect, search documentation for Unicenter - Network and Systems Management (Unicenter TNG) - All versions for document number J01051-1E...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.