diya

Members
  • Content count

    70
  • Joined

  • Last visited

  • Days Won

    1

diya last won the day on May 31 2012

diya had the most liked content!

Community Reputation

1 Neutral

About diya

  • Rank
    Member
  1. Any Help Guys??
  2. Hi Guys, One of the things that make the multicast harder for me is tree naming, In sparse mode, the tree that originated from the root toward multicast recievers (*,G) is called shared tree, some times RPT "root path tree" since it is rooted from the RP, But I didn't find a unified name for the tree that orginated from the Source toward the RP (S,G) tree, some time they called SPT "I dont know what does it stand for but Shoretest Path Tree is something very different and cannot be here" and some time they call it shared tree, these different namings make understanding other advanced multicast technologies much harder form me, I just would like clarify those basic things hoping that it will make multicast technologies easier...
  3. R1 configs: R1(config-if)#do sh run | incl ip pim ip pim sparse-mode ip pim sparse-mode ip pim dr-priority 2 ip pim nbma-mode ip pim sparse-mode ip pim rp-address 1.1.1.1 1 interface Serial0/0 ip address 192.168.1.1 255.255.255.0 ip pim dr-priority 2 ip pim nbma-mode ip pim sparse-mode encapsulation frame-relay clock rate 2000000 frame-relay map ip 192.168.1.2 102 broadcast frame-relay map ip 192.168.1.3 103 broadcast are these all required configs to multicast to work?
  4. Hi Gyus.. I have very simple topolgy, R1 is the Hub, R2 nad R3 are spokes, R2 joined to 224.10.10.10 on int loo 0 R3 will ping 224.10.10.10 from its ser int all interfaces configured with sparse-dense mode. NBMA mode is enbled on the hub router although that the frame-relay supports Broadcast. eigrp is the IGP between all links, the fast ethernet int is currently disabled, i put it just to help me figuring out the issue, when I used it instead of serial, multicast traffic between R2 and R3 worked, RP is static and installed on R1 loo0 interface the problem is that when I pinged group 224.10.10.10 from R3 serial interface or even loop interface I got reply only for the first rping, then all ICMPs timed out. what happend is that R1 sends directly prune meassge to the source instantly after adding (S,G). here is the PIM debug output from R1 : as it shows it is not RPF issue: *Mar 1 01:24:52.643: PIM(0): Received v2 Join/Prune on Serial0/0 from 192.168.1.2, to us *Mar 1 01:24:52.647: PIM(0): Join-list: (*, 224.10.10.10), RPT-bit set, WC-bit set, S-bit set *Mar 1 01:24:52.655: PIM(0): Check RP 1.1.1.1 into the (*, 224.10.10.10) entry *Mar 1 01:24:52.659: PIM(0): Add Serial0/0/192.168.1.2 to (*, 224.10.10.10), Forward state, by PIM *G Join *Mar 1 01:24:52.663: PIM(0): Prune-list: (192.168.1.3/32, 224.10.10.10) RPT-bit set R1(config-if)# *Mar 1 01:24:59.359: PIM(0): Received v2 Join/Prune on Serial0/0 from 192.168.1.2, to us *Mar 1 01:24:59.363: PIM(0): Join-list: (192.168.1.3/32, 224.10.10.10), RPT-bit set, S-bit set R1(config-if)# *Mar 1 01:25:37.431: PIM(0): Received v2 Register on Serial0/0 from 192.168.1.2 *Mar 1 01:25:37.435: PIM(0): Send v2 Register-Stop to 192.168.1.2 for 0.0.0.0, group 0.0.0.0 R1(config-if)# *Mar 1 01:25:52.055: PIM(0): Received v2 Join/Prune on Serial0/0 from 192.168.1.2, to us *Mar 1 01:25:52.059: PIM(0): Join-list: (*, 224.10.10.10), RPT-bit set, WC-bit set, S-bit set *Mar 1 01:25:52.063: PIM(0): Update Serial0/0/192.168.1.2 to (*, 224.10.10.10), Forward state, by PIM *G Join *Mar 1 01:25:52.403: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.10.10.10
  5. Hi Guys, I think I have something missing in understanding the differece between IP NAT inside and outside, After Testing them too many times in my LAB I found out : 1-The IP NAT inside source Static translates the inside local source address into global inside and does translate the destination address in oppsite direcion "from inside global to inside local". 2-The IP NAT outside source Static translates the outside global source address into outside local and doesn’t translate the destination address in oppsite direcion from local outside to global inside. Until know it is OK, they simply follow same logic, the only difference comes out in opposite traffic " either return traffic or traffic orginated from opposite direction" but the problem is that this rule will break when I do NAT to translate RIP Multcast address to unicast, the command required is: Ip nat outside source static udp neighbourAdd 520 224.0.0.9 520 First question, from the the above 2 rules, my first impression, I should be able to tranaslate the rip multicast traffic using both command IP NAT inside Source static and IP NAT outside Source static, with just replacing the assignmnet of INSIDE and OUTSIDE in the interface, but it Didn't, only the outside source static command working!. Second, which actually blows out my mind !The NAT outsude command only apworks plies when it is designed in opposite direction of the RIP traffic which is compltetly in contrast of 2nd rule!! just replace the multicast address of 224.0.0.9 in the nat command with a unicast address and the nat doesn't work which exactly follows the 2nd rule! Why my rule just applies to unicast traffic and doesn't apply to the RIP example? " i see the NAT works or not by the command debug IP nat de, and watching the logs" I am working on this This issue for 3 days and I read most cisco documents, but they don't talk much ablut the difference between inside & outside natting, so I would appreciate very much any help to clarifying out this issue, and if you need any more details, please post and I am up for it. Thanks
  6. What u mean, which road? I already have real network and it is for my lab.. help me my friend, I have more than a year preparing for that exam, If you have a better road ...or better Route .. to get into it please help>>
  7. Dears, I am looking for products of Real CCIE lab scenarios and answers to train on them for bothe sections: lab and TroubleShooting , can you tell me product names to purchase or download?
  8. HI, Cisco website exams's blueprint show only three topics in the R&S exam: 4.00 Implement MPLS Layer 3 VPNs 4.10 Implement Multiprotocol Label Switching (MPLS) 4.20 Implement Layer 3 virtual private networks (VPNs) on provider edge (PE), provider (P), and customer edge (CE) routers 4.30 Implement virtual routing and forwarding (VRF) and Multi-VRF Customer Edge (VRF-Lite) Does it include L2TP?
  9. how did you know about me?
  10. wow, I am really excited to go to the exam for the barbecue and burger,
  11. Thank you for help, I agree with you regarding dependencies, but some questions have extra independent requirement that are complicated and consumes time -they put them just to make things worse.. Thankyou my friend, in my self test I was able to solve all requirements in the example below except the DHCP rate limit, I am imagining now if I could not able to solve one small like this q in the real exam, then it will be a nightmare..
  12. Dear friends, If i have for example a question of 3 points having many requirements, then I answered multiple requirement and were not able to complete all of them will I lose all the question points??
  13. think of BGP as an Autonomous System Routing protocol, not network routing protocol, so the network information or "Database" it provides will be like this: (autonomous system , how to reach that AS or the IP address of that AS), how to reach the IP of the AS is not BGP job, it is IGP job, so the address of the AS is enough for Ibgp if you use next-hop self it will not use loopback interface instantly, it will use the IP of the interface which it sends the update out to IBGP if it was loopback or physical interface , also, suppose you have more than one loopback interfaces , how the router will "know" which one you want to use as a next hop? so you have to specify it manually if you don't want the original next hop by using first update-source command and then next-hop self command.
  14. From cisco definition, this command is used to send summary rip prefixes , but rip always advertising the major networks!. so no need to that summary, right?. the ios even rejected summaries beyond classuful networks such as 10.0.0.0/6! Even in the case in which a router (router A for example) has two interfaces with two subnets belong to one classuful network such as 10.2.2.0 , 10.1.1.0 "in this case the router is enforced to advertise thses subnets as they are "without summary" to other routers from the same major network, i tried to configure summary-address rip 10.0.0.0 in router A it didn't work, it did not advertised this summary. so why we need this command??