RE: ISIS over FR-FR L2VPN

When IS-IS first forms a neighbor relationship it PAD's the first packet
with the size of the full MTU. I don't see anything you have done to change
the MTU of the path but what happens when you add two MPLS headers one for
MPLS + one for L2VPN, is MTU still 1500? Try to think of the different
things you can do to affect MTU on the path, to either increase it or
decrease at the edge.

Regards,
 
Tyson Scott - CCIE #13513 R&S, Security, and SP
Managing Partner / Sr. Instructor - IPexpert, Inc.
Mailto: tscott_at_ipexpert.com

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
Andrew K Yule
Sent: Saturday, November 27, 2010 2:25 PM
To: ccielab_at_groupstudy.com
Subject: ISIS over FR-FR L2VPN

I have setup a FR to FR layer 2 VPN (l2tpv3).

CE1----fr---PE1--------PE2----fr----CE2

L2TP tunnel is showing up on both the PE routers. I am able to ping remote
interface from both the CE routers as well. MPLS Neighborship is also
getting established between CE1 and CE2. I have tired configuring OSPF and
OSPF neighborship comes up with out any issue.

But when I try to configure ISIS on CE1 and CE2 it's not working.
neighborship is not coming up at all. pls find below the config of both the
CE router. Am I missing something here for ISIS config ???? . There is not
mismatch of interface type. I can't make out with anything in debug as well

--------
CE1
---------
!
clns routing
!
interface Serial1/0
 ip address 10.1.1.1 255.255.255.0
 ip router isis
 encapsulation frame-relay
 mpls ip
 serial restart-delay 0
 no arp frame-relay
 frame-relay map clns 101 broadcast
 frame-relay map ip 10.1.1.2 101 broadcast
 no frame-relay inverse-arp
 clns router isis
 no clns route-cache
!
router isis
 net 49.0001.0000.0000.0001.00

--------
CE2
---------

clns routing
!
interface Serial1/0
 ip address 10.1.1.2 255.255.255.0
 ip router isis
 encapsulation frame-relay
 mpls ip
 serial restart-delay 0
 no arp frame-relay
 frame-relay map clns 201 broadcast
 frame-relay map ip 10.1.1.1 201 broadcast
 no frame-relay inverse-arp
 clns router isis
 no clns route-cache
!
router isis
 net 49.0001.0000.0000.0002.00

CE1#sh clns int s1/0
Serial1/0 is up, line protocol is up
  Checksums enabled, MTU 1500, Encapsulation FRAME-RELAY
  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 disabled
  CLNS SSE switching disabled
  DEC compatibility mode OFF for this interface
  Next ESH/ISH in 24 seconds
  Routing Protocol: IS-IS
    Circuit Type: level-1-2
    Interface number 0x0, local circuit ID 0x1
    Level-1 Metric: 10, Priority: 64, Circuit ID: CE1.01
    DR ID: 0000.0000.0000.00
    Level-1 IPv6 Metric: 10
    Number of active level-1 adjacencies: 0
    Level-2 Metric: 10, Priority: 64, Circuit ID: CE1.01
    DR ID: 0000.0000.0000.00
    Level-2 IPv6 Metric: 10
    Number of active level-2 adjacencies: 0
    Next IS-IS LAN Level-1 Hello in 7 seconds
    Next IS-IS LAN Level-2 Hello in 5 seconds

CE2#sh clns int s1/0
Serial1/0 is up, line protocol is up
  Checksums enabled, MTU 1500, Encapsulation FRAME-RELAY
  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 31 seconds
  Routing Protocol: IS-IS
    Circuit Type: level-1-2
    Interface number 0x0, local circuit ID 0x1
    Level-1 Metric: 10, Priority: 64, Circuit ID: CE2.01
    DR ID: 0000.0000.0000.00
    Level-1 IPv6 Metric: 10
    Number of active level-1 adjacencies: 0
    Level-2 Metric: 10, Priority: 64, Circuit ID: CE2.01
    DR ID: 0000.0000.0000.00
    Level-2 IPv6 Metric: 10
    Number of active level-2 adjacencies: 0
    Next IS-IS LAN Level-1 Hello in 2 seconds
    Next IS-IS LAN Level-2 Hello in 1 seconds

R4#sh debug
CLNS:
  IS-IS Adjacency related packets debugging is on

Debug msg
*Mar 1 01:07:37.327: ISIS-Adj: Sending L1 LAN IIH on Serial1/0, length 1500
*Mar 1 01:07:40.815: ISIS-Adj: Sending L2 LAN IIH on Serial1/0, length 1500
*Mar 1 01:07:47.243: ISIS-Adj: Sending L1 LAN IIH on Serial1/0, length 1500
*Mar 1 01:07:50.627: ISIS-Adj: Sending L2 LAN IIH on Serial1/0, length 1500
*Mar 1 01:07:56.075: ISIS-Adj: Sending L1 LAN IIH on Serial1/0, length 1500
*Mar 1 01:07:59.483: ISIS-Adj: Sending L2 LAN IIH on Serial1/0, length 1500
*Mar 1 01:08:04.163: ISIS-Adj: Sending L1 LAN IIH on Serial1/0, length 1500
*Mar 1 01:08:08.603: ISIS-Adj: Sending L2 LAN IIH on Serial1/0, length 1500
*Mar 1 01:08:13.211: ISIS-Adj: Sending L1 LAN IIH on Serial1/0, length 1500
*Mar 1 01:08:17.811: ISIS-Adj: Sending L2 LAN IIH on Serial1/0, length 1500
*Mar 1 01:08:22.663: ISIS-Adj: Sending L1 LAN IIH on Serial1/0, length 1500
*Mar 1 01:08:25.735: ISIS-Adj: Sending L2 LAN IIH on Serial1/0, length 1500
*Mar 1 01:08:32.363: ISIS-Adj: Sending L1 LAN IIH on Serial1/0, length 1500
*Mar 1 01:08:33.715: ISIS-Adj: Sending L2 LAN IIH on Serial1/0, length 1500
*Mar 1 01:06:03.955: ISIS-Adj: Sending L1 LAN IIH on Serial1/0, length 1500
*Mar 1 01:06:04.451: ISIS-Adj: Sending L2 LAN IIH on Serial1/0, length 1500

Blogs and organic groups at http://www.ccie.net
Received on Sat Nov 27 2010 - 14:33:11 ART