Background:
I've been tasked to setup a VLAN and routing at our DC. The VLAN ID is 25, which I've configured on an HP v1910 switch by way of a trunk port and tagged with VLAN 25.
I also have an ESXi host with a portgroup tagged with VLAN 25 connected to a port on the v1910 switch that's a hybrid port belonging to VLAN 5 untagged and VLAN 25 tagged.
The VLAN works as far as I can tell, since the IPs I've been instructed to use seemingly can ping to the remote device just fine. The IP I've been assigned:
10.10.25.10/30, or 10.10.25.10 mask 255.255.255.252 The remote IP used to test is 10.10.25.9/30, which I can ping (traceroute works as well, one hop to 10.10.25.9)
The issue now though is this:
The IP 10.10.25.10/30 has been assigned to a VM directly on my side, with the vNIC connecting to the port group belonging to VLAN 25. The device at the remote site though is 192.168.78.10, meaning that I need to route traffic to 192.168.78.10 via the NIC belonging to VLAN 25 and the next hop as 10.10.25.9 (instruction given from network admin at remote site, assuming 10.10.25.9 is a router or routing-capable device).
Here's what I've tried doing on the VM running a Windows OS (interface 25 is the NIC belonging to VLAN 25):
route add 192.168.78.10 mask 255.255.255.255 10.10.25.9 if 25
I cannot connect to 192.168.78.10 at this point though. What confuses me more is that doing a traceroute to 192.168.78.10 does not produce any visible hops, even though I can ping 10.10.25.9 fine, which should surely show up as a network hop?
My questions:
Is the problem on my side, or at the remote site? If it's on my end, am I missing something perhaps?