The cool kids all do vNIC these days. That's SRIOV adapters with VIOs managing an automatic failover.
more here: https://blog.vios4i.com/search/label/vNIC
------------------------------
Vincent Greene
IT Consultant
Technology Expert labs
IBM
Vincent.Greene@ibm.comThe postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
------------------------------
Original Message:
Sent: Wed August 23, 2023 09:19 AM
From: Steven Riedmueller
Subject: Binding to a particular IP address
Yup I think that's definitely the way to go these days. Our setup was done by a business partner when SRIOV was what all the "cool kids" were doing!
------------------------------
Steven Riedmueller
Certified IBM i Admin
Speaker, Mentor, and Advocate
------------------------------
Original Message:
Sent: Wed August 23, 2023 09:08 AM
From: Robert Berendt
Subject: Binding to a particular IP address
We have a very fault tolerant setup. Ethernet is served from multiple VIOS lpars using multiple FC adapters, etc. Still shows up as one line description to that lpar of IBM i. So it's not like binding to one particular IP address chokes down any of our fault tolerances. The other IP addresses are simply for stuff like
https://functiona.dekko.com
https://functionB.dekko.com
...
------------------------------
Robert Berendt IBMChampion
Original Message:
Sent: Wed August 23, 2023 08:51 AM
From: Steven Riedmueller
Subject: Binding to a particular IP address
I think you've got it with the BINDIFC parameter. We're using SRIOV so I have 2 "physical" interfaces with a bunch of virtual interfaces built on top of them. We use BINDIFC(*NONE) so the system will use either of the physical interfaces. If one goes down, it will use the other. In your case you're trying to do the opposite (force traffic to a particular destination to bind to a specific local interface).
------------------------------
Steven Riedmueller
Certified IBM i Admin
Speaker, Mentor, and Advocate