CUOM 2.0 and ACS 4.0 integration

jprietoruiz · ‎03-14-2007

Hi everybody! I am evaluating CUOM 2.0 integrated with ACS 4.0. I have added two clusters and I have created three users (two of them has full access to only one cluster and the other one has full access to every cluster).

The problem I find is that I cannot see anything in Service Level View. If I change ACS mode to non ACS mode, I am able to see the nodes in Service Level View. Has anybody find this problem before? Is it a bug or is it a problem originated in my enviroment?

Thank you very much.

Regards, Jesus.

Joe Clarke · ‎03-14-2007

All users, or just a subset? What does the group configuration look like in ACS for the users that do not see any nodes? What is your System Identity User, and how is it defined in ACS?

jprietoruiz · ‎03-14-2007

I have the problem with all the users.

The user that has full access to every cluster is the system identity user. It belongs to the 'OM Admins' group, which has every permission (it is a custom shared profile) for cwhp and iptm for three Network Device Groups:

- A NDG that contains the CUOM itself.

- A NDG that contains elements for one cluster.

- A NDG that contains elements for the other cluster.

Other user belongs to 'Cluster1 Admins' group, which has every permission for two NDGs:

- A NDG that contains the Cluster1 elements.

- A NDG that contains the CUOM itself.

The third user belongs to 'Cluster2 Admins' group, which has every permission for two NDGs:

- A NDG that contains the Cluster2 elements.

- A NDG that contains the CUOM itself.

I did not have any problem for registering the applications in ACS. Also, the 'Device Management' features have a normal behaviour according to my users definitions, it seems only Service Level View is failing.

Thanks.

Joe Clarke · ‎03-14-2007

It sounds like your ACS integration is solid, and you've verified other aspects of Common Services/CUOM are showing the devices, so I think you've stumbled upon a new problem with the Service Level View. I don't see any reports of such a problem, so I recommend you open a TAC service request so additional debugging can be done.