cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1234
Views
0
Helpful
4
Replies

ISR G2 Routers - Tunnel Interface

johng231
Level 3
Level 3

Does anyone know why there are 3 tunnel interfaces enabled by default? They don't show up on the running config, only shows up when you issue a show ip int brief. I can't seem to remove it at all. It looks like it's not being advertised out anywhere but I still would like to know how to remove it as our global policy uses tunnel0-2 for GRE backup tunnels.

Tunnel0                    172.16.0.1      YES unset  up                    up     
Tunnel1                    172.16.0.1      YES unset  up                    up     
Tunnel2                    172.16.0.1      YES unset  up                    up  

Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.0(1)M1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 02-Dec-09 15:23 by prod_rel_team

ROM: System Bootstrap, Version 15.0(1r)M1, RELEASE SOFTWARE (fc1)

dlt01r uptime is 1 day, 23 hours, 7 minutes
System returned to ROM by power-on
System image file is "flash0:c2900-universalk9-mz.SPA.150-1.M1.bin"


This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

Cisco CISCO2901/K9 (revision 1.0) with 2576383K/45056K bytes of memory.
Processor board ID FTX140880QM
4 FastEthernet interfaces
2 Gigabit Ethernet interfaces
2 Serial(sync/async) interfaces
1 Channelized E1/PRI port
DRAM configuration is 64 bits wide with parity enabled.
255K bytes of non-volatile configuration memory.
4099032K bytes of ATA System CompactFlash 0 (Read/Write)


License Info:

License UDI:

-------------------------------------------------
Device#   PID                   SN
-------------------------------------------------
*0        CISCO2901/K9          FTX140880QM   

Technology Package License Information for Module:'c2900'

----------------------------------------------------------------
Technology    Technology-package          Technology-package
              Current       Type          Next reboot 
-----------------------------------------------------------------
ipbase        ipbasek9      Permanent     ipbasek9
security      None          None          None
uc            uck9          Permanent     uck9
data          None          None          None

Configuration register is 0x2102

4 Replies 4

paolo bevilacqua
Hall of Fame
Hall of Fame

Perhaps these are leftovers of previous configurations, due to a cosmetic bug.

Did you ever get this problem fixed.

I have exactly the same problem

Plays havoc with our monitoring tool  as these interfaces are always showing up as over 100% utilisation!

No. Cisco I think had said it was just part of the new version and there's nothing that can be done to remove them. We just ignored the interfaces and used the next sequence available.

rseiler
Level 3
Level 3

This is because you have an WCCP L3 GRE connected device. Recent IOS exposes the actual GRE tunnels that are used, previous releases hid them. This is useful for troubleshooting but a little disconcerning if you are not used to it. This stumped me for awhile, TAC had no idea.

You can get rid of them, however. The same IOS version you are running allows WCCP L2 redirection, which is *much* lower CPU overhead on both the WAE and the router. Just change the WAE configuration to use WCCP L2 for both ingress and egress and the tunnels will go away. Obviously, the WAE has to be L2 adjacent to an interface on the router.

Let me know if I'm on track here or if you are experiencing a completely different issue.

/Rick

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card