Environment
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3
Novell Business Continuity Cluster 1.2.2
Novell Cluster Services 1.8.8
Novell Identity Manager 3.6.1
Novell Business Continuity Cluster 1.2.2
Novell Cluster Services 1.8.8
Novell Identity Manager 3.6.1
Situation
Trying to BCC-Enable a cluster resource and the objects are not
showing up in the landing zone in the other cluster.
The following errors show up in the IDM trace logs after enabling debug on the drivers.
createEntry -672 ERR_NO_ACCESS
modifyEntry -613 ERR_SYNTAX_VIOLATION
nameToID -601 ERR_NO_SUCH_ENTRY
The following errors show up in the IDM trace logs after enabling debug on the drivers.
createEntry -672 ERR_NO_ACCESS
modifyEntry -613 ERR_SYNTAX_VIOLATION
nameToID -601 ERR_NO_SUCH_ENTRY
Resolution
Make sure the proper rights are given to the user who is assigned
as security equals on each IDM driver.
BCC 1.2.2 Administration Guide for OES 2 SP3
Workaround:
Use the Admin user as security equals on each IDM driver in BCC cluster.
Workaround:
Use the Admin user as security equals on each IDM driver in BCC cluster.
Additional Information
Troubleshooting:
1. Enable IDM debug logging. Follow our BCC 1.2.2 Online documentation.
2. Analyze the IDM trace logs. Look for the following eDirectory type errors.
createEntry -672 ERR_NO_ACCESS
modifyEntry -613 ERR_SYNTAX_VIOLATION
nameToID -601 ERR_NO_SUCH_ENTRY
When you BCC enable an NSS cluster resource, the IDM driver will create 4 objects in the destination cluster.
- Cluster resource object which will reside in the cluster container.
The other 3 objects will be in the landing zone container specified in the IDM driver config.
- Virtual NCP server object
- Pool object
- Volume object.
1. Enable IDM debug logging. Follow our BCC 1.2.2 Online documentation.
2. Analyze the IDM trace logs. Look for the following eDirectory type errors.
createEntry -672 ERR_NO_ACCESS
modifyEntry -613 ERR_SYNTAX_VIOLATION
nameToID -601 ERR_NO_SUCH_ENTRY
When you BCC enable an NSS cluster resource, the IDM driver will create 4 objects in the destination cluster.
- Cluster resource object which will reside in the cluster container.
The other 3 objects will be in the landing zone container specified in the IDM driver config.
- Virtual NCP server object
- Pool object
- Volume object.