Re: [mpls-linux-devel] LDPD configuration

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

First, my testing/bug fixing has only been for LDP operating in:
- Downstream Unsolicited
- Order control mode
- Liberal label retention

The above configuration is the default config, therefor there is
no need to issue any command under 'mpls ldp' or 'mpls ip'.  If you do
decide to test out the various configuration options below 'mpls ldp' and
'mpls ip' please send me bug reports ... or success reports :-)

As far as why your sessions will not establish.  To start off, you should
be using vtysh instead of connecting to each daemon independently.  Once
inside vtysh, you can configure all of the protocols.  Here is what I do:

monkey2# conf t
monkey2(config)# mpls ldp
monkey2(config-ldp)# exit
monkey2(config)# int eth1
monkey2(config-if)# mpls labelspace 0
Labelspace: 0
monkey2(config-if)# mpls ip
monkey2(config-if-ldp)# end
monkey2# sho ldp discovery

Local LSR Identifier: 192.168.3.2

Interface Discovery Sources:
        eth1: xmit/recv
            LDP Id: 192.168.3.1:0

Targeted Discovery Sources:
        No configured peers

monkey2# show ldp neighbor
Peer LDP Ident: 192.168.3.1:0; Local LDP Ident: 192.168.3.2:0
        TCP connection: 0.0.0.0.646 - 9.67.0.24.0
        State: OPERATIONAL; Msgs sent/recv: 13/34; UNSOLICITED
        Up time: 00:00:56
        LDP discovery sources:
          eth1
        Addresses bound to peer:
          192.168.2.1   192.168.3.1     192.168.1.183   192.168.5.1

monkey2#

In the above output the information about the TCP connection is invalid.
I need to fix this.  When using the standard config, the TCP connection
will be setup using the IP addresses of the directly connected interfaces.

Good luck!

On Tue, Nov 21, 2006 at 05:19:34PM +0100, Sienes Rodr?guez Gonzalo wrote:
> Hi!
>=20
> After testing static configurations of LSPs and tunnels, now I'm trying to
> automate the process. I've compiled and succesfully installed quagga-mpls
> and ldp-portable from your p4 repository including the links created with
> "create-links" file within the ldpd directory. Now, I'm able to run ospf =
but
> I have some problems with ldp.
>=20
> This is the scenario I use to test it:
>=20
> 13.0.0.0/24   .1   .1          .2   .1          .2   .1   14.0.0.0/24
>          -------PE1--------------PE2--------------PE3-------
>             eth2   eth0      eth1   eth0      eth1   eth2
>                     10.0.0.0/24      11.0.0.0/24
>=20
> And the .conf files in PE2:
>=20
> ZEBRA.CONF
> ------------------------------------------------------------------
> !
> ! Zebra configuration saved from vty
> !   2006/11/17 10:18:06
> !
> hostname PE2
> password root
> !
> log file /var/log/quagga/zebra.log
> !
> interface eth0
> !
> interface eth1
> !
> interface lo
> !
> line vty
> !
>=20
> OSPFD.CONF
> ------------------------------------------------------------------
> !
> ! Zebra configuration saved from vty
> !   2006/11/09 17:15:53
> !
> hostname l12p07
> password root
> !
> log file /var/log/quagga/ospfd.log
> !
> interface eth0
>  description 11.0.0.1 netmask 255.255.255.0 broadcast 11.0.0.255=20
> !=20
> interface eth1 =20
>  description 10.0.0.2 netmask 255.255.255.0 broadcast 10.0.0.255=20
> !
> interface lo=20
> !=20
> !=20
> router ospf =20
>  ospf router-id 0.0.0.2
>  network 10.0.0.0/24 area 0 =20
>  network 11.0.0.0/24 area 0=20
> !=20
> !
> line vty=20
> !
>=20
> LDPD.CONF
> ------------------------------------------------------------------
> !
> ! Zebra configuration saved from vty
> !   2006/11/17 18:25:07
> !
> hostname ldpd
> password root
> !
> log file /var/log/quagga/ldpd.log
> !
> !mpls ldp
> ! address-mode lsr-id
> ! lsp-control-mode ordered
> ! lsr-id 2.0.0.0
> !
> interface eth0
>  mpls ip
> !  distribution-mode du
> !
> interface eth1
>  mpls ip
> !  distribution-mode du
> !
> interface lo
> !
> line vty
> !
>=20
> Within "ldpd.conf" I have to comment(!) many lines and execute them via
> command line, otherwise the daemon would not start. Also, I did realize t=
hat
> after doing this, they don't appear on the "running config" of ldpd. The
> only command that show up is "mpls ldp".
>=20
> I'd like to configure a LSP from PE1 to PE3, so on PE3 I also put the
> command "egress connected".
>=20
> I capture ldp HELLOs discovering the neighbors and KEEPALIVEs. The HELLO
> packets carry the LSR-Id set on the command line but the KEEPALIVEs from =
PE2
> to PE1 and PE3, always contained a bad TCP CheckSum. Furthermore I don't =
see
> any message regarding sesion activation.
>=20
> Any information about these problems could be very useful.
>=20
> Thanks in advance,
>=20
> regards
>=20
> Gonzalo.

> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> mpls-linux-devel mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-devel

--=20
James R. Leu
jl...@mi...