Note: Per the KB, you can't have a "-" in the VIF name.
yeah, I'm a bit pissed on that "specialist" who setup the Storage I will have to delete the VIF and recreate it ha ? I should do that via BMC or Console, if I do it via Systemmanager I will lose Connection once deleted.
F*** I didnt want to do a complete base setup of the Filer
After deletion of the VIF is it possible to create a new VIF with out an IP like it is now. I mean that only the VLANs have IP's ?
or does the VIF it self always need an IP ?
Is it a "public" subnet in the Internet sense? Or public to the rest of your company?
not in sense of Internet I mean public to the rest of the company.
Hard to design in a forum, but if you have a VLAN-capable GbE switching infrastructure, there's no reason you can't put 3 VLAN's on the VIF: Public, NFS, iSCSI. Your default route entry would point out the Public subnet, allowing the filer to reach big "I" and other subnets for AutoSupport, DNS, NTP, SNMP, etc. You might want to try CLI if System Manager doesn't let you do this, for some reason.
I have VLAN-capable switches but im not sure if I should leave the basic IP of the Filer (without a VLAN) in the "public" subnet ... sure creating VLANs would separate NDS and ISCSI.
Have other companies also have the basic IP of the filer in the normal subnet and create VLANs for Storage traffic ?
BTW, I noticed you're running 7.3.5P1 - You should move off this release (7.3.6 would be ideal) as soon as possible.
Details: http://now.netapp.com/NOW/products/csb/csb1106-03.shtml
this seems very important to you, the 7.3.5P1 has not yet fixed this Excessive SCSI recovery scans error hasn't it ? the version where it was fixed is 7.3.51P1 or are they the same ?