Re: [mpls-linux-general] (no subject)
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
Re: [mpls-linux-general] (no subject)
|
From: James R. L. <jl...@mi...> - 2003-06-19 14:23:56
|
I would create a 'dummy0' interface on each device (as I describe in my zebra sample on http://mpls-linux.sf.net/). Also you will never get traffic between just two boxes to be labeled (there is no reason, they would both be LERs). You need a 3rd device to make it interesting. Take a look at user-mode-linux (http://user-mode-linux.sf.net/) for a 'easy' way to simulate a multi node network on one device. On Thu, Jun 19, 2003 at 12:37:07PM +0200, a a wrote: > Hi! >=20 > I have checked the output from the commands you recommended me, and fou= nd=20 > some strange stuff... >=20 > #show ldp database > 192.168.0.0/24 local binding: label: gen 10000 > 192.168.0.0/24 remote binding: no outlabel lsr: 192.168.0.101:0 >=20 > I have the following hardware setup: >=20 > snowcrash-mpls pennywise-mpls > 192.168.0.101 192.168.0.100 > | | > | eth0 | eth0 > +-----------------------------------------------+ > 192.168.0.0/24 >=20 > How do I get the mplsd to assign an outgoing label to the other machine= ? > I have included my conf-files and all output from the show ... stuff. >=20 > Thanks in advance, > Andreas >=20 > >From: "James R. Leu" <jl...@mi...> > >Reply-To: jl...@mi... > >To: a a <dre...@ho...> > >CC: mpl...@li... > >Subject: Re: [mpls-linux-general] (no subject) > >Date: Tue, 17 Jun 2003 10:54:11 -0500 > > > >On Tue, Jun 17, 2003 at 01:44:24PM +0200, a a wrote: > > > Hi again! > > > > > > How do I use the labels given by the zebra-ldp? I have investigated= some > > > pkts with tethereal and found that the pkts are not mpls pkts... > > > Do I have to use mplsadm in order to use the lsp:s? > > > >Check the output from the 'ldp' related show commands. From the mplsd > >command line: > > > > show ldp discovery > > show ldp neighbor > > show ldp database > > > >Also look at the MPLS show commands: > > > > show mpls forwarding > > show mpls ftn > > > >Also, check the: > > > > show ip route > > > >output from the zebra command line. > > > >If everything is running correctly mplsd will create the MPLS forwardi= ng > >entites in the kernel for you and bind the LSPs to route entries. > > > > > > > > Sincerly, > > > Drew > > > > > > _________________________________________________________________ > > > Hitta r=E4tt p=E5 n=E4tet med MSN S=F6k http://search.msn.se/ > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: INetU > > > Attention Web Developers & Consultants: Become An INetU Hosting Par= tner. > > > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commis= sion! > > > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.= php > > > _______________________________________________ > > > mpls-linux-general mailing list > > > mpl...@li... > > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > >-- > >James R. Leu > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: INetU > >Attention Web Developers & Consultants: Become An INetU Hosting Partne= r. > >Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commissio= n! > >INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > >_______________________________________________ > >mpls-linux-general mailing list > >mpl...@li... > >https://lists.sourceforge.net/lists/listinfo/mpls-linux-general >=20 > _________________________________________________________________ > Hitta r=E4tt p=E5 n=E4tet med MSN S=F6k http://search.msn.se/ > ! > ! Zebra configuration saved from vty > ! 2002/03/23 17:07:30 > ! > hostname snowcrash-mplsd > password zebra > enable password zebra > ! > mpls ldp > ! > interface lo > ! > interface eth0 > mpls ldp > ! > interface dummy0 > ! > line vty > exec-timeout 0 0 > ! >=20 > ! -*- ospf -*- > ! > ! OSPFd sample configuration file > ! > ! > hostname snowcrash-ospfd > password zebra > enable password zebra > interface lo > interface eth0 > interface dummy0 > interface teql0 > router ospf > passive-interface lo > network 10.0.0.0/24 area 0 > network 192.168.0.0/24 area 0 > ! network 192.168.0.2/32 area 0 > line vty > exec-timeout 0 0 >=20 > log stdout >=20 > ! -*- zebra -*- > ! > ! zebra sample configuration file > ! > ! $Id: zebra.conf.sample,v 1.14 1999/02/19 17:26:38 developer Exp $ > ! > hostname snowcrash-zebra > password zebra > enable password zebra > ! > ! Interface's description. > ! > interface lo > description Loopback > ! > interface dummy0 > ip address 192.168.0.250/32 > ! > interface eth0 > ! > !interface sit0 > ! multicast >=20 > interface teql0 > ! > ! Static default route sample. > ! > !ip route 0.0.0.0/0 203.181.89.241 > ! >=20 > !log file zebra.log >=20 > snowcrash-mplsd> show ldp database > 192.168.0.0/24 remote binding: no outlabel lsr: 192.168.0.100:0 > 192.168.0.0/24 local binding: label: gen 10000 >=20 > snowcrash-mplsd> show ldp discovery >=20 > Local LSR Identifier: 192.168.0.101 >=20 > Interface Discovery Sources: > eth0: xmit >=20 > Targeted Discovery Sources: > No configured peers >=20 > snowcrash-mplsd> show ldp neighbor > Peer LDP Ident: 192.168.0.100:0; Local LDP Ident: 192.168.0.101:0 > TCP connection: 0.0.0.0.646 - 192.168.0.100.646 > State: OPERATIONAL; Msgs sent/recv: 25/73; UNSOLICITED > Up time: 00:05:22 > LDP discovery sources: > eth0 > Addresses bound to peer: > 192.168.0.100 >=20 >=20 > snowcrash-mplsd> show ldp session > 2 192.168.0.100 45 OPERATIONAL > 192.168.0.100 > snowcrash-mplsd> show mpls forw > snowcrash-mplsd> show mpls forwarding > Insegments: > Lbl Spc Label Owner > 0 10000 LDP > Total 1 >=20 > Outsegments: >=20 > Total 0 >=20 > Cross Connects: >=20 > Total 0 >=20 > snowcrash-mplsd> show mpls ftn > FTNs: >=20 > Total 0 >=20 > snowcrash-zebra# show ip route > C>* 127.0.0.0/8 is directly connected, lo > O 192.168.0.0/24 [110/10] is directly connected, eth0, 00:18:41 > C>* 192.168.0.0/24 is directly connect, eth0 >=20 --=20 James R. Leu |
