Maybe there is a easier way to do what I want (probably is)
We have a hardware device over there and its on the network but you cant management it from ip just some sort of software it came with. It will only find this device if its on the same land segment. At are office site we have 4 VLANS so it was easy I just setup 4 ports on a switch on different vlans and I just plug the cable into the right port when I need to make some changes.
If the connection between the remote site and the main site is a layer 2 connection, simply make it a trunk, and add all necessary vlans to the trunk. On a switch on the main site, put a port in the same vlan as the device in question, and you should be able to manage it fine.
I have a slightly different approach to suggest. Assuming that the link to the remote warehouse is a routed layer 3 link and that trunking VLANs would not work, I wonder if you could configure address translation for incoming traffic to this device so that it looks like the traffic to it is coming from a local address.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...