Hi Sudipta,
I have a solution for you and I implemented this.
with this solution you don't have to change the paths.
1. Get a cerberus software or any ftp/sftp provided software(I like cerberus)
2.Talk to your F5 people
Reason: put an F5 in the front and the current 7-mode interfaces as a backend members and then when the users hit that IP's F5 will translate to CDOT LIF's
So based on the rules on F5 side they will say ftp/sftp hit any FTP/SFTP server and remaining SMB & NFS traffic route to storage LIF's.
3.talking about the paths:
in 7-mode it will be as /vol/volname rite
so from a cerberus side we can accomplish with out changing the paths like stated below...
create a cifs share from CDOT name any thing like 'ftpshare' so point this ftpshare as a root path in cerberus side. Now comes the actual solution
since there is already a 'ftpshare' exists on the CDOT cluster now create a folder under this share call it has 'vol'
then the share that are currently exists on the 7-mode side you make a junction-path under 'vol' like below...
"/ftpshare/vol/actual7mode share name" (so you have to repeat for all shares on 7-mode side)
cerberus can intergate with AD so all the ftp jobs user id if they use domain account then no issues here...
END result will be like this...
after the cut-over to CDOT. users are not required to change paths since logically on the CDOT side you created under /vol..
so for a incoming ftp job it will hit F5 and based on the service it will route to a ceberus server and with already existing paths it will go there and drop a file like below
/vol/7modevolname/folder/folder/file.
if the traffic is straight SMB then it will route to CDOT LIF's.
Please send me a email if you have any questions on this.