Hi,

You may consider taking a detailed look at the EMC primus solution - emc116831.

Please check the /nas/server/slot_2/netd file and ensure the old interface is not used by the CIFS server.

Thanks,
Sandip

If you run server_cifs server_2 command - do you find any unused interface mentioned there? It will look like -

server_cifs server_2
server_2 :
256 Cifs threads started
Security mode = NT
Max protocol = NT1
I18N mode = UNICODE
Home Directory Shares DISABLED
Usermapper auto broadcast enabled

Usermapper[0] = [127.0.0.1] state:active (auto discovered)

Enabled interfaces: (All interfaces are enabled)

Disabled interfaces: (No interface disabled)

Unused Interface(s):
if=cge5 l=1.1.1.1 b=1.1.1.255 mac=8:0:1b:42:7b:72

That's not fair then - since the Interface is listed as Unused and you also Disabled it from being used by CIFS service - this should not happen. I guess this is the time to engage Support and clean up the stuff.

By the way - if at all possible, restarting the CIFS service may help. But that may be the last option - so you may try with Support now.

Sorry for not being able to solve your issue
Sandip

Also - try to Disable the Interface from being used by CIFS service by using the following command -

server_cifs server_2 -Disable interface_name

Please let me know, whether this helps.
Thanks,
Sandip

this old interface is listed as "Unused Interface". I just tried to disable it and then delete and still getting this:

server_ifconfig server_2 -delete old_interface
server_2 :
Error 2216: server_2 : old_interface : item is currently in use by CIFS server: CIFSSERVERNAME.company.local

Hmm - in that case - do you find any more details on server_log?

Let me try to search few more things for you - by the way, is it possible to restart the CIFS service? That may be the last option to try.

Thanks,
Sandip

i had taken a look at that solution ..but this file only contains interfaces for CIFS servers residing on physical datamover ..i don't see any interfaces for CIFS servers residing in VDMs.

support chat guy had to defer it to somebody who will have to dial-in into the box.

I see a similar case in the Primus emc101784 - but again the CIFS server here is on the VDM and netd file will not list it up.

So - explore the new Chat feature let us know, what magic Support does
Thanks again for checking it out with us -
Sandip

unfortunatelly i can't bounce CIFS service ..there are other CIFS server in production. I'll open a ticket ..or maybe try the new support chat thingy ?

ok ..it's fixed now. When i looked at "/nas/server/vdm/vdm_1/vdm.cfg" file i did not pay very good attention, take a look:

cifs add wins=128.120.205.1 wins=128.120.205.205
cifs add compname=SATURN.MICROSOFT.LOCAL domain=MICROSOFT.LOCAL interface=omega dns=MICROSOFT.LOCAL interface=saturn
 

you see what's going on ? There are two interfaces (old interface omega and new interface saturn). That's why it would not allow me to delete omega as it was still stuck here. Support guy just deleted it from this file and voila ..i was able to delete it. So when he was done it looked like this:

cifs add wins=128.120.205.1 wins=128.120.205.205
cifs add compname=SATURN.MICROSOFT.LOCAL domain=MICROSOFT.LOCAL interface=saturn

i don't know why but he also deleted dns entry from this file.

just PLEASE do not edit config files yourself

support know the ramifications and they know if other files or NASDB need to be changed as well or if services need to be stopped/restarted

looks like support can remove an interface from the CIFS server if

- the CIFS service on the data mover is stopped

- or in case of a CIFS server on a VDM that VDM is mounted but not loaded

If you find that you need that more often please file a Product Enhancement Report
Personally I think it would be usefull to have to command to just stop/start one CIFS server

i hope they do ..support guy wanted to bounce datamover to fix this issue, when i said "hell no" ..i got production CIFS servers running ..only then he went back and kept researching.

he did not unload the VDM ..he just modifed vdm.conf file, at least that's what he told me.

as a matter of fact i know he did not unload VDM as i have other production CIFS servers on that same VDM.

Message was edited by:
dynamox