Re: [mpls-linux-general] MPLS on ATM
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
Re: [mpls-linux-general] MPLS on ATM
|
From: James R. L. <jl...@mi...> - 2001-04-05 00:48:47
|
Hello, Great output. It lets me know exactly what is happening. It looks like your creating a good outlabel. The inlabel looks like it is created as well. Packets are being sent from MPLS to the ATM layer on the ingress. But on the egress, nothing is ever making it to the MPLS layer. Can you get cell counters on your ATM switch? Check to see if it is seeing any cells coming from the ingress. Also can you check the ATM counters on the egress and see if any cells are making it that far. Can you try doing a back to back connection? (no switch) Jim On Wed, Apr 04, 2001 at 04:22:55PM +0100, cacote wrote: > HI, > > The message debug output of the two hosts ( NORTE e ESTE ) used in the > scenario described, is included in the two files that go in attach. > > The file nortemes is the the message of the Host Norte (machine that does > the pinging ) and the file estemes > is the message output of the Host Este ( machine that is pinged and that > crashes ). > > I dont know if it helps you in any way but, we have the two ATM cards in > the scenario connected by a switch in each we created the PVC we are using ( > 0/104 PVC). > > Thank you for your help , > best regards > > > HUGO CACOTE > > > > "James R. Leu" wrote: > > > BTW > > > > Do you have any output from the crashes? I'd like to find where it is > > crashing, and fix it :-) > > > > Make sure to send me the MPLS debug output. > > > > Jim > > > > On Tue, Apr 03, 2001 at 08:38:58PM +0100, cacote wrote: > > > HI > > > > > > I ve been testing the new MPLS package (mpls-linux-0.990), it worked > > > allright in ethernet but when I > > > got to teste it in ATM there were problems. > > > > > > My scenario is the following: > > > > > > > > > > > > ||||||||||||||||| > > > |||||||||||||||| > > > || norte > > > || > > > || este || > > > || > > > || > > > || || > > > > > > ||||||||||||||||| > > > |||||||||||||||| > > > | atm0 > > > 192.168.50.10 | atm0 > > > 192.168.50.20 > > > > > > | > > > | > > > |------------------------------------- | > > > > > > The ATM cards I am using are the following: > > > > > > ForeRunnerLe 155 mbit/s nicstar (chipset) > > > > > > The configuration i made on both hosts was this: > > > > > > > > > ON norte: > > > [root@norte /root]# route add -host 192.168.50.20/32 gw 192.168.50.20 > > > [root@norte /root]# mplsadm -A -O atm:0/104:atm0 > > > [root@norte /root]# mplsadm -B -O atm:0/104:atm0 -f 192.168.50.20/32 > > > [root@norte /root]# mplsadm -L atm0:0 > > > > > > If we try and check the configurations we see: > > > > > > [root@norte /root]# cat /proc/net/mpls_out > > > 80680008 PUSH(atm 0/104) SET(atm0) > > > [root@norte /root]# cat /proc/net/mpls_fec > > > 80680008 192.168.50.20/32 > > > > > > ON este: > > > [root@este /root]# route add -host 192.168.50.10/32 gw 192.168.50.10 > > > [root@este /root]# mplsadm -L atm0:0 > > > [root@este /root]# mplsadm -A -I atm:0/104:0 > > > > > > If we try and check the configurations we see: > > > > > > [root@este /root]# cat /proc/net/mpls_in > > > 80680000 atm 0/104 0 POP DLV > > > > > > If we then make [root@norte /root]# ping 192.168.50.20 , and if then > > > use ethereal to monitor the > > > packets in the two hosts we see no MPLS and just ICMP. I should add that > > > sometimes whem trying this > > > scenario the machine that is being pinged just crashes with no apparent > > > reason. > > > > > > Is there something wrong in the setup of the scenario? Is there anybody > > > that has a scenario where MPLS > > > works with ATM ? > > > > > > Thank you for the Help, best regards > > > > > > HUGO CACOTE > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > mpls-linux-general mailing list > > > mpl...@li... > > > http://lists.sourceforge.net/lists/listinfo/mpls-linux-general > > > > -- > > James R. Leu > Apr 4 15:14:18 este kernel: mpls_set_labelspace: enter > Apr 4 15:14:18 este kernel: mpls_set_labelspace: labelspace(0) > Apr 4 15:14:18 este kernel: mpls_set_labelspace: exit > Apr 4 15:16:26 este kernel: mpls_add_in_label: enter > Apr 4 15:16:26 este kernel: mpls_info_default_in_instruction: enter > Apr 4 15:16:26 este kernel: mpls_info_default_in_instruction: exit > Apr 4 15:16:26 este kernel: mpls_atm_create_vcc: enter(0,0,104,1) > Apr 4 15:16:26 este kernel: mpls_atm_create_vcc: vci 104 <-> 1024 vpi 0 <-> 4 > Apr 4 15:16:26 este kernel: mpls_atm_create_vcc: create_vcc > Apr 4 15:16:26 este kernel: mpls_atm_create_vcc: setting up vcc > Apr 4 15:16:26 este kernel: mpls_atm_create_vcc: exit > Apr 4 15:16:26 este kernel: mpls_add_in_label: succeeded creating vcc > Apr 4 15:16:26 este kernel: mpls_add_in_label: exit > Apr 4 15:21:23 norte kernel: mpls_set_labelspace: enter > Apr 4 15:21:23 norte kernel: mpls_set_labelspace: labelspace(0) > Apr 4 15:21:23 norte kernel: mpls_set_labelspace: exit > Apr 4 15:24:53 norte kernel: mpls_add_out_label: enter > Apr 4 15:24:53 norte kernel: mpls_make_dst: enter > Apr 4 15:24:53 norte kernel: mpls_make_dst: before bind neighbor > Apr 4 15:24:53 norte kernel: mpls_make_dst: bind neighbor succeeded > Apr 4 15:24:53 norte kernel: mpls_make_dst: exit(c3e2a380) > Apr 4 15:24:53 norte kernel: mpls_info_default_moi_instruction: enter > Apr 4 15:24:53 norte kernel: mpls_info_default_moi_instruction: exit > Apr 4 15:24:53 norte kernel: mpls_atm_create_vcc: enter(0,0,104,2) > Apr 4 15:24:53 norte kernel: mpls_atm_create_vcc: vci 104 <-> 1024 vpi 0 <-> 4 > Apr 4 15:24:53 norte kernel: mpls_atm_create_vcc: create_vcc > Apr 4 15:24:53 norte kernel: mpls_atm_create_vcc: setting up vcc > Apr 4 15:24:53 norte kernel: mpls_atm_create_vcc: exit > Apr 4 15:24:53 norte kernel: mpls_add_out_label: succeeded to create VCC > Apr 4 15:24:53 norte kernel: Label ATM 0/104 > Apr 4 15:24:53 norte kernel: Key ATM 0/104 8 > Apr 4 15:24:53 norte kernel: mpls_add_out_label: exit > Apr 4 15:24:53 norte kernel: mpls_prep_out2fec: enter > Apr 4 15:24:53 norte kernel: Label ATM 0/104 > Apr 4 15:24:53 norte kernel: Key ATM 0/104 8 > Apr 4 15:24:53 norte kernel: mpls_fill_key_res: enter > Apr 4 15:24:53 norte kernel: mpls_fill_key_res: exit > Apr 4 15:24:53 norte kernel: mpls_bind_out2fec: copied label to the FIB_NODE > Apr 4 15:24:53 norte kernel: mpls_bind_out2fec: Added FEC to list > Apr 4 15:24:53 norte kernel: mpls_bind_out2fec: exit > Apr 4 15:26:01 norte kernel: rt_set_nexthop: adding label to dst > Apr 4 15:26:01 norte kernel: rt_set_nexthop: before - mtu = 9180 > Apr 4 15:26:01 norte kernel: rt_set_nexthop: after - mtu = 9176 > Apr 4 15:26:01 norte kernel: rt_set_nexthop: adding label to dst > Apr 4 15:26:01 norte kernel: rt_set_nexthop: before - mtu = 9180 > Apr 4 15:26:01 norte kernel: rt_set_nexthop: after - mtu = 9176 > Apr 4 15:26:02 norte kernel: mpls_output: enter > Apr 4 15:26:02 norte kernel: mpls_output2: enter > Apr 4 15:26:02 norte kernel: mpls_output2: push > Apr 4 15:26:02 norte kernel: mpls_opcode_push: enter > Apr 4 15:26:02 norte kernel: mpls_opcode_push: using tailroom > Apr 4 15:26:02 norte kernel: mpls_opcode_push: done using tailroom > Apr 4 15:26:02 norte kernel: mpls_opcode_push: exit > Apr 4 15:26:02 norte kernel: mpls_output2: set ATM > Apr 4 15:26:02 norte kernel: mpls_output2: output device = atm0 > Apr 4 15:26:02 norte kernel: mpls_finish: enter > Apr 4 15:26:02 norte kernel: mpls_finish: exit > Apr 4 15:26:02 norte kernel: mpls_output2: ATM > Apr 4 15:26:02 norte kernel: mpls_output2: ATM send > Apr 4 15:26:02 norte kernel: mpls_output2: exit(0) > Apr 4 15:26:02 norte kernel: mpls_atm_pop: enter > Apr 4 15:26:02 norte kernel: mpls_atm_pop: exit > Apr 4 15:26:02 norte kernel: mpls_output: exit > Apr 4 15:26:03 norte kernel: mpls_output: enter > Apr 4 15:26:03 norte kernel: mpls_output2: enter > Apr 4 15:26:03 norte kernel: mpls_output2: push > Apr 4 15:26:03 norte kernel: mpls_opcode_push: enter > Apr 4 15:26:03 norte kernel: mpls_opcode_push: using tailroom > Apr 4 15:26:03 norte kernel: mpls_opcode_push: done using tailroom > Apr 4 15:26:03 norte kernel: mpls_opcode_push: exit > Apr 4 15:26:03 norte kernel: mpls_output2: set ATM > Apr 4 15:26:03 norte kernel: mpls_output2: output device = atm0 > Apr 4 15:26:03 norte kernel: mpls_finish: enter > Apr 4 15:26:03 norte kernel: mpls_finish: exit > Apr 4 15:26:03 norte kernel: mpls_output2: ATM > Apr 4 15:26:03 norte kernel: mpls_output2: ATM send > Apr 4 15:26:03 norte kernel: mpls_output2: exit(0) > Apr 4 15:26:03 norte kernel: mpls_atm_pop: enter > Apr 4 15:26:03 norte kernel: mpls_atm_pop: exit > Apr 4 15:26:03 norte kernel: mpls_output: exit > Apr 4 15:26:04 norte kernel: mpls_output: enter > Apr 4 15:26:04 norte kernel: mpls_output2: enter > Apr 4 15:26:04 norte kernel: mpls_output2: push > Apr 4 15:26:04 norte kernel: mpls_opcode_push: enter > Apr 4 15:26:04 norte kernel: mpls_opcode_push: using tailroom > Apr 4 15:26:04 norte kernel: mpls_opcode_push: done using tailroom > Apr 4 15:26:04 norte kernel: mpls_opcode_push: exit > Apr 4 15:26:04 norte kernel: mpls_output2: set ATM > Apr 4 15:26:04 norte kernel: mpls_output2: output device = atm0 > Apr 4 15:26:04 norte kernel: mpls_finish: enter > Apr 4 15:26:04 norte kernel: mpls_finish: exit > Apr 4 15:26:04 norte kernel: mpls_output2: ATM > Apr 4 15:26:04 norte kernel: mpls_output2: ATM send > Apr 4 15:26:04 norte kernel: mpls_output2: exit(0) > Apr 4 15:26:04 norte kernel: mpls_atm_pop: enter > Apr 4 15:26:04 norte kernel: mpls_atm_pop: exit > Apr 4 15:26:04 norte kernel: mpls_output: exit > Apr 4 15:26:05 norte kernel: mpls_output: enter > Apr 4 15:26:05 norte kernel: mpls_output2: enter > Apr 4 15:26:05 norte kernel: mpls_output2: push > Apr 4 15:26:05 norte kernel: mpls_opcode_push: enter > Apr 4 15:26:05 norte kernel: mpls_opcode_push: using tailroom > Apr 4 15:26:05 norte kernel: mpls_opcode_push: done using tailroom -- James R. Leu |
