At your filer console prompt, type in the following:- Your filer name*> options autosupport Make sure you have the correct mail relay validate it using nslookup, and make sure you can ping it. autosupport.mailhost         relay.your_company.com Test the autosupport daemon, you can do this by adding some valid E-mail address to the following option, put in your E-Mail address and two others separated by a “,” no space. autosupport.to               you@yourcompany.com, admin@yourcompany.com, Check the filer for the exact syslog error messages in regard to autosupport, that will give you a lead on what is failing. Thanks, Robert ... View more

Hello  genisysau, Good questions, and a good add on from aborzenkov, thanks! You are trying to achieve a lot of different service options with meager resources; and you want to service iSCSI, NFS and CIFS requests. The FAS2040, has only 4 data NICs; some of the above mentioned configs will work but with out NIC redundancy you may incur downtime, which negates the purpose of a high availability dual controller cluster system like this one. When you use VIF’s you still have to issue the VIF an IP address, if that’s correct, then I believe you will have 3 separate IP’s per controller, for iSCSI, NFS and CIFS services and you only have 4 NICs, you need to go back to the drawing board and plan this right. If you decide to use vif create lacp, make sure that LACP is enabled on your Network switch, this has never worked well for us because at any one time only one port is channeling traffic. You can use vif create multi and use the ip load balancing switch that’s what I recommend. To achieve high network throughput, in many NetApp benchmark illustrations, Jumbo frames has been enabled, and even thought the advantage is less CPU overload because of less header processing. Jumbo frames most legitimate deployment is most seen between trunks, and not client server setups, your clients and intermediate routers MTU will have to be configured to use jumbo frames on their NIC’s, if they are not, then communication will translate to the clients frame size. You cannot load balance, cannot bond the NIC cards on both filers, these are two separate filers with different identities, and the same interface names, .i.e. e0a, e0b, e0c and e0d, designed to be able to take over each others roles, please clarify with Netapp, therefore the configurations should be the same. I recommend going with the Citrix Desktop on ESX hosts instead of the CitrixZen server, we discovered that our full Blade Chassis could only give us 96GB of RAM, for 1000 desktops at 2GB of RAM, VM can over subscribe to 140GB, ZenServer could not. ... View more

genisysau , I forgot, for the Custer Failover both filers should be licensed to run all your protocols, CIFS, NFS ….. ... View more

Hello genisysau, The FAS2040, is a good work horse, we are only running CIFS, but we also have over 13000 users; We procured two of these as an upgrade and believe me, we are very impressed with them, I have them setup 17 miles apart over dark fiber in replication mode running SnapMirror Synchronous. There are several parts to your question, and I don’t have all the answers; VIF’s are really easy to use, once you understand the visual picture, the beauty of the FAS2040, is that it has a total of 8 data ports, four per head and two management ports, (Dual Controller). So this will help  for what you are trying to do,  LACP is a Link aggregation protocol which is really using multiple network ports in parallel to increase of your network pipe and or create redundancy for higher availability. BUT YOUR NETWORK SWITCH HAVE TO SUPPORT IT, Before you complicate your configuration, just ask your network guys, to provide simple port aggregation on the switch, without any sharing information, like LACP, let the ONTAP VIF daemon control all the that stuff, because the commands are really all straight forward on the NetApp side, Just ensure that all interfaces to be included in the VIF are configured to the down status, which means that your management port has to been operational first, unless you have direct console access to the units. You can test different VIF configurations as you decide to separate the different protocol traffic, CIFS, NFS, and iSCSI, the VIF create command is not persistent across reboots unless the command is added to the /etc/rc file, and once you are satisfied with the config, run setup, to lock it into the /etc/rc file. Some helpful stuff; http://now.netapp.com/NOW/knowledge/docs/ontap/rel733/html/ontap/nag/GUID-708701F9-0ED1-4B0D-A1D8-8F0F4DEED03B.html Ours is an enterprise class solution for even higher redundancy, the traffic goes across two switches; Your network guys have to be fully onboard with this solution other wise you can bring the entire network down with a “Broadcast storm” A state in which a message that has been broadcast across a network  results in even more responses, and each response results in still more responses into a snowball effect. A severe broadcast storm can block all other network traffic, resulting in a network meltdown. Broadcast storms can usually be prevented by carefully configuring a network to block illegal broadcast messages. http://now.netapp.com/NOW/knowledge/docs/ontap/rel733/html/ontap/nag/GUID-A293832B-C740-4A60-9FB0-0353676EE2A6.html During your testing don’t forget to add the route and the gateway  commands;  “that’s not common knowledge” Hope this helps, Robert M. ... View more