SuperUser
 
Posts:26
 |
| 10/13/2004 8:33 AM |
|
I have a problem with my TNG, when I see the values of PROPAGATED_SEV on the "Object Browser", these are (the majority) completely different to the reality.
I.E. with the Node view I can see that the agents in a server X are Normal, but on the Object Browser that same Server is with a value different to 0 (zero = normal)
I'm working with NSM 3.1 GenLevel 0403.
Do you have any idea why it's happen this?
Thank you
Raul |
|
|
|
SuperUser
Posts:26
|
| 10/13/2004 11:12 AM |
|
First off, what status is seen on the map? Is it the same as the DSM from nodeview or is it matching Object browser? Open task manager and verify you see the sevprop and sevpro~1 processes running. Sometimes sevpro~1 shuts down, other times I've noticed they are both running but the incorrect propagated severity is seen. In either case I would recycle sevprop with the following commands:
sevprop stop
Then check task manager again and verify both processes are no longer running, then issue
sevprop start
Check to see if Object browser is reporting the correct status.
-Mike |
|
|
|
SuperUser
Posts:26
|
| 10/13/2004 2:13 PM |
|
Hi Mike
On the map I can see the same status as the nodeview.
Let me tell you that I have a CORe and a DSM in diferent machines, and both has only the "sevprop" process running but no sevpro~1.
I applied the commands sevprop stop and start but nothing happend.
In other hand, I have other TNG (a CORe and DSM in the same machine) where I can see the sevprop and sevpro~1 processes running.
Do you have some idea about my problem? |
|
|
|
SuperUser
Posts:26
|
| 10/13/2004 5:59 PM |
|
Raul,
You should see both of these processes running on the COR server. I would recommend applying the latest sevprop and WV tools patches and see if this helps out.
-Mike |
|
|
|
SuperUser
Posts:26
|
| 10/15/2004 8:56 AM |
|
Mike,
I have added the account "SeverityPropagation" to the administrator group and I have restarted the "CA-Unicenter TNG Severity Propagation" service in both machine (CORe and DSM).
The sevpro~1 process didn┤t appear but the problem changed I mean now the object Browser (propagated_sev) show me the same status as nodeview, but the colour in some objects doesn't change.
I.E. I have a server with memory Critical, but on the map appear green, and if I see the agent its Managed Object Notebook in the tab status appear Critical and with the option Propagate.
I have seen this problem only with memory problem, with other components colours change.
-Raul |
|
|
|
SuperUser
Posts:26
|
| 10/26/2004 6:38 PM |
|
You need to open an issue with CA. What you're experiencing is the same problem I've fought for months. The Sevprop service was not propagating severity changes reliably. The released 6 test patches to fix the problem:
T12A235 T12A248 T360068 T363070 T363072 T363076
If you're running this in a Active Directory (AD) environment, you will have to recycle SevProp, sevpropcom (a.k.a. sevpro~1) rmi_server and startbpv when the group policy is applied because it breaks Sevprop's connection to the repository DB which is WAD according to CA. Also with AD, you may have problems with the way the above services are configured to run. By default they run with the severitypropagation user account. AD may cause them to not run properly unless you have them configured with a domain admin account. |
|
|
|
SuperUser
Posts:26
|
| 10/26/2004 6:42 PM |
|
| I would suggest to get the SEVPROP patches, if this hasn't been done |
|
|
|
SuperUser
Posts:26
|
| 10/26/2004 6:45 PM |
|
| You don't say if you are running a remote DSM or a combined DSM/CORE or if your managers are Windows or something else. Either way, I would start with a reboot of the DSM if possible, or a restarting AWSERVICES. Hope that helps. |
|
|
|
SuperUser
Posts:26
|
| 10/26/2004 6:46 PM |
|
You need to open an issue with CA. What you're experiencing is the same problem I've fought for months. The Sevprop service was not propagating severity changes reliably. The released 6 test patches to fix the problem:
T12A235 T12A248 T360068 T363070 T363072 T363076
If you're running this in a Active Directory (AD) environment, you will have to recycle SevProp, sevpropcom (a.k.a. sevpro~1) rmi_server and startbpv when the group policy is applied because it breaks Sevprop's connection to the repository DB which is WAD according to CA. Also with AD, you may have problems with the way the above services are configured to run. By default they run with the severitypropagation user account. AD may cause them to not run properly unless you have them configured with a domain admin account. Good luck, you're going to need |
|
|
|
SuperUser
Posts:26
|
| 09/16/2005 10:53 AM |
|
Hi all,
I have a similar problem but in my case I see the right state into nodeview while in the 2dmap agent is always green.
I have only thi problem whit the scriptAgt agent....Any Idea?
Thank You For you support |
|
|
|