From JayasriS at aaesys.com Wed Nov 3 14:20:44 2010 From: JayasriS at aaesys.com (Jayasri Sangu) Date: Wed, 3 Nov 2010 14:20:44 -0700 Subject: [Xorp-users] PIM-SM multiple receivers In-Reply-To: <4CCAFCF9.4090007@candelatech.com> References: <2DE723F44CAFD24A9B6BF606813F010C4078EAF4E3@aae-exch> <2DE723F44CAFD24A9B6BF606813F010C4078EAF58C@aae-exch> <4CCAF374.8040707@candelatech.com> <2DE723F44CAFD24A9B6BF606813F010C4078EAF5CE@aae-exch> <4CCAFCF9.4090007@candelatech.com> Message-ID: <2DE723F44CAFD24A9B6BF606813F010C4078EAF659@aae-exch> Hi All, I have a network with four PIM-SM routers as given below. [cid:image001.png at 01CB7B62.4D15B1F0] [cid:image002.png at 01CB7B62.4D15B1F0] [cid:image003.png at 01CB7B62.4D15B1F0] [cid:image004.png at 01CB7B62.4D15B1F0] R3 with PIM-SM R3 with PIM-SM R2 with PIM-SM R1 with PIM-SM LAN When the sender sends the multicast packet, only one receiver is receiver is receiving the multicast packets. Why not other two receivers are not receiving the multicast packets? I can see all the PIM routers have other three PIM routers as neighbors and receiving the BOOTSTRAP messages from all other three routers. Thanks Jayasri Sangu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101103/2bedb8c6/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1258 bytes Desc: image001.png Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101103/2bedb8c6/attachment-0007.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1260 bytes Desc: image002.png Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101103/2bedb8c6/attachment-0008.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 1251 bytes Desc: image003.png Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101103/2bedb8c6/attachment-0009.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 1604 bytes Desc: image004.png Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101103/2bedb8c6/attachment-0010.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 155 bytes Desc: image005.png Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101103/2bedb8c6/attachment-0011.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 165 bytes Desc: image006.png Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101103/2bedb8c6/attachment-0012.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 157 bytes Desc: image007.png Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101103/2bedb8c6/attachment-0013.bin From allanh0526 at gmail.com Wed Nov 3 20:15:39 2010 From: allanh0526 at gmail.com (Yen Wen) Date: Thu, 4 Nov 2010 11:15:39 +0800 Subject: [Xorp-users] Multicast address with reserved field set to zero Message-ID: Hi all, Recently I am trying to do a ipv6 Multicast Routing test which I get into trouble in. Any guidance and hints are precious for me and I will be appreciated. I'm trying to run XORP-1.5 in a multicast scenario using Ubuntu 9.04. (Rebuild kernel to linux-2.6.29) Previously, I used xorp in a basic multicast topology and all was fine. (TN1->RUT->TN2) Now I want to test TN2's multicast address with reserved field set to zero and the RUT must not forward multicast packets to TN2. The test procedure mainly refer to IPv6 Ready Logo Core Self_Test-5.0.0 (by *TAHI* Project). v6LC_1_1_10_J - IP Forwarding - Source and Destination Address - Intermediate Node (Request sent to Multicast address (Reserved Value = 0)) Verify that a node properly forwards the ICMPv6 Echo Requests. TN1 RUT TN2 (Link0) (Link1) | | | |-------------------------->| | | Echo Request | | | | | | |-------------------------->| | | no packet | | | | | | | v v v 1. Configure multicast routing on the RUT. 2. TN2 is a Listener for the multicast group FF10::1:2. 3. TN1 transmits an Echo Request to TN2's multicast address with reserved field set to zero (FF10::1:2) with a first hop through the RUT. The source address is TN1's Global address. 4. Observe the packets transmitted by the RUT on Link1. Multicast address FF10::1:2 ^ When Reserved Value = 0, the NUT must not forward the Echo Request. Result: The NUT must not forward the Echo Request(Reserved Value = 0), but it still forward the echo request from TN1 to TN2. # cat config.boot interfaces { restore-original-config-on-shutdown: false interface eth3 { description: "Ethernet Interface #3" disable: false discard false default-system-config { } } interface eth4 { description: "Ethernet Interface #4" disable: false discard false default-system-config { } } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea6 { disable: false interface eth3 { vif eth3 { disable: false } } interface eth4 { vif eth4 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } traceoptions { flag all { disable: false } } } } protocols { mld { disable: false interface eth3 { vif eth3 { disable: false version: 2 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } interface eth4 { vif eth4 { disable: false version: 2 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } traceoptions { flag all { disable: false } } } } protocols { pimsm6 { disable: false interface eth3 { vif eth3 { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface eth4 { vif eth4 { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } static-rps { rp 3ffe:501:ffff:101:260:e0ff:fe4a:fac3 { group-prefix ff10::/8 { rp-priority: 192 hash-mask-len: 126 } } } switch-to-spt-threshold { disable: false interval: 100 bytes: 102400 } traceoptions { flag all { disable: false } } } } protocols { fib2mrib { disable: false } } root at desktop> show mld group Interface Group Source LastReported Timeout V State eth4 ff10::1:2 :: fe80::200:ff:fe00:101 257 1 E root at desktop> show pim6 mfc Group Source RP ff10::1:2 3ffe:501:ffff:100:200:ff:fe00:100 3ffe:501:ffff:101:260:e0ff:fe4a:fac3 Incoming interface : eth3 Outgoing interfaces: .O. root at desktop> show mfea6 dataflow Group Source ff10::1:2 3ffe:501:ffff:100:200:ff:fe00:100 Measured(Start|Packets|Bytes) Type Thresh(Interval|Packets|Bytes) Remain 79310.673584|0|? <= 210.0|0|? 201.825812 79310.673813|?|0 >= 100.0|?|102400 91.826041 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101104/b0bdd0b5/attachment.html From greearb at candelatech.com Wed Nov 3 20:45:52 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 03 Nov 2010 20:45:52 -0700 Subject: [Xorp-users] Multicast address with reserved field set to zero In-Reply-To: References: Message-ID: <4CD22C70.6010005@candelatech.com> On 11/03/2010 08:15 PM, Yen Wen wrote: > Hi all, > Recently I am trying to do a ipv6 Multicast Routing test which I get into trouble in. > Any guidance and hints are precious for me and I will be appreciated. > > I'm trying to run XORP-1.5 in a multicast scenario using Ubuntu 9.04. (Rebuild kernel to linux-2.6.29) > Previously, I used xorp in a basic multicast topology and all was fine. (TN1->RUT->TN2) > Now I want to test TN2's multicast address with reserved field set to zero and the RUT must not forward multicast packets to TN2. I know the latest xorp.ct and kernel 2.6.34+ can work with IPv6 multicast, but there may still be issues we haven't found, and I don't think we've tested your scenario. If you do fix it, please post a patch and I'll try to integrate it into xorp.ct. Or, it may be a kernel bug, in which case you might try 2.6.36 kernel and hope someone has fixed it (I'd be interested to see any kernel patch you might come up with as well..) Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Wed Nov 3 20:52:47 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 03 Nov 2010 20:52:47 -0700 Subject: [Xorp-users] PIM-SM multiple receivers In-Reply-To: <2DE723F44CAFD24A9B6BF606813F010C4078EAF659@aae-exch> References: <2DE723F44CAFD24A9B6BF606813F010C4078EAF4E3@aae-exch> <2DE723F44CAFD24A9B6BF606813F010C4078EAF58C@aae-exch> <4CCAF374.8040707@candelatech.com> <2DE723F44CAFD24A9B6BF606813F010C4078EAF5CE@aae-exch> <4CCAFCF9.4090007@candelatech.com> <2DE723F44CAFD24A9B6BF606813F010C4078EAF659@aae-exch> Message-ID: <4CD22E0F.4090907@candelatech.com> On 11/03/2010 02:20 PM, Jayasri Sangu wrote: > Hi All, > > I have a network with four PIM-SM routers as given below. > > Oval: REC - 3Oval: REC - 2Oval: REC - 1Oval: Sender > > R3 with PIM-SM > > R3 with PIM-SM > > R2 with PIM-SM > > R1 with PIM-SM > > LAN > > When the sender sends the multicast packet, only one receiver is receiver is receiving the > > multicast packets. Why not other two receivers are not receiving the multicast packets? > > I can see all the PIM routers have other three PIM routers as neighbors and receiving the BOOTSTRAP messages > > from all other three routers. You might check the linux kernels to see if it has MR entries for each of the systems attempting to listen? cat /proc/net/ip_mr_cache cat /proc/net/ip_mr_vif You might sniff to see if the routers see the pkt on the upstream interface, and make sure it has large enough TTL. Make sure you can unicast ping from source to all of your sink machines. What version of xorp are you using, and what OS? Thanks, Ben > > Thanks > > Jayasri Sangu > -- Ben Greear Candela Technologies Inc http://www.candelatech.com From amarnath at copperheadsystems.com Wed Nov 3 21:15:35 2010 From: amarnath at copperheadsystems.com (amarnath at copperheadsystems.com) Date: Wed, 3 Nov 2010 22:15:35 -0600 Subject: [Xorp-users] how to get the list of bugs fixed in xorp-1.6 Message-ID: Hi All, Can anybody please let me know how to see what are bugs fixed in XORP-1.6 and the fixes for that bugs. Regards, Amarnath. From greearb at candelatech.com Wed Nov 3 21:33:52 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 03 Nov 2010 21:33:52 -0700 Subject: [Xorp-users] how to get the list of bugs fixed in xorp-1.6 In-Reply-To: References: Message-ID: <4CD237B0.4040208@candelatech.com> On 11/03/2010 09:15 PM, amarnath at copperheadsystems.com wrote: > Hi All, > Can anybody please let me know how to see what are bugs fixed in XORP-1.6 > and the fixes for that bugs. This might help a bit, but I wasn't active in xorp at that time and didn't write the rls notes for pre 1.7. https://github.com/greearb/xorp.ct/blob/master/xorp/RELEASE_NOTES Thanks, Ben > > Regards, > Amarnath. > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com From ilya at psn.ru Tue Nov 9 02:31:03 2010 From: ilya at psn.ru (Ilya Ovchinnikov) Date: Tue, 09 Nov 2010 13:31:03 +0300 Subject: [Xorp-users] host routes, proxy arp and multicast Message-ID: <4CD922E7.90001@psn.ru> Hi All! We operate a network with central router (linux), many vlan's and a lot of host routes: % ip r l 10.0.0.2 dev vlan823 proto static scope link src 10.0.0.1 10.0.0.4 dev vlan908 proto static scope link src 10.0.0.1 10.0.0.5 dev vlan532 proto static scope link src 10.0.0.1 10.0.0.6 dev vlan901 proto static scope link src 10.0.0.1 10.0.0.7 dev vlan535 proto static scope link src 10.0.0.1 10.0.0.8 dev vlan624 proto static scope link src 10.0.0.1 10.0.0.9 dev vlan509 proto static scope link src 10.0.0.1 10.0.0.10 dev vlan605 proto static scope link src 10.0.0.1 . . . 10.0.0.34 dev vlan2853 proto static scope link src 10.0.0.1 . . . Proxy-arp is used on the router. No IP address were assigned to vlan### interfaces. Now we need to set up multicast routing between multicast source on eth5 and all these vlan's. XORP refuses to work with this configuration - it says: [ 2010/11/09 12:45:07.110947 TRACE xorp_igmp MLD6IGMP ] mld6igmp_process: RX IGMP_V2_LEAVE_GROUP from 10.0.0.34 to 224.0.0.2 on vif vlan2853 [ 2010/11/09 12:45:07.110982 WARNING xorp_igmp MLD6IGMP ] RX IGMP_V2_LEAVE_GROUP from 10.0.0.34 to 224.0.0.2 on vif vlan2853: source must be directly connected Can anybody please suggest a solution without total renumbering? With best regads, Ilya Ovchinnikov From JayasriS at aaesys.com Tue Nov 16 09:08:55 2010 From: JayasriS at aaesys.com (Jayasri Sangu) Date: Tue, 16 Nov 2010 09:08:55 -0800 Subject: [Xorp-users] XrlPFSTCPSender died: Keepalive timeout In-Reply-To: References: Message-ID: <2DE723F44CAFD24A9B6BF606813F010C4078EAF7A7@aae-exch> Hi All, I am running xorp-1.6 on my linux modems as a PIM router. If I keep running the PIM router I am getting XrlPFSTCPSender died: Keepalive timeout errors and PIM router stops working. Is there any timeout set for PIM router? [ 1970/01/01 08:04:07 ERROR xorp_igmp:365 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepa live timeout [ 1970/01/01 08:04:13 ERROR xorp_rib:363 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepal ive timeout [ 1970/01/01 08:04:14 ERROR xorp_pimsm4:366 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Kee palive timeout [ 1970/01/01 08:04:14 ERROR xorp_rtrmgr:361 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Kee palive timeout [ 1970/01/01 08:04:14 ERROR xorp_igmp:365 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepa live timeout [ 1970/01/01 08:04:15 ERROR xorp_fib2mrib:364 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: K eepalive timeout [ 1970/01/01 08:04:17 ERROR xorp_pimsm4:366 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Kee palive timeout [ 1970/01/01 08:04:17 ERROR xorp_pimsm4:366 PIM +2476 xrl_pim_node.cc fea_client_send_protocol_mess age_cb ] Cannot send a protocol message: 210 Transport failed [ 1970/01/01 08:04:17 INFO xorp_pimsm4 XRL ] Sender died (protocol = "stcp", address = "127.0.0.1:59 349") [ 1970/01/01 08:04:18 ERROR xorp_igmp:365 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepa live timeout [ 1970/01/01 08:04:22 ERROR xorp_pimsm4:366 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Kee palive timeout [ 1970/01/01 08:04:22 ERROR xorp_rtrmgr:361 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Kee palive timeout [ 1970/01/01 08:04:24 ERROR xorp_fib2mrib:364 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: K eepalive timeout [ 1970/01/01 08:04:25 ERROR xorp_rib:363 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepal ive timeout [ 1970/01/01 08:04:26 ERROR xorp_pimsm4:366 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Kee palive timeout [ 1970/01/01 08:04:26 ERROR xorp_rtrmgr:361 FINDER +91 finder_xrl_queue.hh dispatch_cb ] Sent xrl g ot response 211 Reply timed out [ 1970/01/01 08:04:26 ERROR xorp_rtrmgr:361 FINDER +91 finder_xrl_queue.hh dispatch_cb ] Sent xrl g ot response 211 Reply timed out [ 1970/01/01 08:04:26 ERROR xorp_rtrmgr:361 FINDER +91 finder_xrl_queue.hh dispatch_cb ] Sent xrl g ot response 211 Reply timed out [ 1970/01/01 08:04:26 ERROR xorp_rtrmgr:361 FINDER +91 finder_xrl_queue.hh dispatch_cb ] Sent xrl g ot response 211 Reply timed out [ 1970/01/01 08:04:27 ERROR xorp_pimsm4:366 PIM +2799 xrl_pim_node.cc finder_event_observer_0_1_xrl _target_death ] FEA (instance fea-a700290ec07a1f3ef4083c1b5cdd350f at 127.0.0.1) has died, shutting dow n. [ 1970/01/01 08:04:27 WARNING xorp_pimsm4 PIM ] ==IN 11== delete RP 10.174.100.223 for group prefix 224.0.1.20/32 [ 1970/01/01 08:04:27 WARNING xorp_pimsm4 PIM ] == CALL delete bsr_rp rp-addr = 10.174.100.223 [ 1970/01/01 08:04:27 INFO xorp_pimsm4 PIM ] Bootstrap mechanism stopped [ 1970/01/01 08:04:27 INFO xorp_pimsm4 PIM ] Interface stopped: Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.174.100.223 subnet: 10.174.100.0/24 broadcast: 10.174.100.255 peer: 0.0.0.0 Flags: MULTICAS T BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 1970/01/01 08:04:27 INFO xorp_pimsm4 PIM ] Interface stopped: Vif[sat0] pif_index: 6 vif_index: 1 addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 1970/01/01 08:04:27 INFO xorp_pimsm4 PIM ] Interface stopped: Vif[register_vif] pif_index: 0 vif_i ndex: 2 addr: 10.174.100.223 subnet: 10.174.100.223/32 broadcast: 0.0.0.0 peer: 0.0.0.0 Flags: PIM_R EGISTER UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 1970/01/01 08:04:27 ERROR xorp_fib2mrib:364 FIB2MRIB +1572 xrl_fib2mrib_node.cc finder_event_obse rver_0_1_xrl_target_death ] FEA (instance fea-a700290ec07a1f3ef4083c1b5cdd350f at 127.0.0.1) has died, shutting down. [ 1970/01/01 08:04:27 ERROR xorp_igmp:365 MLD6IGMP +1624 xrl_mld6igmp_node.cc finder_event_observer _0_1_xrl_target_death ] FEA (instance fea-a700290ec07a1f3ef4083c1b5cdd350f at 127.0.0.1) has died, shut ting down. [ 1970/01/01 08:04:27 INFO xorp_igmp MLD6IGMP ] Interface stopped: Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.174.100.223 subnet: 10.174.100.0/24 broadcast: 10.174.100.255 peer: 0.0.0.0 Flags: MULTI CAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 1970/01/01 08:04:27 INFO xorp_igmp MLD6IGMP ] Interface stopped: Vif[sat0] pif_index: 6 vif_index: 1 addr: 10.0.1.223 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCA ST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 1970/01/01 08:04:27 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "MFEA_4" does not exist or is not enabled. [ 1970/01/01 08:04:27 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "fea" does not exist or is not enabled. [ 1970/01/01 08:04:27 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "MFEA_4" does not exist or is not enabled. [ 1970/01/01 08:04:27 WARNING xorp_pimsm4 XrlPimTarget ] Handling method for mld6igmp_client/0.1/del ete_membership4 failed: XrlCmdError 102 Command failed Failed to delete membership for (0.0.0.0, 224 .0.0.2) [ 1970/01/01 08:04:27 ERROR xorp_igmp:365 MLD6IGMP +1092 xrl_mld6igmp_node.cc mld6igmp_client_send_ add_delete_membership_cb ] Cannot delete membership for a multicast group with a client: 102 Command failed Failed to delete membership for (0.0.0.0, 224.0.0.2) [ 1970/01/01 08:04:27 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "fea" does not exist or is not enabled. [ 1970/01/01 08:04:27 WARNING xorp_pimsm4 XrlPimTarget ] Handling method for mld6igmp_client/0.1/del ete_membership4 failed: XrlCmdError 102 Command failed Failed to delete membership for (0.0.0.0, 224 .0.0.13) [ 1970/01/01 08:04:27 WARNING xorp_pimsm4 XrlPimTarget ] Handling method for mld6igmp_client/0.1/del ete_membership4 failed: XrlCmdError 102 Command failed Failed to delete membership for (0.0.0.0, 224 .0.0.22) [ 1970/01/01 08:04:27 INFO xorp_rtrmgr:361 RTRMGR +280 module_manager.cc module_exited ] Module nor mal exit: fib2mrib [ 1970/01/01 08:04:27 ERROR xorp_igmp:365 MLD6IGMP +1092 xrl_mld6igmp_node.cc mld6igmp_client_send_ add_delete_membership_cb ] Cannot delete membership for a multicast group with a client: 102 Command failed Failed to delete membership for (0.0.0.0, 224.0.0.13) [ 1970/01/01 08:04:27 ERROR xorp_igmp:365 MLD6IGMP +1092 xrl_mld6igmp_node.cc mld6igmp_client_send_ add_delete_membership_cb ] Cannot delete membership for a multicast group with a client: 102 Command failed Failed to delete membership for (0.0.0.0, 224.0.0.22) [ 1970/01/01 08:04:27 ERROR xorp_pimsm4:366 PIM +2806 xrl_pim_node.cc finder_event_observer_0_1_xrl _target_death ] MFEA (instance MFEA_4-5c3b3f84b2f6d979a2b55b7856f81193 at 127.0.0.1) has died, shutting down. [ 1970/01/01 08:04:27 ERROR xorp_igmp:365 MLD6IGMP +1631 xrl_mld6igmp_node.cc finder_event_observer _0_1_xrl_target_death ] MFEA (instance MFEA_4-5c3b3f84b2f6d979a2b55b7856f81193 at 127.0.0.1) has died, shutting down. [ 1970/01/01 08:04:47 ERROR xorp_pimsm4:366 XRL +720 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Kee palive timeout [ 1970/01/01 08:04:47 ERROR xorp_pimsm4:366 PIM +2476 xrl_pim_node.cc fea_client_send_protocol_mess age_cb ] Cannot send a protocol message: 210 Transport failed [ 1970/01/01 08:04:47 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "fea" does not exist or is not enabled. [ 1970/01/01 08:04:47 ERROR xorp_pimsm4:366 PIM +2476 xrl_pim_node.cc fea_client_send_protocol_mess age_cb ] Cannot send a protocol message: 201 Resolve failed [ 1970/01/01 08:04:47 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "fea" does not exist or is not enabled. [ 1970/01/01 08:04:47 ERROR xorp_pimsm4:366 PIM +2476 xrl_pim_node.cc fea_client_send_protocol_mess age_cb ] Cannot send a protocol message: 201 Resolve failed [ 1970/01/01 08:04:47 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "MFEA_4" does not exist or is not enabled. [ 1970/01/01 08:04:47 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "fea" does not exist or is not enabled. [ 1970/01/01 08:04:47 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "fea" does not exist or is not enabled. [ 1970/01/01 08:04:47 ERROR xorp_pimsm4:366 PIM +2476 xrl_pim_node.cc fea_client_send_protocol_mess age_cb ] Cannot send a protocol message: 201 Resolve failed [ 1970/01/01 08:04:47 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "MFEA_4" does not exist or is not enabled. [ 1970/01/01 08:04:47 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "fea" does not exist or is not enabled. [ 1970/01/01 08:04:47 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "MFEA_4" does not exist or is not enabled. [ 1970/01/01 08:04:47 WARNING xorp_rtrmgr:361 XrlFinderTarget +407 ../xrl/targets/finder_base.cc ha ndle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Com mand failed Target "fea" does not exist or is not enabled. [ 1970/01/01 08:06:49 ERROR xorp_igmp:365 XRL +378 xrl_pf_stcp.cc die ] STCPRequestHandler died: li fe timer expired [ 1970/01/01 08:06:52 ERROR xorp_igmp:365 XRL +378 xrl_pf_stcp.cc die ] STCPRequestHandler died: li fe timer expired [ 1970/01/01 08:06:54 ERROR xorp_pimsm4:366 XRL +378 xrl_pf_stcp.cc die ] STCPRequestHandler died: life timer expired [ 1970/01/01 08:06:55 ERROR xorp_rib:363 XRL +378 xrl_pf_stcp.cc die ] STCPRequestHandler died: lif e timer expired Thanks Jayasri From greearb at candelatech.com Tue Nov 16 09:23:23 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 16 Nov 2010 09:23:23 -0800 Subject: [Xorp-users] XrlPFSTCPSender died: Keepalive timeout In-Reply-To: <2DE723F44CAFD24A9B6BF606813F010C4078EAF7A7@aae-exch> References: <2DE723F44CAFD24A9B6BF606813F010C4078EAF7A7@aae-exch> Message-ID: <4CE2BE0B.1050000@candelatech.com> On 11/16/2010 09:08 AM, Jayasri Sangu wrote: > Hi All, > > I am running xorp-1.6 on my linux modems as a PIM router. If I keep running the PIM router > I am getting XrlPFSTCPSender died: Keepalive timeout errors and PIM router stops working. > > Is there any timeout set for PIM router? There is a global variable (or maybe #define) somewhere that determines the timeout. You could hack that and re-compiled. It has already been increased in xorp-ct (helps with running lots of xorp processes on slow virtual-machines, or with something like valgrind enabled). That said, unless you are running under high load on a really slow system, you probably shouldn't be seeing timeouts. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From robert.borz at web.de Fri Nov 26 04:39:40 2010 From: robert.borz at web.de (Robert Borz) Date: Fri, 26 Nov 2010 13:39:40 +0100 (CET) Subject: [Xorp-users] OSPF Multipath Routes Message-ID: <1315190462.600191.1290775180565.JavaMail.fmail@mwmweb071> Hello, I'm currently having a shot at Xorp as an alternative to Quagga, but I'm unable to configure OSPF so that the result will be a multipath route with multiple gateways. Here's my test setup: Two routers (A and B) interconnected by two physical ethernet cards each. First line on A has 172.16.1.1/24, second one has 172.16.2.1/24. There's also an additional dummy interface having 192.168.100.1/32. First ethernet line on B has 172.16.1.2/24, second line has 172.16.2.2/24. Here's an dummy interface, too, having the IP address 192.168.100.2/32. With my Quagga setup, the resulting routing tables are like this: Host A: 192.168.100.2 proto zebra metric 20 nexthop via 172.16.1.2 dev eth0 weight 1 nexthop via 172.16.2.2 dev eth1 weight 1 172.16.2.0/24 dev eth1 proto kernel scope link src 172.16.2.1 172.16.1.0/24 dev eth0 proto kernel scope link src 172.16.1.1 Host B (MikroTik machine): # DST-ADDRESS PREF-SRC GATEWAY DISTANCE ... 2 ADo 192.168.100.1/32 172.16.2.1 110 172.16.1.1 ... But exchanging Quagga on host A by Xorp (config.boot see below) results in this routing table: 192.168.100.2 via 172.16.1.2 dev eth0 proto xorp metric 11 notify 172.16.2.0/24 dev eth1 proto kernel scope link src 172.16.2.1 172.16.1.0/24 dev eth0 proto kernel scope link src 172.16.1.1 The routes on Host B stay the same, regardless of Host A runs Quagga or Xorp. Doesn't Xorp support multipath routes with OSPF? Or is it just an configuration issue? Regards, Robert Borz ------------------------------ boot.config ------------------------------ interfaces { restore-original-config-on-shutdown: false interface eth0 { disable: false vif eth0 { disable: false address 172.16.1.1 { prefix-length: 24 broadcast: 172.16.1.255 disable: false } } } interface eth1 { disable: false vif eth1 { disable: false address 172.16.2.1 { prefix-length: 24 broadcast: 172.16.2.255 disable: false } } } interface dummy0 { disable: false vif dummy0 { disable: false address 192.168.100.1 { prefix-length: 32 disable: false } } } } protocols { ospf4 { router-id: 192.168.100.1 area 0.0.0.0 { interface eth0 { vif eth0 { address 172.16.1.1 { disable: false } } } interface eth1 { vif eth1 { address 172.16.2.1 { disable: false } } } } area 192.168.100.1 { interface dummy0 { vif dummy0 { address 192.168.100.1 { } } } } } } ------------------------------------------------------------------------- ___________________________________________________________ WEB.DE DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2 From B32946 at freescale.com Mon Nov 29 11:19:37 2010 From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946) Date: Mon, 29 Nov 2010 12:19:37 -0700 Subject: [Xorp-users] XORP-PIM Commands are NOT Working ! Message-ID: <9D8289DE2B23FA4EBC165B4CFB37186601BEB3@039-SN1MPN1-004.039d.mgd.msft.net> Hi Guys, I am a new bie to XORP and trying to use it for PIM-SM V4. The issus is ; I have installed the binaries and able to start the necessary daemons on my Ubuntu Machine. But when I am trying to use the CLI; some commands are NOT Working. All the PIM Related Commands are NOT Working. It is throwing me an error message saying that "Invalid Xorp Command" Ex: show PIM neighbors etc.. So., how to bypass this error? And what is the reason for which these commands are NOT executable on CLI of XORP ? I Logged in as XORP [User Name]. Thanks in Advance . Looking forward for the reply ! -Best Regards, VKS. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101129/402a6b9f/attachment.html From jmitchell at ll.mit.edu Mon Nov 29 11:21:25 2010 From: jmitchell at ll.mit.edu (Jeff Mitchell) Date: Mon, 29 Nov 2010 14:21:25 -0500 Subject: [Xorp-users] XORP-PIM Commands are NOT Working ! In-Reply-To: <9D8289DE2B23FA4EBC165B4CFB37186601BEB3@039-SN1MPN1-004.039d.mgd.msft.net> References: <9D8289DE2B23FA4EBC165B4CFB37186601BEB3@039-SN1MPN1-004.039d.mgd.msft.net> Message-ID: <4CF3FD35.5070207@ll.mit.edu> On 11/29/2010 02:19 PM, Vunnava Kesava Srinivas-B32946 wrote: > Hi Guys, > I am a new bie to XORP and trying to use it for PIM-SM V4. The issus is > ; I have installed the binaries and able to start the necessary daemons > on my Ubuntu Machine. But when I am trying to use the CLI; some commands > are NOT Working. All the PIM Related Commands are NOT Working. It is > throwing me an error message saying that "Invalid Xorp Command" > Ex: show PIM neighbors etc.. They'd work if you used the right name. It's "pim" not "PIM". --Jeff From B32946 at freescale.com Mon Nov 29 11:22:21 2010 From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946) Date: Mon, 29 Nov 2010 12:22:21 -0700 Subject: [Xorp-users] XORP-PIM Commands are NOT Working ! In-Reply-To: <4CF3FD35.5070207@ll.mit.edu> References: <9D8289DE2B23FA4EBC165B4CFB37186601BEB3@039-SN1MPN1-004.039d.mgd.msft.net>, <4CF3FD35.5070207@ll.mit.edu> Message-ID: <9D8289DE2B23FA4EBC165B4CFB37186601BEC5@039-SN1MPN1-004.039d.mgd.msft.net> oh Sorry . Here for an example ; I have shown in CAPS. But in real I tried SMALL Letters only. Not Working. Is there any Prerequisite for it ? -VKS. ________________________________ From: Jeff Mitchell [jmitchell at ll.mit.edu] Sent: 30 November 2010 00:51:25 To: Vunnava Kesava Srinivas-B32946 Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] XORP-PIM Commands are NOT Working ! On 11/29/2010 02:19 PM, Vunnava Kesava Srinivas-B32946 wrote: > Hi Guys, > I am a new bie to XORP and trying to use it for PIM-SM V4. The issus is > ; I have installed the binaries and able to start the necessary daemons > on my Ubuntu Machine. But when I am trying to use the CLI; some commands > are NOT Working. All the PIM Related Commands are NOT Working. It is > throwing me an error message saying that "Invalid Xorp Command" > Ex: show PIM neighbors etc.. They'd work if you used the right name. It's "pim" not "PIM". --Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101129/1ff5807e/attachment.html From greearb at candelatech.com Tue Nov 30 10:24:23 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 30 Nov 2010 10:24:23 -0800 Subject: [Xorp-users] XORP-PIM Commands are NOT Working ! In-Reply-To: <9D8289DE2B23FA4EBC165B4CFB37186601BEC5@039-SN1MPN1-004.039d.mgd.msft.net> References: <9D8289DE2B23FA4EBC165B4CFB37186601BEB3@039-SN1MPN1-004.039d.mgd.msft.net>, <4CF3FD35.5070207@ll.mit.edu> <9D8289DE2B23FA4EBC165B4CFB37186601BEC5@039-SN1MPN1-004.039d.mgd.msft.net> Message-ID: <4CF54157.9070404@candelatech.com> On 11/29/2010 11:22 AM, Vunnava Kesava Srinivas-B32946 wrote: > oh Sorry . Here for an example ; I have shown in CAPS. But in real I > tried SMALL Letters only. Not Working. > Is there any Prerequisite for it ? Please show us your config file, the exact command you tried and it's errors, and let us know what version of xorp you are using. You should provide this sort of information with any bug report for any project. We may still not know how to fix your issue, but at least we'd have a chance! Thanks, Ben > -VKS. > ------------------------------------------------------------------------ > *From:* Jeff Mitchell [jmitchell at ll.mit.edu] > *Sent:* 30 November 2010 00:51:25 > *To:* Vunnava Kesava Srinivas-B32946 > *Cc:* xorp-users at xorp.org > *Subject:* Re: [Xorp-users] XORP-PIM Commands are NOT Working ! > > On 11/29/2010 02:19 PM, Vunnava Kesava Srinivas-B32946 wrote: > > Hi Guys, > > I am a new bie to XORP and trying to use it for PIM-SM V4. The issus is > > ; I have installed the binaries and able to start the necessary daemons > > on my Ubuntu Machine. But when I am trying to use the CLI; some commands > > are NOT Working. All the PIM Related Commands are NOT Working. It is > > throwing me an error message saying that "Invalid Xorp Command" > > Ex: show PIM neighbors etc.. > > They'd work if you used the right name. It's "pim" not "PIM". > > --Jeff > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com From p_latini at hotmail.com Tue Nov 30 15:10:04 2010 From: p_latini at hotmail.com (Patricio Latini) Date: Tue, 30 Nov 2010 23:10:04 +0000 Subject: [Xorp-users] OSPF6 not working Message-ID: I am trying to configure ospf6 on an interface, however i so not see any hello going out. Has anybody got working ospf6 on v1.6? Thanks a lot Patricio This is the configuration ospf6 0 { router-id: 172.17.0.1 area 1.0.0.1 { default-lsa { } interface vlan18 { vif vlan18 { address FC00:0000:0000:FF00::1 { } hello-interval: 1 } } interface vlan19 { vif vlan19 { address FC00:0000:0000:FF01::1 { } } } } } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101130/19dc49b1/attachment.html From greearb at candelatech.com Tue Nov 30 15:17:47 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 30 Nov 2010 15:17:47 -0800 Subject: [Xorp-users] OSPF6 not working In-Reply-To: References: Message-ID: <4CF5861B.3030203@candelatech.com> On 11/30/2010 03:10 PM, Patricio Latini wrote: > I am trying to configure ospf6 on an interface, however i so not see any > hello going out. > > Has anybody got working ospf6 on v1.6? I know it can work in xorp.ct, but I haven't tried it in v1.6. I think you'll need a global and link-local IPv6 addr configured for each interface. You might look here for some example configs: https://github.com/greearb/xorp.ct/tree/master/xorp/rtrmgr/config ospf-mcast-router1.conf ospf-mcast-router2.conf Thanks, Ben > > Thanks a lot > > Patricio > > This is the configuration > > ospf6 0 { > router-id: 172.17.0.1 > area 1.0.0.1 { > default-lsa { > } > interface vlan18 { > vif vlan18 { > address FC00:0000:0000:FF00::1 { > } > hello-interval: 1 > } > } > interface vlan19 { > vif vlan19 { > address FC00:0000:0000:FF01::1 { > } > } > } > } > } > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com From p_latini at hotmail.com Tue Nov 30 15:58:51 2010 From: p_latini at hotmail.com (Patricio Latini) Date: Tue, 30 Nov 2010 23:58:51 +0000 Subject: [Xorp-users] OSPF6 not working In-Reply-To: <4CF5861B.3030203@candelatech.com> References: , <4CF5861B.3030203@candelatech.com> Message-ID: Ben, thanks a lot. Adding the link-local address to the interfaces made the difference. Now it is working fine! Patricio > Date: Tue, 30 Nov 2010 15:17:47 -0800 > From: greearb at candelatech.com > To: p_latini at hotmail.com > CC: xorp-users at xorp.org > Subject: Re: [Xorp-users] OSPF6 not working > > On 11/30/2010 03:10 PM, Patricio Latini wrote: > > I am trying to configure ospf6 on an interface, however i so not see any > > hello going out. > > > > Has anybody got working ospf6 on v1.6? > > I know it can work in xorp.ct, but I haven't tried it in v1.6. > > I think you'll need a global and link-local IPv6 addr configured > for each interface. You might look here for some example configs: > > https://github.com/greearb/xorp.ct/tree/master/xorp/rtrmgr/config > > ospf-mcast-router1.conf > ospf-mcast-router2.conf > > Thanks, > Ben > > > > > Thanks a lot > > > > Patricio > > > > This is the configuration > > > > ospf6 0 { > > router-id: 172.17.0.1 > > area 1.0.0.1 { > > default-lsa { > > } > > interface vlan18 { > > vif vlan18 { > > address FC00:0000:0000:FF00::1 { > > } > > hello-interval: 1 > > } > > } > > interface vlan19 { > > vif vlan19 { > > address FC00:0000:0000:FF01::1 { > > } > > } > > } > > } > > } > > > > > > > > _______________________________________________ > > Xorp-users mailing list > > Xorp-users at xorp.org > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101130/37304a23/attachment.html From B32946 at freescale.com Tue Nov 30 20:27:39 2010 From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946) Date: Tue, 30 Nov 2010 21:27:39 -0700 Subject: [Xorp-users] XORP-PIM Commands are NOT Working ! In-Reply-To: <4CF54157.9070404@candelatech.com> References: <9D8289DE2B23FA4EBC165B4CFB37186601BEB3@039-SN1MPN1-004.039d.mgd.msft.net>, <4CF3FD35.5070207@ll.mit.edu> <9D8289DE2B23FA4EBC165B4CFB37186601BEC5@039-SN1MPN1-004.039d.mgd.msft.net> <4CF54157.9070404@candelatech.com> Message-ID: <9D8289DE2B23FA4EBC165B4CFB37186601BF51@039-SN1MPN1-004.039d.mgd.msft.net> Thanks Ben. Please find the necessary information. Please note that with the Existing Configuration File ; I am able to start the necessary daemons [pim-sm4 etc... ] . Error ############ xorp at P2020RDB> show pim Not a XORP command! xorp at P2020RDB> show pim Not a XORP command! ######### Configuration File ########################### interfaces { interface eth0 { vif eth0 { address 192.168.1.10 { prefix-length: 24 } } } interface eth1 { vif eth1 { address 10.20.20.20 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } /* traceoptions { flag all { disable: false } } */ } } protocols { igmp { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } /* traceoptions { flag all { disable: false } } */ } } /* protocols { static { mrib-route 10.30.0.0/16 { next-hop: 10.10.10.20 } } } */ protocols { pimsm4 { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } /* Note: static-rps and bootstrap should not be mixed */ static-rps { rp 10.10.10.10 { group-prefix 224.0.0.0/4 { } } } /* bootstrap { disable: false cand-bsr { scope-zone 224.0.0.0/4 { cand-bsr-by-vif-name: "dc0" } } cand-rp { group-prefix 224.0.0.0/4 { cand-rp-by-vif-name: "dc0" } } } */ switch-to-spt-threshold { /* approx. 1K bytes/s (10Kbps) threshold */ disable: false interval: 100 bytes: 102400 } /* traceoptions { flag all { disable: false } } */ } } protocols { fib2mrib { disable: false } } ####################### Looking forward for the reply!. -Wishes, VKS. From: Ben Greear [mailto:greearb at candelatech.com] Sent: Tuesday, November 30, 2010 11:54 PM To: Vunnava Kesava Srinivas-B32946 Cc: Jeff Mitchell; xorp-users at xorp.org Subject: Re: [Xorp-users] XORP-PIM Commands are NOT Working ! On 11/29/2010 11:22 AM, Vunnava Kesava Srinivas-B32946 wrote: > oh Sorry . Here for an example ; I have shown in CAPS. But in real I > tried SMALL Letters only. Not Working. > Is there any Prerequisite for it ? Please show us your config file, the exact command you tried and it's errors, and let us know what version of xorp you are using. You should provide this sort of information with any bug report for any project. We may still not know how to fix your issue, but at least we'd have a chance! Thanks, Ben > -VKS. > ------------------------------------------------------------------------ > *From:* Jeff Mitchell [jmitchell at ll.mit.edu] > *Sent:* 30 November 2010 00:51:25 > *To:* Vunnava Kesava Srinivas-B32946 > *Cc:* xorp-users at xorp.org > *Subject:* Re: [Xorp-users] XORP-PIM Commands are NOT Working ! > > On 11/29/2010 02:19 PM, Vunnava Kesava Srinivas-B32946 wrote: > > Hi Guys, > > I am a new bie to XORP and trying to use it for PIM-SM V4. The issus is > > ; I have installed the binaries and able to start the necessary daemons > > on my Ubuntu Machine. But when I am trying to use the CLI; some commands > > are NOT Working. All the PIM Related Commands are NOT Working. It is > > throwing me an error message saying that "Invalid Xorp Command" > > Ex: show PIM neighbors etc.. > > They'd work if you used the right name. It's "pim" not "PIM". > > --Jeff > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101130/ae36325b/attachment-0001.html From B32946 at freescale.com Tue Nov 30 20:32:52 2010 From: B32946 at freescale.com (Vunnava Kesava Srinivas-B32946) Date: Tue, 30 Nov 2010 21:32:52 -0700 Subject: [Xorp-users] XORP-PIM Commands are NOT Working ! References: <9D8289DE2B23FA4EBC165B4CFB37186601BEB3@039-SN1MPN1-004.039d.mgd.msft.net>, <4CF3FD35.5070207@ll.mit.edu> <9D8289DE2B23FA4EBC165B4CFB37186601BEC5@039-SN1MPN1-004.039d.mgd.msft.net> <4CF54157.9070404@candelatech.com> Message-ID: <9D8289DE2B23FA4EBC165B4CFB37186601BF62@039-SN1MPN1-004.039d.mgd.msft.net> Also forgotten to add that using Xorp Version is 1.6 and the Command I am trying to use is "show pim neighbors" ; but after getting to "pim" itself ; cli is throwing the above mentioned error. The usage of the command is mentioned in pim Test Suite ; page Number 19. -Regards, VKS. From: Vunnava Kesava Srinivas-B32946 Sent: Wednesday, December 01, 2010 9:58 AM To: 'Ben Greear' Cc: Jeff Mitchell; xorp-users at xorp.org Subject: RE: [Xorp-users] XORP-PIM Commands are NOT Working ! Thanks Ben. Please find the necessary information. Please note that with the Existing Configuration File ; I am able to start the necessary daemons [pim-sm4 etc... ] . Error ############ xorp at P2020RDB> show pim Not a XORP command! xorp at P2020RDB> show pim Not a XORP command! ######### Configuration File ########################### interfaces { interface eth0 { vif eth0 { address 192.168.1.10 { prefix-length: 24 } } } interface eth1 { vif eth1 { address 10.20.20.20 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } /* traceoptions { flag all { disable: false } } */ } } protocols { igmp { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } /* traceoptions { flag all { disable: false } } */ } } /* protocols { static { mrib-route 10.30.0.0/16 { next-hop: 10.10.10.20 } } } */ protocols { pimsm4 { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } /* Note: static-rps and bootstrap should not be mixed */ static-rps { rp 10.10.10.10 { group-prefix 224.0.0.0/4 { } } } /* bootstrap { disable: false cand-bsr { scope-zone 224.0.0.0/4 { cand-bsr-by-vif-name: "dc0" } } cand-rp { group-prefix 224.0.0.0/4 { cand-rp-by-vif-name: "dc0" } } } */ switch-to-spt-threshold { /* approx. 1K bytes/s (10Kbps) threshold */ disable: false interval: 100 bytes: 102400 } /* traceoptions { flag all { disable: false } } */ } } protocols { fib2mrib { disable: false } } ####################### Looking forward for the reply!. -Wishes, VKS. From: Ben Greear [mailto:greearb at candelatech.com] Sent: Tuesday, November 30, 2010 11:54 PM To: Vunnava Kesava Srinivas-B32946 Cc: Jeff Mitchell; xorp-users at xorp.org Subject: Re: [Xorp-users] XORP-PIM Commands are NOT Working ! On 11/29/2010 11:22 AM, Vunnava Kesava Srinivas-B32946 wrote: > oh Sorry . Here for an example ; I have shown in CAPS. But in real I > tried SMALL Letters only. Not Working. > Is there any Prerequisite for it ? Please show us your config file, the exact command you tried and it's errors, and let us know what version of xorp you are using. You should provide this sort of information with any bug report for any project. We may still not know how to fix your issue, but at least we'd have a chance! Thanks, Ben > -VKS. > ------------------------------------------------------------------------ > *From:* Jeff Mitchell [jmitchell at ll.mit.edu] > *Sent:* 30 November 2010 00:51:25 > *To:* Vunnava Kesava Srinivas-B32946 > *Cc:* xorp-users at xorp.org > *Subject:* Re: [Xorp-users] XORP-PIM Commands are NOT Working ! > > On 11/29/2010 02:19 PM, Vunnava Kesava Srinivas-B32946 wrote: > > Hi Guys, > > I am a new bie to XORP and trying to use it for PIM-SM V4. The issus is > > ; I have installed the binaries and able to start the necessary daemons > > on my Ubuntu Machine. But when I am trying to use the CLI; some commands > > are NOT Working. All the PIM Related Commands are NOT Working. It is > > throwing me an error message saying that "Invalid Xorp Command" > > Ex: show PIM neighbors etc.. > > They'd work if you used the right name. It's "pim" not "PIM". > > --Jeff > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20101130/79637d11/attachment-0001.html