mpls-linux-general

[mpls-linux-general] what's the next step to dig in LDP code

[<m9...@cn...>]

Hi James,

Last time you told me to do "Start ldpd, telnet localhost 2610, =
configure, turn on LDP globally, turn on LDP on an interface, use the =
'?' key to figure out what commands are availble".

I have tried it , and I got the result below, there seems only few =
comands available.  What should I do on next step??

uml-1(config-ldp)#
  disable           Disable
  end               End current mode and change to enable mode.
  exit              Exit current mode and down to previous mode
  help              Description of the interactive help system
  list              Print command list
  lsp-control-mode  control mode
  lsr-id            LDP Label Switch Router Identifier
  no                Negate a command or set its defaults
  quit              Exit current mode and down to previous mode
  show              Show running system information
  trace             LDP debugging
  write             Write running configuration to memory, network, or
                    terminal


Best Regards

Timothy
2005.02.19


>On Wed, Feb 16, 2005 at 12:28:13AM +0800, ?????x wrote:
> Hi James,
>=20
> I remember last time you gived me the answer about LDP question which =
was showed below
>=20
> "Have your tried to run it yet?  Try that and start working on the =
first segfault you hit ...."
>=20
> Now, I want to know how to try it, if Quagga+LDP is not ready for =
users, how do I try it? Could you give me a hint?

Start ldpd, telnet localhost 2610, configure,
turn on LDP globally, turn on LDP on an interface, use the '?' key to =
figure
out what commands are availble.

> Thanks
>=20
> Timothy
> 2005.02.15
>=20
> The original mail was showed below
>=20
> On Tue, Feb 15, 2005 at 11:33:30PM +0800, ?????x wrote:
> > Hi James,
> >=20
> > I am trying to run LDP now. But I don't know where to start? And how =
to try it. Could you give me some examples or some scenarios?
> >=20
> > Thanks
> >=20
> > Timothy
> > 2005.02.15
> >=20
> > Check out the "Access to my development repository" on
> >  http://mpls-linux.sf.net/
> > =20
> >  On Wed, Feb 02, 2005 at 05:53:00PM +0800, ?????x wrote:
> >  > Hi James,
> >  >=20
> >  > According to your answer, could you explain more about "there are =
more significant bugs
> > to fix" that you mention before, I don"t understand clearly, could =
you give me some examples
> > or some hints.
> > =20
> >  Have your tried to run it yet?  Try that and start working on the
> >  first segfault you hit ....
> > =20
> >  > If I want to work on the code, where to grab the latest from your =
development tree (I am
> > not sure what you mean)?
> >  >=20
> >  > Thanks very much.
> >  >=20
> >  > Best Regards.
> >  >=20
> >  > Timothy
> >  > 2005.02.02
> >  >=20
> >  > > Why do you not listen to what I"ve said before? There are more =
significant
> >  > >bugs to fix then to try and port all of the "extra" commands to =
the new
> >  > >porting layer.  If you are determined to work on the code grab =
the latest
> >  > >from my development tree and get the basic commands working.
> >  >=20
> >  > >On Tue, Feb 01, 2005 at 05:19:01PM +0800, ?????x wrote:
> >  > > Hi James,
> >  > >=20
> >  > > When I canceled "#if 0" of some parts of "ldp_vtysh.c", for =
example:=20
> >  > >=20
> >  > > DEFUN(ldp_if_remote_tcp_port,
> >  > >       ldp_if_remote_tcp_port_cmd,
> >  > >       "remote-tcp-port <1-65535>",
> >  > >       "MPLS interface configuration\n"
> >  > >       "remote LDP port\n"
> >  > >       "port number\n")
> >  > > {
> >  > >   struct interface *ifp =3D vty->index;
> >  > >   struct ldp_interface *li =3D (struct =
ldp_interface*)ifp->info;
> >  > >   struct ldp *ldp =3D li->ldp;
> >  > >=20
> >  > >   li->entity.remote_tcp_port =3D atoi(argv[0]);
> >  > >   if (!ldp) {
> >  > >     li->create_on_hold =3D MPLS_BOOL_TRUE;
> >  > >     return CMD_SUCCESS;
> >  > >   }
> >  > >=20
> >  > >   ldp_cfg_entity_set(ldp->h, &li->entity, =
LDP_ENTITY_CFG_REMOTE_TCP);
> >  > >   return CMD_SUCCESS;
> >  > > }
> >  > >=20
> >  > > When I  compile it, there was an error:
> >  > > ldp_vty.c:1555: error: structure has no member named `ldp"
> >  > >=20
> >  > > Then I went to check "ldp_interface.h", I found that there =
actually has no this member
> > in "struct ldp_interface".
> >  > >=20
> >  > > Thanks.
> >  > >=20
> >  > > Timothy
> >  > > 2005.02.01
> >  > --=20
> >  > James R. Leu
> >  > jleu@mi...
> > =20
> >  --=20
> >  James R. Leu
> >  jleu@mi...
> > =20
>=20
> --=20
> James R. Leu
> jl...@mi...

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

Re: [mpls-linux-general] what's the next step to dig in LDP code

[James R. L. <jl...@mi...>]

First make sure you have OSPF up and running between the hosts across
the same interfaces as you will run LDP.

It's been a while since I have tried, but I believe all you need to=20
turn on is:

ldpd> conf t
ldpd(config)# mpls ldp
ldpd(config-ldp)# exit
ldpd(config)# int eth0
ldpd(config-if)# mpls ip
ldpd(config-ldp)# end
ldpd> show ldp
ldpd> show ldp neigh
ldpd> show ldp ?

If you do this on two hosts, they should form an adj, and then a session
then start exchanging labels.  If you get that far, then try to break thing=
s:
-disable/enable ldp globally
-disable/enable ldp on an interface
-remove/add ldp on an inteface
-remove/add lgp globablly

If you get this far then start playing with addresses:
-add/remove an IP address to a different interface (you should see the
 address be added and removed on the LDP peer

If you get this far then start playing with routes:
-add/remove static routes which get advertised into OSPF

Let me know where things break.  Make sure to keep track of what you
did to break things (consider using the unix utility 'script' to capture
everything you do).

Good luck

On Sat, Feb 19, 2005 at 10:45:45PM +0800, ?????x wrote:
> Hi James,
>=20
> Last time you told me to do "Start ldpd, telnet localhost 2610, configure=
, turn on LDP globally, turn on LDP on an interface, use the '?' key to fig=
ure out what commands are availble".
>=20
> I have tried it , and I got the result below, there seems only few comand=
s available.  What should I do on next step??
>=20
> uml-1(config-ldp)#
>   disable           Disable
>   end               End current mode and change to enable mode.
>   exit              Exit current mode and down to previous mode
>   help              Description of the interactive help system
>   list              Print command list
>   lsp-control-mode  control mode
>   lsr-id            LDP Label Switch Router Identifier
>   no                Negate a command or set its defaults
>   quit              Exit current mode and down to previous mode
>   show              Show running system information
>   trace             LDP debugging
>   write             Write running configuration to memory, network, or
>                     terminal
>=20
>=20
> Best Regards
>=20
> Timothy
> 2005.02.19
>=20
>=20
> >On Wed, Feb 16, 2005 at 12:28:13AM +0800, ?????x wrote:
> > Hi James,
> >=20
> > I remember last time you gived me the answer about LDP question which w=
as showed below
> >=20
> > "Have your tried to run it yet?  Try that and start working on the firs=
t segfault you hit ...."
> >=20
> > Now, I want to know how to try it, if Quagga+LDP is not ready for users=
, how do I try it? Could you give me a hint?
>=20
> Start ldpd, telnet localhost 2610, configure,
> turn on LDP globally, turn on LDP on an interface, use the '?' key to fig=
ure
> out what commands are availble.
>=20
> > Thanks
> >=20
> > Timothy
> > 2005.02.15
> >=20
> > The original mail was showed below
> >=20
> > On Tue, Feb 15, 2005 at 11:33:30PM +0800, ?????x wrote:
> > > Hi James,
> > >=20
> > > I am trying to run LDP now. But I don't know where to start? And how =
to try it. Could you give me some examples or some scenarios?
> > >=20
> > > Thanks
> > >=20
> > > Timothy
> > > 2005.02.15
> > >=20
> > > Check out the "Access to my development repository" on
> > >  http://mpls-linux.sf.net/
> > > =20
> > >  On Wed, Feb 02, 2005 at 05:53:00PM +0800, ?????x wrote:
> > >  > Hi James,
> > >  >=20
> > >  > According to your answer, could you explain more about "there are =
more significant bugs
> > > to fix" that you mention before, I don"t understand clearly, could yo=
u give me some examples
> > > or some hints.
> > > =20
> > >  Have your tried to run it yet?  Try that and start working on the
> > >  first segfault you hit ....
> > > =20
> > >  > If I want to work on the code, where to grab the latest from your =
development tree (I am
> > > not sure what you mean)?
> > >  >=20
> > >  > Thanks very much.
> > >  >=20
> > >  > Best Regards.
> > >  >=20
> > >  > Timothy
> > >  > 2005.02.02
> > >  >=20
> > >  > > Why do you not listen to what I"ve said before? There are more s=
ignificant
> > >  > >bugs to fix then to try and port all of the "extra" commands to t=
he new
> > >  > >porting layer.  If you are determined to work on the code grab th=
e latest
> > >  > >from my development tree and get the basic commands working.
> > >  >=20
> > >  > >On Tue, Feb 01, 2005 at 05:19:01PM +0800, ?????x wrote:
> > >  > > Hi James,
> > >  > >=20
> > >  > > When I canceled "#if 0" of some parts of "ldp_vtysh.c", for exam=
ple:=20
> > >  > >=20
> > >  > > DEFUN(ldp_if_remote_tcp_port,
> > >  > >       ldp_if_remote_tcp_port_cmd,
> > >  > >       "remote-tcp-port <1-65535>",
> > >  > >       "MPLS interface configuration\n"
> > >  > >       "remote LDP port\n"
> > >  > >       "port number\n")
> > >  > > {
> > >  > >   struct interface *ifp =3D vty->index;
> > >  > >   struct ldp_interface *li =3D (struct ldp_interface*)ifp->info;
> > >  > >   struct ldp *ldp =3D li->ldp;
> > >  > >=20
> > >  > >   li->entity.remote_tcp_port =3D atoi(argv[0]);
> > >  > >   if (!ldp) {
> > >  > >     li->create_on_hold =3D MPLS_BOOL_TRUE;
> > >  > >     return CMD_SUCCESS;
> > >  > >   }
> > >  > >=20
> > >  > >   ldp_cfg_entity_set(ldp->h, &li->entity, LDP_ENTITY_CFG_REMOTE_=
TCP);
> > >  > >   return CMD_SUCCESS;
> > >  > > }
> > >  > >=20
> > >  > > When I  compile it, there was an error:
> > >  > > ldp_vty.c:1555: error: structure has no member named `ldp"
> > >  > >=20
> > >  > > Then I went to check "ldp_interface.h", I found that there actua=
lly has no this member
> > > in "struct ldp_interface".
> > >  > >=20
> > >  > > Thanks.
> > >  > >=20
> > >  > > Timothy
> > >  > > 2005.02.01
> > >  > --=20
> > >  > James R. Leu
> > >  > jleu@mi...
> > > =20
> > >  --=20
> > >  James R. Leu
> > >  jleu@mi...
> > > =20
> >=20
> > --=20
> > James R. Leu
> > jl...@mi...
>=20
> --=20
> James R. Leu
> jl...@mi...

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