You could just use some sort of industrial Modbus/TCP gateway to poll all your devices and make the data available on your main network at an IP address of your choice. The addressing scheme of the original Modbus devices would then not matter as that network would be physically isolated from your main network. So long as these devices support multiple ...
don't use duplicate IP addresses ever unless you're asking for trouble
DHCP servers can be set up in redundant/failover mode, that is what you want
reserve IP addresses by MAC, so they don't change
use a layer-3 switch for routing in between subnets (low price, high performance)
depending on budget and requirements, consider a redundant switch layer in ...
How do I route the lacpdu packets through the unmanaged switch and make the etherchannel work?
Etherchannel, LACP or a static LAG trunk can't work across an unmanaged switch ever.
As both Rons have suggested you need either:
a managed switch with an Etherchannel or an LACP trunk to each of the other switches
a managed switch w/o LACP filtering (non-...
As Ron Trunk pointed out, LACP uses a special multicast OUI on its frames. Your unmanaged switch does not recognize the OUI, only that it is multicast, and it sends the multicast frames to every other switch interface. LACP frames are sent with the special 01:80:c2:00:00:02 multicast MAC address. The IEEE has reserved the 01:80:c2 OUI for link protocols, and ...
You probably can't with a single switch. LACP frames are multicast, so the unmanaged switch will flood them out all ports. This will cause several problems:
The sending switch will see its frame received on its other port. The switch will interpret this as a loop and refuse to aggregate the link.
The receiving switch will see the same packet on both ...
The answer really depends on the capabilities of your switches. If you have a single managed switch that can be configured with VLANs (almost every enterprise-grade switch ever made), then you can set up different VLANs, which logically divide the switch as if you had separate switches.
To get traffic from one VLAN to another VLAN requires a router, and you ...
SFTP is supported by Huawei on most of switches models. Share your complete model number.
PS: By default, the SFTP service is disabled. You need to enable it.
Here is completed configuration of SFTP, You can see my configuration for help
sysname SSH Server
local-user client001 password cipher %$%$c|-D8KO4/,B[(FR.r!LHg]TK%$%$
For the same fiber, one switch on one end was saying the link was up,
and the other switch on the other and was saying the same link was
That happens when Switch A (Rx) receives a signal from Switch B (Tx), but Switch B (Rx), for whatever reason (bad fiber, bad SFP, dirt/dust, etc.) does not receive a good signal from Switch A (Tx). Switch A ...
There's no general rule for that. Different vendors do things differently, even with different device series.
Most often, there are two indicators per port: one indicating link status (also lighting up briefly when an inserted module is activated) and the other indicating activity - either direction.
Note that both link status and activity are from the ...
At t =NL/R the I packet reaches the destination
At t =NL/R +L/R the II packet reaches the destination
At t = NL/R +L/R+L/R the III packet reaches the destination
At t = NL/R + (P-1)L/R the Pth packet reaches the destination.
So total delay = NL/R + ( P-1) L/R = (N+P-1)L/R
It was my mistake. I thought i had jumbo frames enabled on the second switch, but that was not the case. That's why i was able to ping the storage from the ESX, but unable to connect to the iSCSI volumes. i did not need to stack the switches. Just having a layer-2 domain (as @RonMaupin suggested on the comments section) with jumbo frames enabled worked.
To access the serial port, that model of switch needs specific hardware flow control on the serial port to work - either enable it in PuTTY/etc if your serial port hardware supports it or use two null-modem DB9 adaptors back to back.
It's easier to access it via telnet after resetting it to defaults.
Doing a "Battery Backed RAM test" from the boot menu or ...
Let us assume that I have a large corporate WLAN network with many access points having the same SSID. The WLAN access points are connected to each other by learning Ethernet switches.
My question is, how do the switches in the network learn that the client has moved to another access point if the client is only consuming downlink data?
There is no ...
In addition to the other two answers, which are correctly pointing out what your overall problem is with understanding of routing and re-addressing, I just want to briefly give you two easy options as a starting point if you really want to connect to the OPNSense system and do it all yourself:
You could set up an IP - Alias with a 192.168.x.N address on ...
For renumbering a network there are different strategies:
Run in parallel
(may be tricky with DNS / require an additional, temporary DNS server)
add new IP address as secondary to all servers and services (routers etc)
change all other nodes (clients) one by one
remove old IP address from servers and services, make secondary IP primary
Use router ...
You cannot do this the way you are trying to do it.
Your work PC will mask the destination address with its network mask and realize that the destination is on a different network, so it will frame the packet with its configured gateway (router) layer-2 address, and the frame will be sent to the gateway. The gateway doesn't have a route to the network, so ...