I've got a requirement to use vfilers and ipspaces to segregate network traffic to a NetApp filer in a multi-tenancy environment.
Unfortunately, most of it has already been implemented and designed, so we're investigating how to retrofit this.
Our initial model had vfilers with 3 interfaces - management, backup and 'data'. Multiple vfilers would all use management and backup, but they'd have their own dedicated 'data' vlan and subnet, which would then be presented into the different network segments as appropriate.
The advantage of ipspaces is it segregates interfaces, such that each logical interface can only belong to one ipspace. This means we can't have common management and backup on each of the vfilers any more. (At least, not without doing some somewhat nasty things like multiple vlans within the same subnet)
I think we've figured out how to deal with the backups, in that we can use the base filer to do snapvaults (and thus can remove the need for the 'backup' interface).
However what I'm stumbling on now is the 'vol0' export - we mount vol0 from all the vfilers on a management host, and we also mount some of the home drive structure, so we can create qtrees and set initial ownership and skeleton files, because we don't want to give out root access.
I suspect the answer will be "You can't" but on the offchance - is anyone able to tell me if there's a way to export vfiler vol0 (and assigned vfiler volumes) from the base vfiler0, in a different IP space?