cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3131
Views
0
Helpful
3
Replies

CLNS/ISIS over GRE Tunnel issue

pexx
Level 1
Level 1

Hi!

I have problems bringing up CLNS over ISIS on a GRE Tunnel!

Router1 (R1) sees the CLNS Neighborship of Router2 (R2) but (R2) does not see (R1)!

I do successfully run about 20 GRE Tunnels on R1 to different Routers. This new one is the first I experience problems with!

 

First I tried different MTU values (clns mtu 1400, 1450, 1476) because of some Google-found discussions - didn´t work! I have no more idea what to try! Can someone please help!?

 

 

Here are some show commands:

R1#sh ver
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-JS-M), Version 12.2(19a), RELEASE SOFTWARE (fc2)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Mon 29-Sep-03 23:45 by pwade
Image text-base: 0x60008930, data-base: 0x61454000

ROM: System Bootstrap, Version 11.1(20)AA2, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

R1 uptime is 1 year, 46 weeks, 4 days, 12 hours, 55 minutes
System returned to ROM by power-on
System restarted at 23:47:53 zomemez Thu Nov 5 2015
System image file is "flash:c3640-js-mz.122-19a.bin"

cisco 3640 (R4700) processor (revision 0x00) with 98304K/32768K bytes of memory.
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
4 Ethernet/IEEE 802.3 interface(s)
2 FastEthernet/IEEE 802.3 interface(s)
DRAM configuration is 64 bits wide with parity disabled.
125K bytes of non-volatile configuration memory.
32768K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102


R1#sh run int tu 28
interface Tunnel28
 ip address 11.1.1.2 255.255.255.0
 clns mtu 1476
 clns router isis d0430201
 tunnel source Loopback0
 tunnel destination 10.87.126.26
end

R1#sh int tu 28
Tunnel28 is up, line protocol is up
  Hardware is Tunnel
  Internet address is 11.1.1.2/24
  MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
     reliability 255/255, txload 28/255, rxload 28/255
  Encapsulation TUNNEL, loopback not set
  Keepalive not set
  Tunnel source 10.249.252.136 (Loopback0), destination 10.87.126.26
  Tunnel protocol/transport GRE/IP, key disabled, sequencing disabled
  Checksumming of packets disabled,  fast tunneling enabled
  Last input 00:00:01, output 00:00:03, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/0 (size/max)
  5 minute input rate 1000 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     1817 packets input, 2238605 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     1818 packets output, 2319699 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
R1#sh clns int tu 28
Tunnel28 is up, line protocol is up
  Checksums enabled, MTU 1476, Encapsulation TUNNEL
  ERPDUs enabled, min. interval 10 msec.
  RDPDUs enabled, min. interval 100 msec., Addr Mask enabled
  Congestion Experienced bit set at 4 packets
  CLNS fast switching enabled
  CLNS SSE switching disabled
  DEC compatibility mode OFF for this interface
  Next ESH/ISH in 16 seconds
  Routing Protocol: IS-IS (d0430201)
    Circuit Type: level-1-2
    Interface number 0x4, local circuit ID 0x103
    Neighbor System-ID: 0020.6001.7701
    Level-1 Metric: 10, Priority: 64, Circuit ID: rr-wdm-aosi.03
    Number of active level-1 adjacencies: 0
    Next IS-IS Hello in 1 seconds

R1#show clns nei detail
Area d0430201:
System Id      Interface   SNPA                State  Holdtime  Type Protocol
0020.6001.7701 Tu28        10.87.126.26        Init   25        L1   IS-IS
  Area Address(es): 47.0005.8000.0043.0000.d043.0201
  Uptime: 00:07:58



Debug isis adjacencies on R1:

1y46w: ISIS-Adj (d0430201): Rec serial IIH from *Tunnel* (Tunnel28), cir type L1, cir id 00, length 1475
1y46w: ISIS-Adj (d0430201): rcvd state DOWN, old state INIT, new state INIT












R2#sh ver
Cisco IOS Software [Denali], Catalyst L3 Switch Software (CAT3K_CAA-UNIVERSALK9-M), Version 16.3.2, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Tue 08-Nov-16 17:31 by mcpre


Cisco IOS-XE software, Copyright (c) 2005-2016 by cisco Systems, Inc.
All rights reserved.  Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0.  The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY.  You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0.  For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.


ROM: IOS-XE ROMMON
BOOTLDR: CAT3K_CAA Boot Loader (CAT3K_CAA-HBOOT-M) Version 4.26, RELEASE SOFTWARE (P)

R2 uptime is 4 hours, 11 minutes
Uptime for this control processor is 4 hours, 14 minutes
System returned to ROM by reload at 09:19:23 MEST Wed Sep 27 2017
System restarted at 07:24:55 UTC Wed Sep 27 2017
System image file is "flash:/cat3k_caa-universalk9.16.03.02.SPA.bin"
Last reload reason: Reload Command



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.


Technology Package License Information:

-----------------------------------------------------------------
Technology-package                   Technology-package
Current             Type             Next reboot  
------------------------------------------------------------------
ipservicesk9        Permanent        ipservicesk9

cisco WS-C3650-24TS (MIPS) processor (revision M0) with 865815K/6147K bytes of memory.
3 Virtual Ethernet interfaces
28 Gigabit Ethernet interfaces
2048K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
250456K bytes of Crash Files at crashinfo:.
1609272K bytes of Flash at flash:.
0K bytes of  at webui:.

Motherboard Assembly Number        : 73-15898-05
Model Revision Number              : M0
Motherboard Revision Number        : B0
Model Number                       : WS-C3650-24TS
          

Switch Ports Model              SW Version        SW Image              Mode   
------ ----- -----              ----------        ----------            ----   
*    1 28    WS-C3650-24TS      16.3.2            CAT3K_CAA-UNIVERSALK9 BUNDLE



R2#sh run int tu 28
interface Tunnel28
 ip address 11.1.1.1 255.255.255.0
 tunnel source Loopback500
 tunnel destination 10.249.252.136
 clns mtu 1476
 clns router isis d043.0201




R2#sh clns int tu 28
Tunnel28 is up, line protocol is up
  Checksums enabled, MTU 1476, Encapsulation TUNNEL
  ERPDUs enabled, min. interval 10 msec.
  RDPDUs enabled, min. interval 100 msec., Addr Mask enabled
  Congestion Experienced bit set at 4 packets
  CLNS fast switching enabled
  CLNS SSE switching disabled
  DEC compatibility mode OFF for this interface
  Next ESH/ISH in 52 seconds
  Routing Protocol: IS-IS
    Circuit Type: level-1-2
    Interface number 0x1, local circuit ID 0x100
    Level-1 Metric: 10, Priority: 64, Circuit ID: sw-muenchen-po.00
    Level-1 IPv6 Metric: 10
    Number of active level-1 adjacencies: 0
    Next IS-IS Hello in 5 seconds
    if state DOWN
R2#sh int tu 28
Tunnel28 is up, line protocol is up
  Hardware is Tunnel
  Internet address is 11.1.1.1/24
  MTU 17868 bytes, BW 100 Kbit/sec, DLY 50000 usec,
     reliability 255/255, txload 2/255, rxload 1/255
  Encapsulation TUNNEL, loopback not set
  Keepalive not set
  Tunnel linestate evaluation up
  Tunnel source 10.87.126.26 (Loopback500), destination 10.249.252.136
   Tunnel Subblocks:
      src-track:
         Tunnel28 source tracking subblock associated with Loopback500
          Set of tunnels with source Loopback500, 1 member (includes iterators), on interface <OK>
  Tunnel protocol/transport GRE/IP
    Key disabled, sequencing disabled
    Checksumming of packets disabled
  Tunnel TTL 255, Fast tunneling enabled
  Tunnel transport MTU 1476 bytes
  Tunnel transmit bandwidth 8000 (kbps)
  Tunnel receive bandwidth 8000 (kbps)
  Last input never, output 00:00:07, output hang never
  Last clearing of "show interface" counters 03:46:57
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/0 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     1833 packets output, 2258281 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 unknown protocol drops
     0 output buffer failures, 0 output buffers swapped out

 

 

 

3 Replies 3

chrihussey
VIP Alumni
VIP Alumni

Looks like somehing is happening in the R1 to R2 direction. The R2 tunnel interface does not indicate any inbound packets, yet the R1 tunnel interface indicates both in and out packets. Can the tunnels ping each other? If they can't, take the ISIS out of the equation and figure that out first.

Are you tunneling across an MPLS or provider network, perhaps their routing is not 100% correct.

If you could supply the configs of the physical interfaces of the tunnels that might also help.

Regards

 

I figured that out - IP works over the Tunnel, address 10.1.1.1 can ping 10.1.1.2 and viceversa!

I recognized that the input packets don´t count up on R2 - mysterious thing is that they don´t even do after the successful IP pings over the Tunnel! Maybe because R2 is a Layer3 Switch (C3650) which does tunnels in software? I made similar experiences with wrong interface statistics on different models.

However, I have no idea why IP does run, but CLNS doesn´t? One more thing is that on R2, the CLNS Interface State of the Tunnel is "DOWN" as you can see in the show commands before!

Joseph W. Doherty
Hall of Fame
Hall of Fame
We had been using IS-IS for IPv6, and across GRE tunnels, we found setting MTU was needed. I recall (we've switched from IS-IS to OSPFv3, so I don't have anything current to look at) there was a CLNS MTU command we used, not an IP MTU command. If I recall that correctly, that might be what you're missing.