LDAP groups are not enumerated. OneFS 7.2.1.2 and OpenDJ 2.6.3

Hello,

OpenDJ 2.6.3 is configured as LDAP Authentication Provider on my Isilon 7.2.1.2.

LDAP does not report any issues, LDAP connection is healthy, integration works OK, users get authenticated, no issues here.

Group Query Settings / DN is configured correctly and Isilon can retrieve the list of groups but cannot enumerate the group users.

In the Advanced LDAP Settings I noticed that the Group Members Attribute is configured as ‘memberUid‘. This attribute is called ‘uniqueMember‘ in OpenDJ LDAP Server.

I tried to change Group Members Attribute from ‘memberUid‘ to ‘uniqueMember‘ but still cannot enumerated the group users.

What may be the problem?

Thank you.

Related:

vnx to unity migration ( options for NAS)

Using ndmpcopy from VNX / Unity to VNX / Unity

A Linux ndmpcopy binary is available from support.emc.com

https://download.emc.com/downloads/DL32451_NDMPCopy.zip.zip

it includes a man page

A couple of tips:

– You need to configure a NDMP password both on the src and dst NAS server (sa/da option)

– src path can be a file system or a snapshot – check with CIFS/NFS/ftp that its valid

– dst path has to be on a writeable file system – on a replication destination NAS server you cannot write directly into / since that would be that NAS server root which isn’t writeable

– dst path directory will be created if it doesn’t exist – unless it’s on the NAS server readonly root

– ndmpcopy doesn’t support a single file as the src – so you need to copy at least a directory

– ndmpcopy works file based so src/dst can be any directory in the file system

– user and tree quotas as well as shares need to be recreated seperately on the dst if needed

Example:

Copying from the read-only manual checkpoint called “ro” of file system fs3_multi on a read-only dst NAS server of a Unity system to a writeable file system fs1_multi on another Unity system into directory restored_fs3

service@unknown spa:~> ./ndmpcopy 10.245.19.153:/ro/test_fs3 10.245.19.147:/fs1_multi/restored_fs3 -sa ndmp:NdmpNdmp1! -da ndmp:NdmpNdmp1! -sport 10000 -dport 10000 -level 0

Connecting to 10.245.19.153. Connecting to 10.245.19.147. 10.245.19.153: CONNECT: Connection established.10.245.19.147: CONNECT: Connection established. 10.245.19.153: LOG: SnapSure file system creation succeeds10.245.19.153: LOG: server_archive: emctar vol 1, 13 files, 0 bytes read, 1983480 bytes written

10.245.19.153: HALT: The operation was successful!

Waiting for 10.245.19.147 to halt too. 10.245.19.147: LOG: server_archive: emctar vol 1, 13 files, 1983480 bytes read, 0 bytes written

10.245.19.147: HALT: The operation was successful!

The transfer is complete.

Elapsed time: 0 hours, 0 minutes, 7 seconds

Related:

Why is Application Modernization So Compelling?

EMC logo


There are 2 key drivers behind application modernization:

  • Reducing Cost & Complexity
  • Increasing Speed & Agility

In order to achieve your organizations business goals we will recommend a series of actions based on the real world experience of helping many customers modernize their application portfolio and adopt an agile approach to rapid cloud native application delivery.

Multi-cloud strategy

Do you have control over your application portfolio and can you quickly identify those applications which are the most important to move to a cloud native solution?  Do you know how you should evaluate those workloads to take advantage of all that cloud has to offer?  Which workloads are appropriate to move based on business requirements and do you have the right cloud options to provide to your business?  We have some proven ideas on how to develop a comprehensive multi-cloud strategy based on your unique business needs, current state of technology, industry drivers, and your organizations financial plan.  Developing a shared vision will allow you to establish a foundation upon which you will be able to drive your organization to new heights. You will build a shared vision with a combination of a top-down approach driven from your business Leadership team, for the “WHAT” – which defines outcomes; sets enterprises standards to maintain quality and provide a consistent work environment across the enterprise.  This is augmented through a highly automated and comprehensive bottom-up approach reflecting the state and requirements of IT for the “HOW” – which determines the best approach for achieving the standards defined at the enterprise level.

You can start small with one set of applications and then scale with confidence. Using a series of key questions that help you determine the best disposition for each application, you will validate and build backlogs for your clouds utilizing an aggressive, lean profiling model.

Build Cloud Native applications

Drive cloud native adoption by replatforming and rewriting the “right” applications and we will help define how best to identify them.  We will help you determine whether your old app is ready for cloud native, and if so we will discuss how you can adapt those applications to take advantage of all that Cloud Native offers. We’ll discuss how we apply an automated approach for performing a 12 factor analysis of your applications.

Best of Breed Tools

We will talk you thru the assessment logic and methods that are utilized to perform this analysis in less time and using fewer resources than others in the marketplace.  This DEW Twitter Image Ireduction in time to value, will allow you to compete with startups in your field and move ahead of incumbents in your space.

Be sure to add “Smart App-Modernization Practices: There’s More To A Portfolio Makeover Than Picking Your New Color!” to your Dell EMC World event calendar to learn all of this and so much more.

 

The post Why is Application Modernization So Compelling? appeared first on InFocus Blog | Dell EMC Services.


Update your feed preferences


   

   


   


   

submit to reddit
   

Related:

Re: VNXのDataMoverとCSの時刻同期について

(1)VNXのDataMoverのNTP時刻同期はserver_2.logに出力されますが、CSのNTP時刻同期のログはどこに出力されますでしょうか。

/var/log/messagesにntpdのログとして出力されます

(2)CSとDataMoverは時刻同期をしておらず、それぞれ単体で動作していると認識していますが、正しい理解でしょうか。

はい。それぞれ独立して単体で動いています。

(設定によりDMの参照先NTPサーバをCSにすることは可能です)

(3)DataMoverは単体で動作しているが、CSは両SPと時刻同期を提供している認識ですが、正しい理解でしょうか。

SPも単体でNTP参照をさせることが可能です。NTPの設定がなされていな場合のみCSと時刻同期(というかCSとの時間差が大きくなるとCSに強制補正)されます。

(参考:CelerraやVNXの各コンポーネント(Control Station, DataMover, Storage Processor)におけるNTPサーバーとの同期動作

(4)SPの時刻同期のログはSPlogに出力されると認識していますが、正しい理解でしょうか。

はい。SPlog(Naviseccliのgetlogコマンド)に出力されます。

Related:

Re: convert FA to RF port

Hi,

We have DMX3 with 5773. We have a RF port replicatng to other DMX3 via fibre.

We wanna migrate from first DMX3 to VMAX via FCIP.

Now can, for eg : 7A0 is an existing RA port …can i use 7A1 for another SRDF traffic to VMAX. They both will be RF ports eventually.

I know that we can’t use the port 7A as half FA and half RF as the whole processor is dedicated for RF but here i wanna use them as RF for both.

7A0 in RDFG1 and 7A1 in RDFG2.

Is it possible ??? If not any real reason of wasting other port ???

Thanks

Related: