<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How to create routed GRE Tunnel from X450G2 to Cisco Router? in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36747#M7643</link>
    <description>Ok guys, I have a new site with two X450G2's running system version 22.5.1.7 and Advanced Edge License.  I currently have a high speed WAN from our local ISP which is a private link back to our HQ.  We obtained a cellular LTE device from another provider that assigned us a /30. &lt;BR /&gt;
&lt;BR /&gt;
For proof of concept I am doing my testing on a spare X450G2 running the same 22.5.1.7 code but just the regular edge licence.  I have the tunnel created and I can ping the endpoints which are the local and remote LTE router.  But the provider of these LTE routers require us to create a GRE tunnel over them.&lt;BR /&gt;
&lt;BR /&gt;
I created the tunnel on the HQ side which terminates into a Cisco 2901 router with this command:&lt;BR /&gt;
interface Tunnel5&lt;BR /&gt;
 description LTE TUNNEL TO R BRANCH&lt;BR /&gt;
 ip address 192.168.205.33 255.255.255.252&lt;BR /&gt;
 ip mtu 1400&lt;BR /&gt;
 ip tcp adjust-mss 1360&lt;BR /&gt;
 tunnel source 10.200.0.1&lt;BR /&gt;
 tunnel destination 10.200.0.22&lt;BR /&gt;
end&lt;BR /&gt;
&lt;BR /&gt;
The LTE router at this HQ site is 10.200.0.1, and the LTE router at the "R Branch" we will call it, is 10.200.0.22.  This Cisco Router can ping 10.200.0.22 without issue.  The Extreme test switch can ping 10.200.0.1 without issue, so I know there is LTE connectivity.&lt;BR /&gt;
&lt;BR /&gt;
Now for creating the GRE tunnels, this Cisco commands above work fine for our other branches that terminate into other Cisco 2901 routers.  However this new site does not have any Cisco routers since we are doing routing in the switch.&lt;BR /&gt;
&lt;BR /&gt;
Here is what I've attempted on the EXOS side for the tunnel:&lt;BR /&gt;
&lt;BR /&gt;
Tunnel is plugged into port 2&lt;BR /&gt;
sh port 2 vid&lt;BR /&gt;
         Untagged&lt;BR /&gt;
Port     /Tagged   VID(s)&lt;BR /&gt;
-------- --------  ------------------------------------------------------------&lt;BR /&gt;
2        Untagged  222&lt;BR /&gt;
&lt;BR /&gt;
sh vlan&lt;BR /&gt;
Untagged ports auto-move: Inform&lt;BR /&gt;
-----------------------------------------------------------------------------------------------&lt;BR /&gt;
Name            VID  Protocol Addr       Flags                         Proto  Ports  Virtual&lt;BR /&gt;
                                                                              Active router&lt;BR /&gt;
                                                                              /Total&lt;BR /&gt;
-----------------------------------------------------------------------------------------------&lt;BR /&gt;
Default         1    10.1.0.111     /16  -f----------T---------------  ANY    1 /26  VR-Default&lt;BR /&gt;
Mgmt            4095 ------------------------------------------------  ANY    0 /1   VR-Mgmt&lt;BR /&gt;
LTE             222  10.200.0.21    /30  -f--------------------------  ANY    1 /1   VR-Default&lt;BR /&gt;
&lt;BR /&gt;
Other vlans excluded from this output...&lt;BR /&gt;
&lt;BR /&gt;
create tunnel backuptunnel gre destination 10.200.0.22 source 10.200.0.21&lt;BR /&gt;
configure tunnel backuptunnel ipaddress 192.168.205.34 255.255.255.252&lt;BR /&gt;
enable ipforwarding tunnel backuptunnel&lt;BR /&gt;
enable ipforwarding vlan LTE&lt;BR /&gt;
&lt;BR /&gt;
sh iproute&lt;BR /&gt;
Ori  Destination        Gateway         Mtr  Flags         VLAN       Duration&lt;BR /&gt;
#s   Default Route      10.1.0.254      1    UG---S-um--f- Default    100d:22h:32m:2s&lt;BR /&gt;
#d   10.1.0.0/16        10.1.0.111      1    U------um--f- Default    100d:22h:32m:4s&lt;BR /&gt;
#s   10.200.0.0/24      10.200.0.22     1    UG---S-um--f- LTE   0d:0h:19m:28s&lt;BR /&gt;
#d   10.200.0.20/30     10.200.0.21     1    U------um--f- LTE   0d:1h:2m:17s&lt;BR /&gt;
#s   192.168.205.0/24   192.168.205.33  1    UG---S-um--f- backuptunnel 0d:0h:25m:23s&lt;BR /&gt;
#d   192.168.205.32/30  192.168.205.34  1    U------um--f- backuptunnel 0d:0h:40m:38s&lt;BR /&gt;
&lt;BR /&gt;
I am expecting that this EXOS switch, 192.168.205.34 should be able to ping the Cisco side of the tunnel at 192.168.205.33, and the Cisco side should be able to ping the EXOS side as well.  However the ping is failing. &lt;BR /&gt;
&lt;BR /&gt;
Obviously the endpoints will be 192.168.205.33 at the branch and 192.168.205.34 at the HQ and we will push traffic over this if the primary WAN goes down (likely using OSPF).&lt;BR /&gt;
&lt;BR /&gt;
Am I missing something, or did I configure something wrong?&lt;BR /&gt;
&lt;BR /&gt;
Again this is just a test switch so we can do antying on it and not disrupt connectivity.  But once I get it working I want to translate this config to the actual branch and drive the LTE device over there and plug it into port 2:49 (with gigabit SFP port).  Port 1:49 is the current WAN handoff in its own transport vlan.  The site has no connectivity issues today, but we want to throw in this LTE backup device just in case there is a fiber cut or other issue with our upstream provider.  We have this configuration today with other sites, but all of those existing sites use either a Cisco 2901 or 2911 router.  We are trying to eliminate that extra piece of equipment if at all possible.&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Fri, 12 Oct 2018 22:32:00 GMT</pubDate>
    <dc:creator>kjstech</dc:creator>
    <dc:date>2018-10-12T22:32:00Z</dc:date>
    <item>
      <title>How to create routed GRE Tunnel from X450G2 to Cisco Router?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36747#M7643</link>
      <description>Ok guys, I have a new site with two X450G2's running system version 22.5.1.7 and Advanced Edge License.  I currently have a high speed WAN from our local ISP which is a private link back to our HQ.  We obtained a cellular LTE device from another provider that assigned us a /30. &lt;BR /&gt;
&lt;BR /&gt;
For proof of concept I am doing my testing on a spare X450G2 running the same 22.5.1.7 code but just the regular edge licence.  I have the tunnel created and I can ping the endpoints which are the local and remote LTE router.  But the provider of these LTE routers require us to create a GRE tunnel over them.&lt;BR /&gt;
&lt;BR /&gt;
I created the tunnel on the HQ side which terminates into a Cisco 2901 router with this command:&lt;BR /&gt;
interface Tunnel5&lt;BR /&gt;
 description LTE TUNNEL TO R BRANCH&lt;BR /&gt;
 ip address 192.168.205.33 255.255.255.252&lt;BR /&gt;
 ip mtu 1400&lt;BR /&gt;
 ip tcp adjust-mss 1360&lt;BR /&gt;
 tunnel source 10.200.0.1&lt;BR /&gt;
 tunnel destination 10.200.0.22&lt;BR /&gt;
end&lt;BR /&gt;
&lt;BR /&gt;
The LTE router at this HQ site is 10.200.0.1, and the LTE router at the "R Branch" we will call it, is 10.200.0.22.  This Cisco Router can ping 10.200.0.22 without issue.  The Extreme test switch can ping 10.200.0.1 without issue, so I know there is LTE connectivity.&lt;BR /&gt;
&lt;BR /&gt;
Now for creating the GRE tunnels, this Cisco commands above work fine for our other branches that terminate into other Cisco 2901 routers.  However this new site does not have any Cisco routers since we are doing routing in the switch.&lt;BR /&gt;
&lt;BR /&gt;
Here is what I've attempted on the EXOS side for the tunnel:&lt;BR /&gt;
&lt;BR /&gt;
Tunnel is plugged into port 2&lt;BR /&gt;
sh port 2 vid&lt;BR /&gt;
         Untagged&lt;BR /&gt;
Port     /Tagged   VID(s)&lt;BR /&gt;
-------- --------  ------------------------------------------------------------&lt;BR /&gt;
2        Untagged  222&lt;BR /&gt;
&lt;BR /&gt;
sh vlan&lt;BR /&gt;
Untagged ports auto-move: Inform&lt;BR /&gt;
-----------------------------------------------------------------------------------------------&lt;BR /&gt;
Name            VID  Protocol Addr       Flags                         Proto  Ports  Virtual&lt;BR /&gt;
                                                                              Active router&lt;BR /&gt;
                                                                              /Total&lt;BR /&gt;
-----------------------------------------------------------------------------------------------&lt;BR /&gt;
Default         1    10.1.0.111     /16  -f----------T---------------  ANY    1 /26  VR-Default&lt;BR /&gt;
Mgmt            4095 ------------------------------------------------  ANY    0 /1   VR-Mgmt&lt;BR /&gt;
LTE             222  10.200.0.21    /30  -f--------------------------  ANY    1 /1   VR-Default&lt;BR /&gt;
&lt;BR /&gt;
Other vlans excluded from this output...&lt;BR /&gt;
&lt;BR /&gt;
create tunnel backuptunnel gre destination 10.200.0.22 source 10.200.0.21&lt;BR /&gt;
configure tunnel backuptunnel ipaddress 192.168.205.34 255.255.255.252&lt;BR /&gt;
enable ipforwarding tunnel backuptunnel&lt;BR /&gt;
enable ipforwarding vlan LTE&lt;BR /&gt;
&lt;BR /&gt;
sh iproute&lt;BR /&gt;
Ori  Destination        Gateway         Mtr  Flags         VLAN       Duration&lt;BR /&gt;
#s   Default Route      10.1.0.254      1    UG---S-um--f- Default    100d:22h:32m:2s&lt;BR /&gt;
#d   10.1.0.0/16        10.1.0.111      1    U------um--f- Default    100d:22h:32m:4s&lt;BR /&gt;
#s   10.200.0.0/24      10.200.0.22     1    UG---S-um--f- LTE   0d:0h:19m:28s&lt;BR /&gt;
#d   10.200.0.20/30     10.200.0.21     1    U------um--f- LTE   0d:1h:2m:17s&lt;BR /&gt;
#s   192.168.205.0/24   192.168.205.33  1    UG---S-um--f- backuptunnel 0d:0h:25m:23s&lt;BR /&gt;
#d   192.168.205.32/30  192.168.205.34  1    U------um--f- backuptunnel 0d:0h:40m:38s&lt;BR /&gt;
&lt;BR /&gt;
I am expecting that this EXOS switch, 192.168.205.34 should be able to ping the Cisco side of the tunnel at 192.168.205.33, and the Cisco side should be able to ping the EXOS side as well.  However the ping is failing. &lt;BR /&gt;
&lt;BR /&gt;
Obviously the endpoints will be 192.168.205.33 at the branch and 192.168.205.34 at the HQ and we will push traffic over this if the primary WAN goes down (likely using OSPF).&lt;BR /&gt;
&lt;BR /&gt;
Am I missing something, or did I configure something wrong?&lt;BR /&gt;
&lt;BR /&gt;
Again this is just a test switch so we can do antying on it and not disrupt connectivity.  But once I get it working I want to translate this config to the actual branch and drive the LTE device over there and plug it into port 2:49 (with gigabit SFP port).  Port 1:49 is the current WAN handoff in its own transport vlan.  The site has no connectivity issues today, but we want to throw in this LTE backup device just in case there is a fiber cut or other issue with our upstream provider.  We have this configuration today with other sites, but all of those existing sites use either a Cisco 2901 or 2911 router.  We are trying to eliminate that extra piece of equipment if at all possible.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 12 Oct 2018 22:32:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36747#M7643</guid>
      <dc:creator>kjstech</dc:creator>
      <dc:date>2018-10-12T22:32:00Z</dc:date>
    </item>
    <item>
      <title>RE: How to create routed GRE Tunnel from X450G2 to Cisco Router?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36748#M7644</link>
      <description>Oh also second question, can I make a second tunnel off the same interface?  In a perfect world I'd love to create a gre tunnel to our LTE device at our DR site, however I get an error message"&lt;BR /&gt;
create tunnel drtunnel gre destination 10.200.0.22 source 10.200.0.21&lt;BR /&gt;
Error: Failed to create tunnel 'drtunnel'&lt;BR /&gt;
&lt;B&gt;&lt;BR /&gt;
&lt;/B&gt;&lt;BR /&gt;
The Cisco 2901 at HQ has 5 tunnels on it from the same source, so I'm not sure why that can handle it but EXOS is throwing an error.</description>
      <pubDate>Fri, 12 Oct 2018 22:47:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36748#M7644</guid>
      <dc:creator>kjstech</dc:creator>
      <dc:date>2018-10-12T22:47:00Z</dc:date>
    </item>
    <item>
      <title>RE: How to create routed GRE Tunnel from X450G2 to Cisco Router?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36749#M7645</link>
      <description>Nevermind.  The problem was on the Cisco side.  The Tunnel destination is supposed to be 10.200.0.21 NOT 10.200.0.22!  DOH!&lt;BR /&gt;
&lt;BR /&gt;
And I was able to create a second tunnel as well.  Also the destination is the IP on the cisco routers at the other end.  Not the device the vendor shipped us! I should of known. The GRE tunnel is established between the switch and the router.  So the tunnel spans the endpoints... the little LTE devices the vendor shipped us are like a layer 2 bridge.</description>
      <pubDate>Sat, 13 Oct 2018 03:12:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36749#M7645</guid>
      <dc:creator>kjstech</dc:creator>
      <dc:date>2018-10-13T03:12:00Z</dc:date>
    </item>
    <item>
      <title>RE: How to create routed GRE Tunnel from X450G2 to Cisco Router?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36750#M7646</link>
      <description>Nevermind.  The problem was on the Cisco side.  The Tunnel destination is supposed to be 10.200.0.21 NOT 10.200.0.22!  DOH!&lt;BR /&gt;
&lt;BR /&gt;
And I was able to create a second tunnel as well.  Also the destination is the IP on the cisco routers at the other end.  Not the device the vendor shipped us! I should of known. The GRE tunnel is established between the switch and the router.  So the tunnel spans the endpoints... the little LTE devices the vendor shipped us are like a layer 2 bridge.&lt;BR /&gt;
&lt;BR /&gt;
So to summarize the two tunnels on EXOS &lt;BR /&gt;
&lt;BR /&gt;
create tunnel backuptunnel gre destination 10.200.0.1 source 10.200.0.21&lt;BR /&gt;
configure tunnel backuptunnel ipaddress 192.168.205.34 255.255.255.252&lt;BR /&gt;
&lt;BR /&gt;
create tunnel drtunnel gre destination 10.200.0.5 source 10.200.0.21&lt;BR /&gt;
configure tunnel drtunnel ipaddress 192.168.205.38 255.255.255.252&lt;BR /&gt;
&lt;BR /&gt;
Where 10.200.0.1 is the IP address on the Cisco Router ethernet interface that the LTE device (10.200.0.2) plugs into at HQ.&lt;BR /&gt;
And 10.200.0.5 is the IP address on the Cisco Router ethernet interface that the DR site LTE device (10.200.0.6) plugs into.&lt;BR /&gt;
&lt;BR /&gt;
The source is the switch vlan LTE, 10.200.0.21, which is placed untagged in one port, and that has a cable going to the vendors newly supplied LTE device that they assigned 10.200.0.22/30.&lt;BR /&gt;
&lt;BR /&gt;
Cisco side HQ site&lt;BR /&gt;
interface Tunnel5&lt;BR /&gt;
 description LTE TUNNEL TO R BRANCH&lt;BR /&gt;
 ip address 192.168.205.33 255.255.255.252&lt;BR /&gt;
 ip mtu 1400&lt;BR /&gt;
 ip tcp adjust-mss 1360&lt;BR /&gt;
 tunnel source 10.200.0.1&lt;BR /&gt;
 tunnel destination 10.200.0.21&lt;BR /&gt;
end&lt;BR /&gt;
&lt;BR /&gt;
Cisco side DR site&lt;BR /&gt;
interface Tunnel6&lt;BR /&gt;
 description LTE TUNNEL TO R BRANCH&lt;BR /&gt;
 ip address 192.168.205.37 255.255.255.252&lt;BR /&gt;
 ip mtu 1400&lt;BR /&gt;
 ip tcp adjust-mss 1360&lt;BR /&gt;
 tunnel source 10.200.0.5&lt;BR /&gt;
 tunnel destination 10.200.0.21&lt;BR /&gt;
end&lt;BR /&gt;
&lt;BR /&gt;
Now we have IP connectivity between these endpoints, we can utilize them in our routing tables.  We will brainstorm a more advanced routing protocol like ospf rather than ping protection on exos (paired with IP SLA on Cisco side).&lt;BR /&gt;</description>
      <pubDate>Sat, 13 Oct 2018 03:17:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36750#M7646</guid>
      <dc:creator>kjstech</dc:creator>
      <dc:date>2018-10-13T03:17:00Z</dc:date>
    </item>
    <item>
      <title>RE: How to create routed GRE Tunnel from X450G2 to Cisco Router?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36751#M7647</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
you should probably test large packet sizes and path MTU discovery over the GRE tunnel. Last time I checked EXOS did not support setting the MTU of a GRE tunnel (see GTAC Knowledge article &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Q_A/Configure-MTU-size-for-GRE-tunnel-in-EXOS/" target="_blank" rel="nofollow noreferrer noopener"&gt;Configure MTU size for GRE tunnel in EXOS&lt;/A&gt;).&lt;BR /&gt;
&lt;BR /&gt;
It might be that too large packets are dropped when sent from the EXOS side. IP packets with DF bit set with size between 1401B and 1476B(*) should trigger an ICMP &lt;I&gt;packet too big&lt;/I&gt; from the Cisco router, but bigger packets might be silently dropped by EXOS without jumbo frames enabled, or forwarded by EXOS if jumbo frames are enabled, but silently dropped on the way to the Cisco router.&lt;BR /&gt;
&lt;BR /&gt;
It might be possible to work around that problem by reducing the MTU of all VLAN IP interfaces by the GRE encapsulation overhead of 24B(*) (see GTAC Knowledge article &lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-change-MTU-size-on-a-VLAN/" target="_blank" rel="nofollow noreferrer noopener"&gt;How to change MTU size on a VLAN?&lt;/A&gt;).&lt;BR /&gt;
&lt;BR /&gt;
(*) assuming 20B IP header and 4B GRE header&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Erik&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Oct 2018 19:28:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/36751#M7647</guid>
      <dc:creator>Erik_Auerswald</dc:creator>
      <dc:date>2018-10-15T19:28:00Z</dc:date>
    </item>
    <item>
      <title>Re: RE: How to create routed GRE Tunnel from X450G2 to Cisco Router?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/92871#M21496</link>
      <description>&lt;P&gt;&lt;a href="https://community.extremenetworks.com/t5/user/viewprofilepage/user-id/19389"&gt;@kjstech&lt;/a&gt;&amp;nbsp;- running into the same case as of today,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have an Extreme L3 switch&amp;nbsp; that need to establish a GRE tunnel with a Cisco router from the ISP side,&amp;nbsp;&lt;/P&gt;&lt;P&gt;but the additional thing here is an IPSEC VPn between an ASA and the same Cisco router to secure the GRE tunnel, the IP I've put is the only thing I have, any suggestion please for the Extreme switch configuration?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Airsail_0-1662117469240.png" style="width: 400px;"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/6117i67E4A3A94DD3A625/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Airsail_0-1662117469240.png" alt="Airsail_0-1662117469240.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Sep 2022 11:20:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/92871#M21496</guid>
      <dc:creator>Airsail</dc:creator>
      <dc:date>2022-09-02T11:20:05Z</dc:date>
    </item>
    <item>
      <title>Re: RE: How to create routed GRE Tunnel from X450G2 to Cisco Router?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/92872#M21497</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Below is a very basic example from EXOS:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.extremenetworks.com/exos_30.7/GUID-B9AF2A2D-37BB-4791-A378-6F8D00556052.shtml" target="_blank"&gt;ExtremeXOS® User Guide (extremenetworks.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It sounds like most of the magic in your situation is happening on the Cisco side of things so not sure what additional configuration you would need from EXOS regarding that topology.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chris Thompson&lt;/P&gt;</description>
      <pubDate>Fri, 02 Sep 2022 12:13:36 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/92872#M21497</guid>
      <dc:creator>CThompsonEXOS</dc:creator>
      <dc:date>2022-09-02T12:13:36Z</dc:date>
    </item>
    <item>
      <title>Re: RE: How to create routed GRE Tunnel from X450G2 to Cisco Router?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/92876#M21498</link>
      <description>&lt;P&gt;While we got point to point connectivity, we abandoned this a long time ago because at the time (not sure if this is still the case in newer firmwares) - we couldn’t include the GRE tunnel interface in OSPF calculation on the extreme side. &amp;nbsp;We always had to just OSPF to another device that DOES have that capeability, such as a Cisco Router, Server running pfsense with the frr plugin, or Ubiquiti EdgeRouter.&lt;/P&gt;&lt;P&gt;We ended up canceling our LTE backup (too slow and too much latency) and moved to cable modem. &amp;nbsp;Now we OSPF with a higher cost to a pfsense box which establishes IPSEC tunnel over a cable modem to another pfsense box at our HQ. &amp;nbsp;&lt;BR /&gt;The local carriers private fiber metro Ethernet is a lower cost route but if it’s cut, OSPF re-converges over to pfsense, out a IPsec tunnel to HQ, then OSPF back into an extreme core.&lt;/P&gt;&lt;P&gt;Overall this back up solution works much faster and the bandwidth&amp;nbsp;with this far greater than a previous LTE solution we were using. &amp;nbsp;Plus it’s cheaper and pfsense is free. &amp;nbsp;We already have a local file and print server at each location so it just spinning up another VM with pfsense on it and using additional Ethernet ports on the 1U server.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Sep 2022 13:01:47 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-create-routed-gre-tunnel-from-x450g2-to-cisco-router/m-p/92876#M21498</guid>
      <dc:creator>Keith9</dc:creator>
      <dc:date>2022-09-02T13:01:47Z</dc:date>
    </item>
  </channel>
</rss>

