i have a second level vif comprised of 2x10G and 2x1 Gb interfaces as standby called VIF-NAS. The interface is trunked so there are a couple of VLANs, VIF-NAS-30, VIF-NAS-31, etc. IPspaces are assigned to each interface. Running 8.0.3 and can't seem to be able to add another VLAN from system manager. Getting error "No interfaces are available to create VLAN interface" so it looks like need to disable VIF-NAS in order to be able to add another VLAN. I mirrored the same configuration on a netapp simulator but running 8.1 and it let me add additional VLANs. So curious if it's because of 8.1 or something else? I don't have another physical filer to test on.
Second question is what is the process of removing vfilers and ipspaces and reassigning all volumes back to vfiler0. I tested on netappsim and stop vfiler, reassign interfaces to default ipspace and destroy vfiler. It seems to work but can anybody verify on physical filer?
The same in the vsim. When you destroy a vFiler the volumes go back to vfiler0. For interfaces ifconfig them 0.0.0.0 down.
For networking I recommend command line. Then also edit rc and hosts. There are some fixed bugs in system manager for networking but still don't trust it on networking. Cli always works and simple to vlan create, Ipspace assign then carefully edit the same commands in rc
Please don't use the system manager for performing the rc file and vfiler modifications. There is Bug in system manager which screw up your vfiler configuration and rc file. Please use the command line.
The recent news from Netapp:
storage system data inaccessibility issues with NetApp® OnCommand® System Manager.
vFiler® configuration changes made on Data ONTAP® operating in 7-Mode may unintentionally change files in the /etc directory of the vFiler unit.
CIFS changes made using the CIFS Setup Wizard from within OnCommand System Manager on systems running Data ONTAP 8.x operating in 7-Mode unintentionally result in the removal of existing user-created CIFS share definitions.
NetApp recommends that customers discontinue using OnCommand System Manager immediately to: