Would be done by design and work of a network specialist brought in for the company if their IT doesn't do this work.
Here we stick with Cisco products since that's what we have support for. If you can't find trained IT staff for your gear, call the maker and see if they have engineering support.
I am designing a manufacturing test solution to test 8 production units at a time.
I have a PC with 8 NICs ... each of these NICs need to communicate with a separate group of 3 devices (we'll say device A, device B and device C). A total of 32 ethernet port connections.
All 8 device A's have the same IP address. All 8 device B's have the same IP address. All 8 device C's have the same IP address.
Creating a separate VLAN for each of the 8 groups of A, B and C and the corresponding NIC using a layer 2 switch should alleviate the problem of the same IP addresses amongst devices. Correct?
Devices A and B behave as expected for any network connected device. The 8 device C's have a unique problem. In the typical installation of device C, it is only connected to another single device as a pair. It will accept incoming data from any IP address, however it always sends data out to a static, pre-determined IP address (this I cannot change).
So, I have the additional requirement that each of my 8 NICs need to receive data from their respective device C at the pre-determined address that device C always sends to. Is the best solution a layer 3 switch? Will this allow me to map this pre-determined IP to the particular NIC on each VLAN?
The first layer 3 device I have examined is the D-Link DGS-3620-52T; my rudimentary understanding of networking leads me to believe that this may fit my needs.
I do have at my disposal, a D-Link DGS-1210-52MP and a DES-3200-52P, both layer 2 switches. These seem capable of segregating each NIC and it's 3 devices to their own VLAN, but I am not sure that it is capable of handling the unique problem posed by device C.
Any input would be appreciated.