[afnog] Problem bringing up MPLS on disimilar interfaces

[Frank A. Kuse]

Hi Mark,

Thanks very much for your support. MPLS is up and running very well now.
The reason of using IS-IS is for future expansion of our network.
The points you have raised has really help in getting my problems fixed.
All support is duly recognized and appreciated.

Cheers,


-----Original Message-----
From: Mark Tinka [mailto:mtinka at globaltransit.net] 
Sent: Monday, September 22, 2008 4:07 PM
To: Frank A. Kuse
Cc: afnog at afnog.org
Subject: Re: [afnog] Problem bringing up MPLS on disimilar interfaces

On Monday 22 September 2008 22:11:15 Frank A. Kuse wrote:

> The show mpls ldp neighbor doesn't show anything.

So LDP isn't establishing. Confirm these 2 routers are directly connected,
i.e., same VLAN.

o Is there any particular reason you're not running IS-IS on
  your physical interfaces?

o Your IS-IS process configuration seems a little complex.
  What's your motive?

o An FE port on a 7200-VXR has a default MTU of 1,500 bytes.
  I see the interface MTU of your Gig-E port on the NPE-G1
  is 1,512 bytes. If you're unable to increase the FE card's
  MTU value, suggest you change the Gig-E port back to the
  default MTU (1,500 bytes), and increase the MPLS MTU value
  on the FE port to 1,526 bytes, or 1,530 bytes, whichever
  is supported. Cisco do not like to support the 'mpls mtu'
  command, but it generally works when you can't have Gig-E
  ports. Don't forget to flap the interface for the MTU
  value to take effect.

o Can you also make sure your routers use their individual
  Loopback addresses as the transport source for LDP:

	mpls ldp router-id Loopback0

Cheers,

Mark.