If you're looking for CIFS event auditing, that is, to have a CIFS server log all events (i.e., file open, close, execute attempts), then yes - you must use the Celerra MMC to activate this function.

If you're looking to audit all of the CIFS connections on a given CIFS server, you can do so from the Control Station via putty like this:

$ server_cifs server_2 -option audit

server_2 :

|||| AUDIT Ctx=0xad3d4820, ref=1, W2K3 Client(WINSERVER1) Port=1638/139

||| DM112-CGE0[NASDOCS] on if=cge0

||| CurrentDC 0xad407620=WINSERVER1

||| Proto=NT1, Arch=Win2K, RemBufsz=0xffff, LocBufsz=0xffff

||| 0 FNN in FNNlist NbUsr=1 NbCnx=1

||| Uid=0x3f NTcred(0xad406a20 RC=2 KERBEROS Capa=0x2)

'NASDOCS\administrator'

|| Cnxp(0xad3d5420), Name=IPC$, cUid=0x3f Tid=0x3f, Ref=1, Aborted=0

| readOnly=0, umask=22, opened files/dirs=1

|||| AUDIT Ctx=0xad43c020, ref=1, W2K3 Client(172.24.102.67) Port=1099/445

||| DM112-CGE0[NASDOCS] on if=cge0

||| CurrentDC 0xad407620=WINSERVER1

||| Proto=NT1, Arch=Win2K, RemBufsz=0xffff, LocBufsz=0xffff

||| 0 FNN in FNNlist NbUsr=1 NbCnx=1

||| Uid=0x3f NTcred(0xad362c20 RC=2 KERBEROS Capa=0x2) 'NASDOCS\user1'

|| Cnxp(0xaec21020), Name=IPC$, cUid=0x3f Tid=0x3f, Ref=1, Aborted=0

| readOnly=0, umask=22, opened files/dirs=2

You'll find more information in the CIFS manual in the Celerra Documentation set.

Let us know if this helps!

Karl