Is there a way to rename a network interface that is assigned to a CIFS server. When I tried it is says I cant do it when its in use. Is there a way to temporarily disable access and then rename it.
seems like we are bit "protective" there - not even stopping CIFS seems to do the trick
If you can do without the interface for a few minutes then you can either disable it (server_cifs -Disable) or easier: - create a new standalone CIFS temp server and use that interface hereby stealing it - then delete temp CIFS server - change the interface name - re-add it to your CIFS server
unfortunatelly no. This process would cause access disruption, but basically you would create a new temporary interface and assign it to your CIFS server, build a temporary CIFS server and assign it interface being used by your current CIFS server. That step will "steal" it from your CIFS servers. Now delete this temporary CIFS server. At this point the interface is available, you can delete it and re-create it with new name. Add this interface back to the original CIFS servers. Create new temporary CIFS server and assing it your temporary interface ...that step will take it away from the original CIFS server and you will be left with just one correct interface. Delete temporary CIFS server and temporary interface. Sorry ..not pretty but works
I did not name it correctly on our primary gateway and need it to match the interface that I have on our secondary gateway for replication to work properly.
Could you do us a favor and take a few minutes to file a Product Enhancement Request (PER) ?
Just go to Powerlink Home > Support > Request Support > Request a Product Enhancement Just select "Celerra General" there and write what you want and why
This goes into product management and engineering and helps us to prioritize enhancements.
While the process takes a while it does happen - for example the ability to modify a CIFS servers NetBios name, aliases and interface were added to Celerra Manager in 5.6
regards Rainer P.S.: anyone else that needs this please do - the number of customers asking for a feature does make a difference.
If its only the destination than I dont understand why the interface would be busy. The destination CIFS server isnt running (unless you failed over the VDM)
Are you sure it isnt another running CIFS server like one on the physical data mover for backup or virus checking that is keeping the interface busy ?
People have mapped drives to the CIFS server, and I assome that DFS would keep an active connection also. So if I stop all connections to this server would that allow the interface to be renamed?
One question before I try these steps. What type of interruptions should I expect by doing this? This CIFS server is destination server of one of our primary DFS folders that we have on our DMZ domain.
Rainer_EMC
6 Operator
•
8645 Posts
1265
0
Posted January 29th, 2009 11:00
seems like we are bit "protective" there - not even stopping CIFS seems to do the trick
If you can do without the interface for a few minutes then you can either disable it (server_cifs -Disable) or easier:
- create a new standalone CIFS temp server and use that interface hereby stealing it
- then delete temp CIFS server
- change the interface name
- re-add it to your CIFS server