Thread: [mpls-linux-general] problems with static label configuration
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general
|
From: Maic G. <ma...@ha...> - 2007-05-04 14:52:03
|
Hallo,
I have some problems with quagga, ldp and mpls. I also have some problems w=
ith
the static label configuration.
I have a fedora core 5 (thanks to Marco Schmidt) and install all the rpm=EF=
s
from sf for the version 1.955.
So first the static label configuration problem:
I do:
Mpls labelspace show
I got:
LABELSPACE entry dev lo labelspace -1
LABELSPACE entry dev eth0 labelspace 20
LABELSPACE entry dev sit0 labelspace -1
I do:
Mpls nhlfe add key 0 instructions push gen 1100 nexthop eth0 ipv4 10.0.0.15
I got:
NHLFE entry key 0x4 mtu 0 propagate_ttl
(0 bytes, 0 pkts)
I got in dmsg:
unk.c:297:genl_mpls_nhlfe_new: enter
MPLS DEBUG net/mpls/mpls_nhlfe.c:394:mpls_add_out_label: enter
MPLS DEBUG net/mpls/mpls_nhlfe.c:130:nhlfe_dst_alloc: enter
MPLS DEBUG net/mpls/mpls_nhlfe.c:115:nhlfe_dst_gc: enter
MPLS DEBUG net/mpls/mpls_nhlfe.c:116:nhlfe_dst_gc: exit
MPLS DEBUG net/mpls/mpls_nhlfe.c:151:nhlfe_dst_alloc: exit
MPLS DEBUG net/mpls/mpls_netlink.c:274:mpls_nhlfe_event: enter
MPLS DEBUG net/mpls/mpls_netlink.c:234:mpls_fill_nhlfe: enter
MPLS DEBUG net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter
MPLS DEBUG net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit
MPLS DEBUG net/mpls/mpls_netlink.c:258:mpls_fill_nhlfe: exit
MPLS DEBUG net/mpls/mpls_netlink.c:288:mpls_nhlfe_event: exit
MPLS DEBUG net/mpls/mpls_nhlfe.c:451:mpls_add_out_label: exit
MPLS DEBUG net/mpls/mpls_opcode.c:345:mpls_build_opcode_push: enter
MPLS DEBUG net/mpls/mpls_opcode.c:356:mpls_build_opcode_push: exit
MPLS DEBUG net/mpls/mpls_opcode.c:1035:mpls_build_opcode_set: enter
MPLS DEBUG net/mpls/mpls_dst.c:169:mpls_dst_alloc: enter
MPLS DEBUG net/mpls/mpls_dst.c:216:mpls_dst_alloc: exit(00000000)
MPLS DEBUG net/mpls/mpls_opcode.c:1080:mpls_build_opcode_set: SET error
building DST info
MPLS DEBUG net/mpls/mpls_opcode.c:1082:mpls_build_opcode_set: exit
MPLS DEBUG net/mpls/mpls_instr.c:89:mpls_instrs_free: enter
MPLS DEBUG net/mpls/mpls_instr.c:65:mpls_instr_release: enter
MPLS DEBUG net/mpls/mpls_opcode.c:376:mpls_clean_opcode_push: enter
MPLS DEBUG net/mpls/mpls_opcode.c:378:mpls_clean_opcode_push: exit
MPLS DEBUG net/mpls/mpls_instr.c:73:mpls_instr_release: exit
MPLS DEBUG net/mpls/mpls_instr.c:65:mpls_instr_release: enter
MPLS DEBUG net/mpls/mpls_instr.c:73:mpls_instr_release: exit
MPLS DEBUG net/mpls/mpls_instr.c:95:mpls_instrs_free: exit
MPLS DEBUG net/mpls/mpls_netlink.c:334:genl_mpls_nhlfe_new: Exit: -1
I do:
Ip route add 192.168.30.0/24 via 10.0.0.15 mpls 4
I got no message -> every think is ok
I got in dmsg:
No message -> every think is ok
I do a:
ip route show
10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.1
192.168.30.0/24 via 10.0.0.15 dev eth0 mpls 0x4
169.254.0.0/16 dev eth0 scope link
-> every think is ok
I do:
ping -c 2 192.168.30.1
PING 192.168.30.1 (192.168.30.1) 56(84) bytes of data.
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
--- 192.168.30.1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 20014ms
I got a mistake
I got in dmsg:
ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev1: claim the port first
ppdev2: claim the port first
ppdev3: claim the port first
MPLS DEBUG net/mpls/mpls_shim.c:63:mpls_set_nexthop: enter
MPLS DEBUG net/mpls/mpls_shim.c:38:mpls_set_nexthop2: enter
MPLS DEBUG net/mpls/mpls_shim.c:43:mpls_set_nexthop2: nhlfe: c805ed80 mtu: =
0
dst: c805ed80
MPLS DEBUG net/mpls/mpls_shim.c:45:mpls_set_nexthop2: exit
MPLS DEBUG net/mpls/mpls_shim.c:74:mpls_set_nexthop: exit
MPLS DEBUG net/mpls/mpls_shim.c:63:mpls_set_nexthop: enter
MPLS DEBUG net/mpls/mpls_shim.c:38:mpls_set_nexthop2: enter
MPLS DEBUG net/mpls/mpls_shim.c:43:mpls_set_nexthop2: nhlfe: c805ed80 mtu: =
0
dst: c805ed80
MPLS DEBUG net/mpls/mpls_shim.c:45:mpls_set_nexthop2: exit
MPLS DEBUG net/mpls/mpls_shim.c:74:mpls_set_nexthop: exit
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
MPLS: unable to find a protocol driver(2048)
Where is the problem? Weeks ago I use an open suse and patch the mpls code
into the kernel and every think works fine. Now I take the kernel form the
linux-mpls project and it does not work.
Please help me.
--------------------------------------------
Maic Groffmann
email: ma...@ha...
|
|
From: James R. L. <jl...@mi...> - 2007-05-04 15:01:59
|
Did you load the mpls4 module? Do a lsmod and check for mpls4 in
the output.
If its not there do:
modprobe mpls4
and try your config again
On Fri, May 04, 2007 at 04:32:35PM +0200, Maic Groffmann wrote:
>=20
> Hallo,
>=20
> I have some problems with quagga, ldp and mpls. I also have some problems=
with
> the static label configuration.
> I have a fedora core 5 (thanks to Marco Schmidt) and install all the rpm?s
> from sf for the version 1.955.
>=20
> So first the static label configuration problem:
>=20
> I do:
> Mpls labelspace show
>=20
> I got:
> LABELSPACE entry dev lo labelspace -1
> LABELSPACE entry dev eth0 labelspace 20
> LABELSPACE entry dev sit0 labelspace -1
>=20
> I do:
> Mpls nhlfe add key 0 instructions push gen 1100 nexthop eth0 ipv4 10.0.0.=
15
>=20
> I got:
> NHLFE entry key 0x4 mtu 0 propagate_ttl
> (0 bytes, 0 pkts)
>=20
> I got in dmsg:
> unk.c:297:genl_mpls_nhlfe_new: enter
> MPLS DEBUG net/mpls/mpls_nhlfe.c:394:mpls_add_out_label: enter
> MPLS DEBUG net/mpls/mpls_nhlfe.c:130:nhlfe_dst_alloc: enter
> MPLS DEBUG net/mpls/mpls_nhlfe.c:115:nhlfe_dst_gc: enter
> MPLS DEBUG net/mpls/mpls_nhlfe.c:116:nhlfe_dst_gc: exit
> MPLS DEBUG net/mpls/mpls_nhlfe.c:151:nhlfe_dst_alloc: exit
> MPLS DEBUG net/mpls/mpls_netlink.c:274:mpls_nhlfe_event: enter
> MPLS DEBUG net/mpls/mpls_netlink.c:234:mpls_fill_nhlfe: enter
> MPLS DEBUG net/mpls/mpls_instr.c:188:mpls_instrs_unbuild: enter
> MPLS DEBUG net/mpls/mpls_instr.c:201:mpls_instrs_unbuild: exit
> MPLS DEBUG net/mpls/mpls_netlink.c:258:mpls_fill_nhlfe: exit
> MPLS DEBUG net/mpls/mpls_netlink.c:288:mpls_nhlfe_event: exit
> MPLS DEBUG net/mpls/mpls_nhlfe.c:451:mpls_add_out_label: exit
> MPLS DEBUG net/mpls/mpls_opcode.c:345:mpls_build_opcode_push: enter
> MPLS DEBUG net/mpls/mpls_opcode.c:356:mpls_build_opcode_push: exit
> MPLS DEBUG net/mpls/mpls_opcode.c:1035:mpls_build_opcode_set: enter
> MPLS DEBUG net/mpls/mpls_dst.c:169:mpls_dst_alloc: enter
> MPLS DEBUG net/mpls/mpls_dst.c:216:mpls_dst_alloc: exit(00000000)
> MPLS DEBUG net/mpls/mpls_opcode.c:1080:mpls_build_opcode_set: SET error
> building DST info
> MPLS DEBUG net/mpls/mpls_opcode.c:1082:mpls_build_opcode_set: exit
> MPLS DEBUG net/mpls/mpls_instr.c:89:mpls_instrs_free: enter
> MPLS DEBUG net/mpls/mpls_instr.c:65:mpls_instr_release: enter
> MPLS DEBUG net/mpls/mpls_opcode.c:376:mpls_clean_opcode_push: enter
> MPLS DEBUG net/mpls/mpls_opcode.c:378:mpls_clean_opcode_push: exit
> MPLS DEBUG net/mpls/mpls_instr.c:73:mpls_instr_release: exit
> MPLS DEBUG net/mpls/mpls_instr.c:65:mpls_instr_release: enter
> MPLS DEBUG net/mpls/mpls_instr.c:73:mpls_instr_release: exit
> MPLS DEBUG net/mpls/mpls_instr.c:95:mpls_instrs_free: exit
> MPLS DEBUG net/mpls/mpls_netlink.c:334:genl_mpls_nhlfe_new: Exit: -1
>=20
>=20
> I do:
> Ip route add 192.168.30.0/24 via 10.0.0.15 mpls 4
>=20
> I got no message -> every think is ok
>=20
> I got in dmsg:
> No message -> every think is ok
>=20
> I do a:
> ip route show
> 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.1
> 192.168.30.0/24 via 10.0.0.15 dev eth0 mpls 0x4
> 169.254.0.0/16 dev eth0 scope link
>=20
> -> every think is ok
>=20
>=20
> I do:
> ping -c 2 192.168.30.1
> PING 192.168.30.1 (192.168.30.1) 56(84) bytes of data.
> ping: sendmsg: No buffer space available
> ping: sendmsg: No buffer space available
>=20
> --- 192.168.30.1 ping statistics ---
> 2 packets transmitted, 0 received, 100% packet loss, time 20014ms
>=20
> I got a mistake
>=20
> I got in dmsg:
>=20
> ppdev0: registered pardevice
> ppdev0: unregistered pardevice
> ppdev1: claim the port first
> ppdev2: claim the port first
> ppdev3: claim the port first
> MPLS DEBUG net/mpls/mpls_shim.c:63:mpls_set_nexthop: enter
> MPLS DEBUG net/mpls/mpls_shim.c:38:mpls_set_nexthop2: enter
> MPLS DEBUG net/mpls/mpls_shim.c:43:mpls_set_nexthop2: nhlfe: c805ed80 mtu=
: 0
> dst: c805ed80
> MPLS DEBUG net/mpls/mpls_shim.c:45:mpls_set_nexthop2: exit
> MPLS DEBUG net/mpls/mpls_shim.c:74:mpls_set_nexthop: exit
> MPLS DEBUG net/mpls/mpls_shim.c:63:mpls_set_nexthop: enter
> MPLS DEBUG net/mpls/mpls_shim.c:38:mpls_set_nexthop2: enter
> MPLS DEBUG net/mpls/mpls_shim.c:43:mpls_set_nexthop2: nhlfe: c805ed80 mtu=
: 0
> dst: c805ed80
> MPLS DEBUG net/mpls/mpls_shim.c:45:mpls_set_nexthop2: exit
> MPLS DEBUG net/mpls/mpls_shim.c:74:mpls_set_nexthop: exit
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
> MPLS DEBUG net/mpls/mpls_output.c:293:mpls_output: enter
> MPLS DEBUG net/mpls/mpls_output.c:332:mpls_output: exit
> MPLS: unable to find a protocol driver(2048)
>=20
>=20
> Where is the problem? Weeks ago I use an open suse and patch the mpls code
> into the kernel and every think works fine. Now I take the kernel form the
> linux-mpls project and it does not work.
>=20
> Please help me.
>=20
> --------------------------------------------
> Maic Groffmann
>=20
> email: ma...@ha...
>=20
>=20
>=20
>=20
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
--=20
James R. Leu
jl...@mi...
|
|
From: Maic G. <ma...@ha...> - 2007-05-04 15:42:44
|
"Maic Groffmann" <ma...@ha...> schrieb: >Did you load the mpls4 module? Do a lsmod and check for mpls4 in the >output. > >If its not there do: > > modprobe mpls4 > >and try your config again Yes, thats is. Thank you very much. If I build my kernel I told the system, please no modules, build everything to the kernel. Did you build more modules in the mpls kernel environment? -------------------------------------------- Maic Groffmann email: ma...@ha... |
|
From: James R. L. <jl...@mi...> - 2007-05-06 02:44:17
|
On Fri, May 04, 2007 at 05:23:16PM +0200, Maic Groffmann wrote: > "Maic Groffmann" <ma...@ha...> schrieb: >=20 >=20 > >Did you load the mpls4 module? Do a lsmod and check for mpls4 in the > >output. > > > >If its not there do: > > > > modprobe mpls4 > > > >and try your config again >=20 > Yes, thats is. Thank you very much. > If I build my kernel I told the system, please no modules, build everythi= ng to > the kernel. >=20 > Did you build more modules in the mpls kernel environment? There are additional modules that could be loaded. Support for IPv6 and Ethernet over MPLS are handled by modules. In addition MPLS tunnel interfaces can be created after loading a module. >=20 >=20 > -------------------------------------------- > Maic Groffmann >=20 > email: ma...@ha... >=20 >=20 >=20 >=20 > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu jl...@mi... |
|
From: Maic G. <ma...@ha...> - 2007-08-07 13:50:22
|
Hallo, I use OSPF with LDP (quagga) and mpls-linux kernel ( all from sourceforge.net). Every think is working fine, but 1) If I try to redistribute some routes in OSPF the daemon crashes with an IO error. 2) If I try to use ISISd for IGP there is no label exchange between the router and the quagga mpls PC. LDP and ISIS adjacencies are established. Did I made a configuration mistake or is isisd without ldp / mpls support? 3) Is it possible to use RIP for IGP with ldp? Thank you for your answer. -------------------------------------------- Maic Groffmann email: ma...@ha... |
|
From: James R. L. <jl...@mi...> - 2007-08-07 14:01:10
|
You're in untested territory. Can you give details of your configuration so I can to duplicate the results here? On Tue, Aug 07, 2007 at 03:27:04PM +0200, Maic Groffmann wrote: > Hallo, >=20 > I use OSPF with LDP (quagga) and mpls-linux kernel ( all from > sourceforge.net). Every think is working fine, but >=20 > 1) If I try to redistribute some routes in OSPF the daemon crashes with a= n IO > error. >=20 > 2) If I try to use ISISd for IGP there is no label exchange between the r= outer > and the quagga mpls PC. LDP and ISIS adjacencies are established. Did I m= ade a > configuration mistake or is isisd without ldp / mpls support? >=20 > 3) Is it possible to use RIP for IGP with ldp?=20 >=20 > Thank you for your answer. >=20 >=20 >=20 > -------------------------------------------- > Maic Groffmann >=20 > email: ma...@ha... >=20 >=20 >=20 >=20 > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general --=20 James R. Leu jl...@mi... |
|
From: Maic G. <ma...@ha...> - 2007-08-09 17:28:48
Attachments:
OSPF-ISIS-eng.html
|
Hallo, I put some trace to this posting. I marked the interesting part of the trace. I have got an OSPF adjacency between the quagga PC and a router. I turn on trace all on the quagga PC in the ldp section. Than I enable ldp on the interface to the router. The ldp adjacency comes up and both systems exchange their local label binding. The result is, the router puts this labels as an remote binding in its forwarding table an the quagga PC does the same. If I use ISIS I do the same. The result was the router puts this labels as an remote binding in its forwarding table again. But the quagga PC did this not: 2007/08/09 18:10:10 LDP: ENTER: ldp_nexthop_for_fec_session 2007/08/09 18:10:10 LDP: EXIT: ldp_nexthop_for_fec_session: NULL 2007/08/09 18:10:10 LDP: OUT: Session 10.205.0.1:0 is not a valid nexthop for 0adb0001/32 Does anybody know why this happen? The first point in my question down is not so interesting any more. But the third one is interesting. Thanks. "James R. Leu" <jl...@mi...> schrieb: > You're in untested territory. Can you give details of your configuration > so I can to duplicate the results here? > > On Tue, Aug 07, 2007 at 03:27:04PM +0200, Maic Groffmann wrote: > > Hallo, > > > > I use OSPF with LDP (quagga) and mpls-linux kernel ( all from > > sourceforge.net). Every think is working fine, but > > > > 1) If I try to redistribute some routes in OSPF the daemon crashes with an > IO > > error. > > > > 2) If I try to use ISISd for IGP there is no label exchange between the > router > > and the quagga mpls PC. LDP and ISIS adjacencies are established. Did I made > a > > configuration mistake or is isisd without ldp / mpls support? > > > > 3) Is it possible to use RIP for IGP with ldp? > > > > Thank you for your answer. > > > > > > > > -------------------------------------------- > > Maic Groffmann > > > > email: ma...@ha... > > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > mpls-linux-general mailing list > > mpl...@li... > > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -------------------------------------------- Maic Groffmann email: ma...@ha... |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X