Working on a POC with mixed or multi protocol access to the same files.  NFS and SMB.  Customer has AD and NIS servicing ~2,000 users.  Most of the users have identical user ID's for Windows and Unix.  However there are ~300 legacy users that have different Windows ID's vs Unix.  WIth VNX or NetApp we would just use a usermapper file.  Not so with Isilon.  BTW running OneFS 7.0.1.5

I first tried to create a user mapper rule that maps (joins) the Windows  user to the Unix user.  Rule is in place and I can see it in the system access zone.  When I create a dir on the share I see that the Windows user owns the dir.  However when I look at it from the NFS side I see that the owner is a randomly auto generated UID/GID in the 1,000,000 range.  I would expect OneFS to have used my mapping and looked to NIS for the proper UID/GID.  But no.  It would appear that OneFS looked at the Windows ID, found it in AD, then took the same ID and tried to find it in NIS, which it obviously won't find.  User mapper rules  out.

  Next I tried manually adding the mapping into the ID mapper DB using

# isi auth mapping modify --sourece-user=DOMAIN\Winuser target-user=unixuser --on-disk

I did an isi auth mapping dump and I see the mapping.  I did a ID mapper clean before entering my mapping to ensure nothing else was in the DB.  Next I go try my test of creating a dir in Windows.  Results are the same as above. Randomly generated UID/GID.  What is even more interesting is when I dump the ID Mapper DB again I can still see my manual mapping, but I now also see a new mapping of my Windows SID mapped to the random generated UID.

In both instances it is as if OneFS isn't looking at any mappings I have created. OneFS seems to be looking at the AD ID and using it instead of look to see if there might be a mapping.

  I listened to Mr Wrights great Webex on AIMA but I wasn't able to glean what I might be missing.  Anyone have some ideas?