#iSCSI Configurations
1 messages · Page 1 of 1 (latest)
It’s ok to do LACP on the Netapp side. Generally speaking most hosts do not like or support iscsi host side using LACP. (Like windows and esx). You are better off using separate interfaces on hosts and LACP on the Netapp.
Exception like rule: if you care to team your interfaces to a hypervisor, that is ok. The guest should have multiple interfaces (non teaming) for iscsi.
Another note, there was a bug as while ago under windows with an Intel driver whereas if you tried to use vlan tagging AND jumbo frames , iscsi would not function. It was like the last note in the 99 page readme file!
When possible using stand alone interfaces, make the native vlan the appropriate iscsi vlan.
Thanks @craggy breach , I have request do you have best practices guide
Not sure there is one. I just use my mind (coming up on 30 years of Netapp)
Lessons learned 😁
Oh 😄 it’s a great experience thank you for help
never had any problems using aggregated interfaces with iscsi on the netapp side... hosts were always vms
They are you using MPIO
it’s recommended to use 2 separate vlans (subnets) and interfaces for iscsi traffic for failover and MPIO benefits. feel free to use ifgrps if you want (and the hosts supports it). https://docs.netapp.com/us-en/ontap/san-config/iscsi-config-concept.html
any time there is more than one path, you should use multipathing software. That's a universal truth for all block devices.
depending on the host, you should also utilize the netapp host utilities as well as pay attention to the maximum number of paths that the OS supports/recommends