last time i had to change ip address on a CIFS server i did not have to delete it (like you had to before). I am just thinking out-loud ..can you uncheck the interface you are using from the CIFS servers, delete interface, then re-create your FSN/LACP and re-assign interface to new device and assign it back to the CIFS server. Not sure how this impacts replication.
Yes, the enhancement that you can directly remove an interface from a CIFS server (and not just add one) got added somewhere in 5.6
What you could always do before it “interface stealing” – create a temp CIFS server and add that interface – it will remove it from its original CIFS server (if that one has more than on interface). Then you can delete the temp CIFS server and old interface
I did some testing and this is what I was able to do. Let me know
if you think there is anything wrong with this process. This
test was done on a non replicated configuration and I am not
100% sure the impact of replication since it would use one
of the IP interfaces on the fail safe network.
Test config:
4 - CIFS Servers
NSTEST100 - VDM100
NSTEMP01 - Server_2
NISCSI01 - Server_2
NSEMCMGMT01 - Server_2
NSTEST100 has a share on it called test and the NTFS permissions
use a machine local group I created to allow a test user to have read only access
to files on share.
1) Record all Network Configuration including FSN, CIFS Servers, Netowrk Interfaces (including VLAN). Once you delete
this you will need to recreate it
2) Right click each CIFS Server and uncheck the interface it is associated with
3) Once all Network Interfaces are seperated from the CIFS Servers, delete each network interface that resides on the FSN you want to reconfigure
4) Delete the FSN
5) Delete the 2 aggregates (trunks) that made up the FSN
6) Create 2 new aggregates (trunks) that will make up the new FSN
7) Create the new FSN
8) Create the 4 network interfaces you deleted using same IP, Subnet, VLAN, etc (at this point you will be happy you recorded this information)
9) Re-associate the appropriate CIFS Server with its IP address
10) Test
After following this procedure, I was able to ping the IPs and was able to access the share on nstest100 and the security permissions appear to be retained.
One issue I appeared to run into was on step 2
When I got to the last CIFS server and tried to uncheck the IP interface, it failed.
For some reason it disabled the interface. I found this by doing a
cifs_server server_2
I then ran the following commands to get the interface back online
cifs_server server_2 -Disable nsemcmgmt01-inf
cifs_server server_2 -Enable nsemcmgmt01-inf
Even though it reported disabled, I had to disable it and then enable it. Just trying to
enable it did not work.
So this process appears to work, assuming I am not missing anything and I am not sure why I would
need a temporary interface.
The area I know I will probably have issues with is replication and I do not have a way to test this easily.
Since replication uses an IP address, it will probably prevent me from deleting the interface for that IP.
I have a feeling I will need to delete the entries under
"Celerra Network Servers" and "Data Mover Interconnects" under replications in the GUI
and do I just have to pause replication to accomplish this?
What would be the procedure to deal with reconfiguring FSN with replication in place?
dynamox
11 Legend
•
20419 Posts
•
87439 Points
800
0
Posted January 5th, 2011 12:00
last time i had to change ip address on a CIFS server i did not have to delete it (like you had to before). I am just thinking out-loud
..can you uncheck the interface you are using from the CIFS servers, delete interface, then re-create your FSN/LACP and re-assign interface to new device and assign it back to the CIFS server. Not sure how this impacts replication.