We have tow L3 switches connectot to each other by L3 link. Each L3 switch switch has different VLANs configured on them. We need to configure GRE tunnle between one VLAN from switch 1 to another VLAN from second switch. To do this I need to use loopback address as source and destination of the TUNNEL. How can it be configured so that the traffic only from those VLAN's will undergo the encapsulation. VLAN's IP from both the switches are reachable with routing protocol.
L3 switch 1 L3 switch 2
VLAN 10 L3 WAN-LINK VLAN 200
ip address 10.1.1.1 /24 ip address 10.1.200.1 /24
VLAN 11 VLAN 211
ip address 10.1.11.1 /24 ip address 10.1.211.1 /24
We are running routing protocol and are able to reach all the networks.
We need to configure the GRE tunnel between for VLAN 10 and VLAN 200 using loopback address.
Can we just take VLAN ip address as input IP address and destination IP address of the tunnel.
Sorry forgot to mention the reason why are we looking fro GRE Tunnel. The reason behinnd forming the GRE Tunnel is that some devices which we have at location one produce a multicast stream with TTL 1 and the users those who need this stream are located at second locaton. Due to this we these devices in the same IP subnet. With GRE can we do it?
>> The reason behinnd forming the GRE Tunnel is that some devices which we have at location one produce a multicast stream with TTL 1 and the users those who need this stream are located at second locaton. Due to this we these devices in the same IP subnet. With GRE can we do it?
As discussed in an older thread a GRE tunnel is not a solution for TTL=1 as the packet will expire before being put into the GRE tunnel
Also GRE tunnels on multilayer switches lower then C6500 are a very bad idea as they will cause traffic to be process switched stay away from it.
But Increasing TTL to a number greater then 1 in a multicast stream shouldn't be so difficult, so this is a case where the application has to be fixed and this can be done easily.
The only way to support this would be the use of a point to point transport service like EoMPLS or L2tPv3 that can be vlan based but this will not be scalable if in the future other remote sites need the stream.
what can be used depends on what platforms you have
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 custome...