Well naming changes and NIC differences would be difficult to mange unless all the servers were all absolutely identical. The information should be in the registry but I tend to stay away from that whenever possible.
Note, no teaming of NICs with just about all block iSCSI SANs. They don't support it so it's a waste and will reduce performance. Just use MPIO for iSCSI.
Was thinking a tool like Netsh may be available. With multiple physical NICs in a server - and possibly teamed Ethernet NICs - including NICs utilized for iSCSI - I have experienced, can be very precise depending on what switch/vlan or SAN the cabling is plugged into - its requires knowledge/documentation of which NIC is hosting Ethernet or iSCSI or teaming, etc. I was hoping a tool could specifically export iSCSI and associated NIC settings.
Also, Windows patches a couple of times have wiped config on all physical NICs as well as VM NICS - it took some time to determine correct physical NIC and then re-team and configure NICs for iSCSI or Ethernet use.
dwilliam62
6 Operator
•
1516 Posts
•
6374 Points
1358
0
Posted March 4th, 2020 11:00
Hello,
Well naming changes and NIC differences would be difficult to mange unless all the servers were all absolutely identical. The information should be in the registry but I tend to stay away from that whenever possible.
Note, no teaming of NICs with just about all block iSCSI SANs. They don't support it so it's a waste and will reduce performance. Just use MPIO for iSCSI.
Good luck!
Regards,
Don