Jump to content

Search the Community

Showing results for tags 'H2'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • ANNOUNCEMENTS
    • ANNOUNCEMENTS
  • CERTIFICATION - - - - - NO REQUESTS IN THESE FORUMS - - - - -
    • CISCO SYSTEMS
    • COMPTIA
    • LINUX
    • MICROSOFT
    • ORACLE
    • PROJECT MANAGEMENT
    • SECURITY CERTIFICATIONS
    • SUN MICROSYSTEMS
    • WIRELESS
    • OTHER CERTIFICATIONS
  • CISCO TECHNICAL SECTION
    • CISCO LABS
    • GNS3
    • NETWORK INFRASTRUCTURE
    • SECURITY
    • WIRELESS
    • SERVICE PROVIDERS
    • COLLABORATION, VOICE AND VIDEO
    • DATA CENTER
    • SMALL BUSINESS
  • MICROSOFT TECHNICAL SECTION
  • OTHER TECHNICAL SECTION
  • TRAINING OFFERS & REQUESTS
  • CERTCOLLECTION MALL
  • GENERAL FORUMS
  • COMMUNITY CENTER

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 24 results

  1. EVE Comm Edition version (updated to 2.0.84) Pre-Loaded LABS H1, H1+ H2 H2+ H3 TS1 TS2 Devices Used in IOU L2-ADVENTERPRISEK9-M-15.1A.bin L3-ADVENTERPRISEK9-M-15.5-2T.bin CLI Credentials root:eve GUI Credentials admin:eve -----> (all are small) [hide] [Hidden Content]]
  2. Hi guys, Here is my feedback for this LABs' experience: First of all I want to say that I used both vendors with materials found on this forum. Feedback: TS1 1. Layer 2 SW2 didn't had the VLAN 12 on interface eth0/0 2. PPP R17 had the wrong password 3. OSPF R22 had E0/0 as passive 4. EIGRP R11/R12/R14 didn't had the weights right (only R13 had them) R13 had a distribute-list that needed 145.14.14.14/32 to be excluded for offset 5. BGP Decreased the metric on R6 for 123.3.3.3 6. IPv6 R25 needed to advertise the E0/0 network 7. DMVPN R19's access-list needed ESP added R15 needed to add hostname to match output R18 didn't had shortcut under Tu0 8. MPLS R4/R6 needed OSPF cost change for their E2/0 interface (for back-up link) R7/R8 didn't had "default-information originate" under router bgp R8 didn't had "ip nat inside" on E0/0.123 9. DMVPN NAT R7 had wrong address for isakmp key 10. NAT R23 didn't had "ip dns server" ============================================================================================= DIAG - H1+ 90% is the same as the workbook, however the last ticket has different answer than both provider's workbooks. The output from the router shows that you have two next-hops for the desired traffic, therefor you have multiple next-hops but it chooses a single hop based on per-destination load-balancing (I think I've chosen the wrong answers here). ============================================================================================= CFG - H2 Same as Workbooks with some changes: 1.1 SW3/SW4/SW5/SW6 had already VTP + vlans configured SW10/SW11 are not in the VLAN table and you don't need to configure anything on them, they have everything preconfigured SW1/SW2 have already VLANs created. 1.2 It states clear that you need to make SW3 primary for normal VLANs and SW4 as back-up for normal vlans. 1.3 Same WB 1.4 Same WB (interface DIAL1 didn't exist and you have to create the route for 192.0.2.0/24 2.1 Same as WB 2.2 Same as WB 2.3 Same as WB (upgrade-cli worked so I just added the router-id and the TAG and at the end I upgraded to named mode) 2.4 Same as WB (R15/R16 redistribute bgp 65002 subnets metric-type 1 under OSPF process) 2.5, 2.6, 2.7 Same as WB 2.8 The exam did not request verification from SW10, only from R101 2.9, 2.10, 2.11 Same as WB 3.1 Same as WB but the verification required just ping not traceroute 3.2 Same as WB but the verification required just ping not traceroute. However there is a request saying "All sites need to import all prefixes". It is unclear if it should be pre-merge or post-merge as well (see 3.4) 3.3 Diagram 6 + the question itself, showed that you need to change the BGP procces from 65006 to 65001. This means local-as towards R55/R56/R58 and also adapt the iBGP. There is a pre-configured iBGP between R50/R51/R52 which is also present in BGP Diagram and you should keep it when merging. 3.4 This one was tricky. Diagram 6 didn't showed any information to find out what to import where. The only guidelines were that: * DC need to receive all prefixes from all sites (Jamesons + Jacobs) * All sites must receive BGP prefixes from DC * Jamesons Main Office should receive only DC prefixes (actually the text said that Main Office should not receive prefixes from Jamesons HQ nor Jacobs HQ nor Jacobs Office) 4.1 Same as WB (one deny ACL matched in class-map matched in policy-map) 4.2 I left this one last because I wanted to test it. I didn't managed to make it work. The question has a note to itself saying that: "When you do "shut" "no shut" on R101, be sure to do "no ip dhcp snooping vlan 100" and "ip dhcp snooping vlan 100" on the distribution switches (SW3/SW4)) I tried, didn't worked. I did a debug and when the R101 got it's ip, there was a huge broadcast storm between SW6/SW4/SW3/R15. When I removed the dhcp snooping for vlan 100 the broadcast storm stopped. Therefor, just to be sure, i didn't configured dhcp snooping for vlan100 (Did the rest of the config though). 5.1 Same as WB however i've set "lease infinite" for that snooping thing. 5.2, 5.3, 5.4 Same as WB I wish everybody good luck (until 23rd of February - after that....God help us all ).
  3. Hello, I am not able to get any communication between AS65005 & AS65007, so it required ? and if yes should I import/export between 2 ASs directly or traffic should pass through MPLS VPN. also filter at R55/R56 is only advertising 172.17.0.0/16 so how for AS65007 to learn about the /24 prefixes.
  4. ric2ccie

    H2 Section 2.2

    Hi All, Just would like to have your take, what should be the perfect answer that Cisco is expecting, considering that both OSPF network type seems to be a good candidate, so would like to see what would be the best answer: - P2M -> no DR at all; - Broadcast + OSPF priority = 0 in spokes -> Actually the DR election takes place, but Spokes will not take part of it. What do you think? Thanks.
  5. [Hidden Content] please check the attached H2 lab .... hope you got your number ASAP H2.gz
  6. mdual

    H2 DMVPN phase 3

    Hi guys, Labbing the H2 and wanted to share something and find out on your thoughts. The requirement says there should be phase 3 DMVPN for the Brunch net routers R19,R20,R21. the config for the spokes are identical - so I am saring R19, and it looks like this : ! interface Tunnel0 ip address 10.100.0.19 255.255.255.0 no ip redirects ip nhrp authentication 65002key ip nhrp map 10.100.0.1 192.0.2.2 ip nhrp map multicast 192.0.2.2 ip nhrp network-id 51 ip nhrp holdtime 300 ip nhrp nhs 10.100.0.1 ip nhrp shortcut ip ospf network point-to-multipoint delay 100 tunnel source Dialer1 tunnel mode gre multipoint tunnel key 65002 tunnel vrf LOCALSP end for R17, which is NHS : ! interface Tunnel0 ip address 10.100.0.1 255.255.255.0 no ip redirects ip nhrp authentication 65002key ip nhrp map multicast dynamic ip nhrp network-id 51 ip nhrp holdtime 300 ip nhrp redirect ip ospf network point-to-multipoint ip ospf 65002 area 51 delay 100 tunnel source Ethernet0/1 tunnel mode gre multipoint tunnel key 65002 end So ! All works as it should and first trace goes over the hub, then rest go to the spoke directly : first : R19#trace 10.16.2.1 so e 0/1 nu pr 1 Type escape sequence to abort. Tracing the route to 10.16.2.1 VRF info: (vrf in name/id, vrf out name/id) 1 10.100.0.1 1 msec 2 10.100.0.20 6 msec next: R19#trace 10.16.2.1 so e 0/1 nu pr 1 Type escape sequence to abort. Tracing the route to 10.16.2.1 VRF info: (vrf in name/id, vrf out name/id) 1 10.100.0.20 6 msec Now the tricky one : the routing table doesn't have nhrp route installed, it got % - "next hop override" : R19#sh ip ro Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP a - application route + - replicated route, % - next hop override Gateway of last resort is 10.100.0.1 to network 0.0.0.0 O*IA 0.0.0.0/0 [110/1001] via 10.100.0.1, 00:01:29, Tunnel0 10.0.0.0/8 is variably subnetted, 12 subnets, 2 masks C 10.16.1.0/24 is directly connected, Ethernet0/1 L 10.16.1.1/32 is directly connected, Ethernet0/1 O % 10.16.2.0/24 [110/2010] via 10.100.0.1, 00:01:29, Tunnel0 O 10.16.3.0/24 [110/2010] via 10.100.0.1, 00:01:29, Tunnel0 C 10.100.0.0/24 is directly connected, Tunnel0 O 10.100.0.1/32 [110/1000] via 10.100.0.1, 00:01:29, Tunnel0 L 10.100.0.19/32 is directly connected, Tunnel0 O % 10.100.0.20/32 [110/2000] via 10.100.0.1, 00:01:29, Tunnel0 O 10.100.0.21/32 [110/2000] via 10.100.0.1, 00:01:29, Tunnel0 C 10.255.1.19/32 is directly connected, Loopback0 O 10.255.1.20/32 [110/2001] via 10.100.0.1, 00:01:29, Tunnel0 O 10.255.1.21/32 [110/2001] via 10.100.0.1, 00:01:29, Tunnel0 R19# The reason we can se from debug : R19# *Apr 20 15:30:11.199: NHRP: Attempting to create instance PDB for (0x0) *Apr 20 15:30:11.211: NHRP: Adding route entry for 10.16.2.0/24 (Tunnel0) to RIB *Apr 20 15:30:11.211: NHRP: Route addition failed (admin-distance) *Apr 20 15:30:11.211: NHRP: nexthop-override added to RIB *Apr 20 15:30:11.211: NHRP: Route watch started for 10.16.2.0/24 *Apr 20 15:30:11.211: NHRP: Adding route entry for 10.100.0.20/32 (Tunnel0) to RIB *Apr 20 15:30:11.211: NHRP: Route addition failed (admin-distance) *Apr 20 15:30:11.211: NHRP: nexthop-override added to RIB *Apr 20 15:30:11.211: NHRP: Route watch started for 10.100.0.20/32 *Apr 20 15:30:11.215: NHRP: R19#Received route watch notification for 10.16.2.0/24 *Apr 20 15:30:11.215: NHRP: Covering prefix is 10.16.2.0/24 *Apr 20 15:30:11.215: NHRP: Received route watch notification for 10.100.0.20/32 *Apr 20 15:30:11.215: NHRP: Covering prefix is 10.100.0.20/32 R19# And finally the question : What your thoughts guys ? "by the nature of it works" it definitely has all components of Phase 3 in place. Except of the fact that no nhrp routes are actually in the routing tables. Would it be considered by cisco as valid phase 3 ? As usual - any ideas are highly appreciated.
  7. Hello, does anybody has a clue why I do not see the full path at the traceroute output. It always stucks at the border routers between R9/R53 or R10/R54 where we have to merge those two networks by doing mutual redistribution of the IGPs and extending the MPLS core. R101#ping 172.17.1.254 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.17.1.254, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms R101#traceroute 172.17.1.254 Type escape sequence to abort. Tracing the route to 172.17.1.254 VRF info: (vrf in name/id, vrf out name/id) 1 10.2.1.253 0 msec 1 msec 0 msec 2 10.2.0.5 1 msec 1 msec 1 msec 3 10.254.0.73 1 msec 1 msec 1 msec 4 10.254.0.13 [MPLS: Label 33 Exp 0] 1 msec 2 msec 1 msec 5 10.254.0.18 [MPLS: Label 26 Exp 0] 1 msec 1 msec 2 msec 6 * * * 7 172.17.253.3 1 msec 1 msec 2 msec 8 172.17.253.21 1 msec 1 msec 1 msec 9 172.17.254.254 2 msec * 6 msec R101# Thanks for your help!
  8. Hello folks, I just read through the task of H2 and came to following conclusion: At the first place you configure all IGPs for Jamesons and Jacobs sites. The next phase is the pre-merge one were we should configure IPv4 eBGP peerings between the ASes in each site for Jameson and Jacobs. Merge phase 1 is the one where the backbone router are placed in each site and where we configure an eBGP peering between Jameson DataCenter and Jacobs HQ Merge phase 2 IGP merge (mutual redistribution of EIGRP and OSPF) till now everything is clear, but for MBGP I lost somehow the track because I got confused about this "merging" approach: For now we had configured IPv4 BGP peerings and beginning with section 3 we have to remove them and place the downlinks at the PEs to the CE router into VRF and build up a VPNv4 BGP peering with an MPLS core which is extendet from Jamesons core network to Jacobs core network. What do you think is this the correct approach or am I missing something ? Thanks for feedback
  9. UNL H2 Thanks to @smallbrother and of course UD. We dont have answers yet, but we should be able to get them. [Hidden Content]
  10. [hide][Hidden Content]] Key- !_VHezg_B0JJh9j97-maMOGdUy9PGS6jPbJkFlCUNtfE Happy Labbing !! :-)
  11. ablongo

    H2 Section 2.6

    Hi All, 2.6 Merge phase 1: BGP Refer to the “Overall Scenario” and “Diagram 5: Merge Phase: 1” Jameson’s and Jacob’s started the first phase of their merge and add a new border router in their respective main site (R18 and R57). Configure the network as per the following requirements: * Interface Lo0 of both R18 and R57 must be add into their respective IGP domain. * Interface Eth0/1 of both R18 and R57 must peer with its connected IGP neighbor. * Both R18 and R57 must advertise a summary prefix via eBGP to each other as follows: R18 advertises 10.0.0.0/8 R57 advertises 172.0.0.0/8 * Both R18 and R57 must propagate the received summary prefix into their respective IGP domain. See my resolution: Obs: Aggregation applies to routes that exist in the BGP routing table. This is in contrast to the network command, which applies to the routes that exists in IP routing table. Aggregation can be performed if at least one or more of the specific routes of the aggregate address exists in the BGP routing table. ## Router R57 - Jacobs ! router eigrp 10 network 172.18.2.1 0.0.0.0 network 172.30.1.57 0.0.0.0 redistribute bgp 65005 metric 10000 10 255 1 1500 route-map Blk_Summ_Netw_172 eigrp router-id 172.30.1.57 ! router bgp 65005 bgp router-id 172.30.1.57 bgp log-neighbor-changes network 172.18.2.0 mask 255.255.255.0 aggregate-address 172.0.0.0 255.0.0.0 summary-only neighbor 10.2.0.45 remote-as 65002 neighbor 10.2.0.45 next-hop-self ! ! ip prefix-list Pfl_Summ_Netw_172 seq 5 permit 172.0.0.0/8 ! route-map Blk_Summ_Netw_172 deny 10 match ip address prefix-list Pfl_Summ_Netw_172 ! route-map Blk_Summ_Netw_172 permit 20 ! ## Router R18 - Jamesons ! router ospf 1 router-id 10.255.1.18 redistribute bgp 65002 subnets route-map Blk_Summ_Netw_10 network 10.2.0.42 0.0.0.0 area 0 network 10.255.1.18 0.0.0.0 area 0 ! router bgp 65002 bgp router-id 10.255.1.18 bgp log-neighbor-changes network 10.2.0.40 mask 255.255.255.252 aggregate-address 10.0.0.0 255.0.0.0 summary-only neighbor 10.2.0.46 remote-as 65005 neighbor 10.2.0.46 next-hop-self ! ip prefix-list Pfl__Summ_Netw_10 seq 5 permit 10.0.0.0/8 ! route-map Blk_Summ_Netw_10 deny 10 match ip address prefix-list Pfl__Summ_Netw_10 ! route-map Blk_Summ_Netw_10 permit 20 !
  12. ablongo

    H2 Section 2.3

    Hi All, I would to like to share with you my disagree with the section 2.3, item TAG 172.172.172.172 resolution that i saw. ITEM - All EIGRP core router R50, R51 and R52 must add the administrative tag “172.172.172.172” to all prefixes that they inject into EIGRP. Ensure that operators can filter routers by using tag wildcard mask My understand is that R50,R51 and R52 should take any route learned (redistributed) from EXTERNAL ways,like, from STATIC, CONNECTED, IGPs, EGPs and set the TAG. So, INJECT INTO, i understand as EXTERNAL ROUTES learned by a redistributed process. On R52, The only EXTERNAL route that should be INJECTED (REDISTRIBUTED) is the connected Loop52 interface. I saw two resolutions using DISTRIBUTE-LIST, but i really think that the correct answer should use route-map with set TAG on the redistribution line command only. My justification is based on this part of the statement "R50, R51 and R52 must add the administrative tag “172.172.172.172” to all prefixes that they inject into EIGRP" So, i understand that R52 (looking from EIGRP perspective) should see your own route "52.52.52.52" with the TAG too. Using distribution-list only the EIGRP neighbors will see this TAG, this behavior will happen with all others (R50 and R51), so these routers will see the external routes that they injected without TAG. My Script: ! ip access-list standard ACL_Loop52 permit 52.52.52.52 ! route-map RM_Loop52 permit 10 match ip address ACL_Loop52 set tag 172.172.172.172 ! address-family ipv4 unicast autonomous-system 1 ! topology base redistribute connected route-map RM_Loop52 exit-af-topology network 172.30.1.52 0.0.0.0 network 172.30.100.3 0.0.0.0 exit-address-family ! R52(config)#do sh ip eig top 52.52.52.52/32 EIGRP-IPv4 VR(Jacobs_65006) Topology Entry for AS(1)/ID(172.30.1.52) for 52.52.52.52/32 State is Passive, Query origin flag is 1, 1 Successor(s), FD is 163840 Descriptor Blocks: 0.0.0.0, from Rconnected, Send flag is 0x0 Composite metric is (163840/0), route is External Vector metric: Minimum bandwidth is 8000000 Kbit Total delay is 1250000 picoseconds Reliability is 255/255 Load is 1/255 Minimum MTU is 1514 Hop count is 0 Originating router is 172.30.1.52 External data: AS number of route is 0 External protocol is Connected, external metric is 0 Administrator tag is 172.172.172.172 R50#sh ip eig top 52.52.52.52/32 EIGRP-IPv4 VR(Jacobs_65006) Topology Entry for AS(1)/ID(172.30.1.50) for 52.52.52.52/32 State is Passive, Query origin flag is 1, 1 Successor(s), FD is 131153920, RIB is 1024640 Descriptor Blocks: 172.30.100.3 (Ethernet0/0), from 172.30.100.3, Send flag is 0x0 Composite metric is (131153920/163840), route is External Vector metric: Minimum bandwidth is 10000 Kbit Total delay is 1001250000 picoseconds Reliability is 255/255 Load is 1/255 Minimum MTU is 1500 Hop count is 1 Originating router is 172.30.1.52 External data: AS number of route is 0 External protocol is Connected, external metric is 0 Administrator tag is 172.172.172.172 On R50 and 51, I did not see any section/item requesting redistribution, so i did not understand why they are mentioned to TAG external routers if they are not INJECTING routes in EIGRP. If we use DISTRIBUTE-LIST (IN) on them, we will TAG external routes learned from R9 and R10 too. that was not requested to do. ITEM - All EIGRP core router R50, R51 and R52 must add the administrative tag “172.172.172.172” to all prefixes THAT THEY INJECT into EIGRP. Ensure that operators can filter routers by using tag wildcard mask I do not see as an "INJECT INTO" the process of LEARN external routes from other peers. Please, share your opinion.
  13. Hi All, I bet that some of You already did, if Yes , please point to the right post or direction - how to simulate L3 switch similar as in lab exam environment? I am able to simulate routers and L2 switches using IOU on GNS3, however I can not find any way to simulate L3 switches. O know that there were some options to use IOU web interface but this is not working any more? Thanks in advance for any suggestions.
  14. Guys, alot thanks to all. Passed with old ts, old diag, and NEW CFG. I don't have new info about ts and diag, for CFG, follow my solution file. alot things was pre-configured, loop was removed with pre-configured on R55 and R56. cisco put redistribut eigrp inside bgp with route-map (permiting only 172.18/16). We need use SoO on side Jameson site, for prevent loop (necessary import own RT on PE). all details I put this file bellow, Commands wrote green, were pre-configured on Exam. Commands wrote red, we need configure. [Hidden Content] good luck guys, you need hard work, A5 is really hard.
  15. Dear All, My solution is working fine and I am getting all the expected output of each and every section. but still not sure about the routing table @ SW10-11. Please review and confirm. SW1#show ip route ospf | be Gat Gateway of last resort is 10.1.254.2 to network 0.0.0.0 O*E2 0.0.0.0/0 [110/1] via 10.1.254.2, 00:22:19, Vlan101 [110/1] via 10.1.254.1, 00:22:27, Vlan101 10.0.0.0/8 is variably subnetted, 7 subnets, 2 masks O 10.255.1.11/32 [110/2] via 10.1.254.1, 00:46:42, Vlan101 O 10.255.1.12/32 [110/2] via 10.1.254.2, 00:46:18, Vlan101 ------------------------------------------------------------------------------------------ SW2#show ip route ospf | be Ga Gateway of last resort is 10.3.254.2 to network 0.0.0.0 O*E2 0.0.0.0/0 [110/1] via 10.3.254.2, 00:18:04, Vlan101 [110/1] via 10.3.254.1, 00:18:11, Vlan101 10.0.0.0/8 is variably subnetted, 7 subnets, 2 masks O 10.255.1.13/32 [110/2] via 10.3.254.1, 00:41:20, Vlan101 O 10.255.1.14/32 [110/2] via 10.3.254.2, 00:41:07, Vlan101 SW2# ----------------------------------------------------------------------------------------- SW10#show ip route | be Ga Gateway of last resort is 172.18.254.2 to network 0.0.0.0 D*EX 0.0.0.0/0 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 10.0.0.0/8 is variably subnetted, 16 subnets, 4 masks D EX 10.0.0.0/8 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.2.0.0/16 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.2.1.0/24 [170/1075200] via 172.18.2.1, 00:39:00, Ethernet0/2 D EX 10.16.1.0/24 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.16.2.0/24 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.16.3.0/24 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.100.0.0/24 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.255.1.15/32 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.255.1.16/32 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.255.1.17/32 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.255.1.18/32 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.255.1.19/32 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.255.1.20/32 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.255.1.21/32 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.255.1.103/32 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 10.255.1.104/32 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 D EX 172.0.0.0/8 [170/568320] via 172.18.254.2, 00:30:13, Vlan101 [170/568320] via 172.18.254.1, 00:30:13, Vlan101 172.18.0.0/16 is variably subnetted, 7 subnets, 3 masks D EX 172.18.0.0/16 [170/568320] via 172.18.254.2, 00:31:52, Vlan101 C 172.18.1.0/24 is directly connected, Vlan100 L 172.18.1.254/32 is directly connected, Vlan100 C 172.18.2.0/24 is directly connected, Ethernet0/2 L 172.18.2.254/32 is directly connected, Ethernet0/2 C 172.18.254.0/24 is directly connected, Vlan101 L 172.18.254.254/32 is directly connected, Vlan101 172.30.0.0/32 is subnetted, 4 subnets D 172.30.1.55 [90/10880] via 172.18.254.1, 00:43:18, Vlan101 D 172.30.1.56 [90/10880] via 172.18.254.2, 00:43:04, Vlan101 D 172.30.1.57 [90/1024640] via 172.18.2.1, 00:43:30, Ethernet0/2 C 172.30.1.110 is directly connected, Loopback0 ---------------------------------------------------------------------------------------------------- SW11#show ip route | Be Gate Gateway of last resort is 172.17.254.1 to network 0.0.0.0 D*EX 0.0.0.0/0 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 10.0.0.0/8 is variably subnetted, 15 subnets, 4 masks D EX 10.0.0.0/8 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.2.0.0/16 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.16.1.0/24 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.16.2.0/24 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.16.3.0/24 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.100.0.0/24 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.255.1.15/32 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.255.1.16/32 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.255.1.17/32 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.255.1.18/32 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.255.1.19/32 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.255.1.20/32 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.255.1.21/32 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.255.1.103/32 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 10.255.1.104/32 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 D EX 172.0.0.0/8 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 172.17.0.0/16 is variably subnetted, 4 subnets, 2 masks C 172.17.1.0/24 is directly connected, Vlan100 L 172.17.1.254/32 is directly connected, Vlan100 C 172.17.254.0/24 is directly connected, Vlan101 L 172.17.254.254/32 is directly connected, Vlan101 172.18.0.0/24 is subnetted, 1 subnets D EX 172.18.1.0 [170/258816] via 172.17.254.1, 00:30:45, Vlan101 172.30.0.0/32 is subnetted, 2 subnets D 172.30.1.58 [90/2848] via 172.17.254.1, 00:42:54, Vlan101 C 172.30.1.111 is directly connected, Loopback0
  16. Hi Guys, In A5/H2 sec 2.4, I see solutions with R1 reflecting routes to all core routers except R2, R9, R10. I understand its not reflected to R2 as its asked in question. but why we r not reflecting routes to R9 and R10 is it a mistake or am i missing something. Thank you
  17. Dear All, Here is one of the requirements in H2 version Inter‐VPN Routing Refer to the “Overall Scenario” and “Diagram 6: Merge Phase 2”. Configure the network as per the following requirements: Jameson’s headquarters (VPN RED), main office (VPN GREEN) and Jacob’ office (VPN BLUE) must receive datacenter prefixes (VPN GREEN). Jameson’s main office (VPN GREEN) may not receive headquarters (VPN RED) prefixes nor Jacob’s headquarters (VPN GREEN) prefixes. In order to simplify future changes, your solution may not be limited to specific prefixes. To me, this requirements is asking that all sites should pass through Jameson Datacenter as it is the only site with full reachability to other sites. Ping works fine for all sites, Jamesons HQ to Jamesons Main office Jamesons HQ to Jamesons DC Jamesons HQ to Jacobs HQ Jamesons HQ to Jacobs office Similary, we can test with Jamesons Main office to other sites and Jacobs HQ, to other. But there is problem while connecting Jacobs HQ to Jacob office. R3 (other also have similar configuration) ip vrf GREEN rd 65002:3 route-target export 65002:3 route-target import 65002:5 route-target import 65002:6 route-target import 65002:7 route-target import 65002:8 route-target import 65005:50 route-target import 65005:51 route-target import 65007:52 R55#ping 10.1.1.254 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.1.1.254, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms R55#ping 10.2.1.104 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.1.104, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms R55#ping 10.3.1.254 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.3.1.254, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms R55#ping 172.17.254.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.17.254.1, timeout is 2 seconds: U.U.U Success rate is 0 percent (0/5) The routing table at R55 shows R55#show ip route Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, + - replicated route Gateway of last resort is 172.18.253.1 to network 0.0.0.0 B* 0.0.0.0/0 [20/0] via 172.18.253.1, 00:06:49 10.0.0.0/8 is variably subnetted, 19 subnets, 4 masks D EX 10.0.0.0/8 [170/563200] via 172.18.254.254, 00:01:34, Ethernet0/0 B 10.2.0.0/16 [20/0] via 172.18.253.1, 00:06:49 D EX 10.2.1.0/24 [170/563200] via 172.18.254.254, 00:01:34, Ethernet0/0 B 10.16.1.0/24 [20/0] via 172.18.253.1, 00:06:49 B 10.16.2.0/24 [20/0] via 172.18.253.1, 00:06:49 B 10.16.3.0/24 [20/0] via 172.18.253.1, 00:06:49 B 10.100.0.1/32 [20/0] via 172.18.253.1, 00:06:49 B 10.100.0.19/32 [20/0] via 172.18.253.1, 00:06:49 B 10.100.0.20/32 [20/0] via 172.18.253.1, 00:06:49 B 10.100.0.21/32 [20/0] via 172.18.253.1, 00:06:49 B 10.255.1.15/32 [20/0] via 172.18.253.1, 00:06:49 B 10.255.1.16/32 [20/0] via 172.18.253.1, 00:06:50 B 10.255.1.17/32 [20/0] via 172.18.253.1, 00:06:50 B 10.255.1.18/32 [20/0] via 172.18.253.1, 00:06:50 B 10.255.1.19/32 [20/0] via 172.18.253.1, 00:06:50 B 10.255.1.20/32 [20/0] via 172.18.253.1, 00:06:50 B 10.255.1.21/32 [20/0] via 172.18.253.1, 00:06:50 B 10.255.1.103/32 [20/0] via 172.18.253.1, 00:06:50 B 10.255.1.104/32 [20/0] via 172.18.253.1, 00:06:50 D EX 172.0.0.0/8 [170/563200] via 172.18.254.254, 00:01:35, Ethernet0/0 172.18.0.0/16 is variably subnetted, 7 subnets, 4 masks B 172.18.0.0/16 [200/0] via 0.0.0.0, 00:07:11, Null0 D 172.18.1.0/24 [90/281856] via 172.18.254.254, 00:08:01, Ethernet0/0 D 172.18.2.0/24 [90/307200] via 172.18.254.254, 00:08:01, Ethernet0/0 C 172.18.253.0/30 is directly connected, Ethernet0/1 L 172.18.253.2/32 is directly connected, Ethernet0/1 C 172.18.254.0/24 is directly connected, Ethernet0/0 L 172.18.254.1/32 is directly connected, Ethernet0/0 172.30.0.0/32 is subnetted, 4 subnets C 172.30.1.55 is directly connected, Loopback0 D 172.30.1.56 [90/409600] via 172.18.254.2, 00:08:05, Ethernet0/0 D 172.30.1.57 [90/435200] via 172.18.254.254, 00:01:35, Ethernet0/0 D 172.30.1.107 [90/409600] via 172.18.254.254, 00:08:01, Ethernet0/0 As you see, the aggregated route is black-holing the whole 172.0.0.0/8 which is generated by R57 and this is one of the requirements. D EX 172.0.0.0/8 [170/563200] via 172.18.254.254, 00:01:35, Ethernet0/0 Confirming black hole routes. R57# show ip route 172.0.0.0 Routing entry for 172.0.0.0/8, supernet Known via "bgp 65005", distance 200, metric 0, type locally generated Redistributing via eigrp 10 Advertised by eigrp 10 metric 100000 1000 255 1 1500 route-map tag-map Routing Descriptor Blocks: * directly connected, via Null0 Route metric is 0, traffic share count is 1 AS Hops 0 MPLS label: none So in my view we need to import export rt values between, Jacobs HQ and office site. (This will not contradict the above question requirement, but one thing I also noted is, there is no specific requirement for Jacob sites to connect with each other) R50, R51 ip vrf GREEN rd 65005:50 route-target export 65005:50 route-target import 65002:3 route-target import 65002:4 ! Changing to ip vrf GREEN rd 65001:50 route-target export 65005:50 route-target import 65002:3 route-target import 65002:4 route-target import 65007:52 ! Similar change in R52 is also made. After doing this, we get specific routes belonging to 172.17.x.x network. R55#show ip route | in R55#show ip route | include 172.17 172.17.0.0/24 is subnetted, 2 subnets B 172.17.1.0 [20/0] via 172.18.253.1, 00:01:38 B 172.17.254.0 [20/0] via 172.18.253.1, 00:01:38 R55#ping 172.17.254.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.17.254.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms If any one has other solution please need your help. Thanks
  18. I am trying to use local-as towards R1 from R50, R51 and R52 but I can't get the vpnv4 adjacencies up. That means I do not want to do "no router bgp 65006" at JACOBS core but I want to use the existing AS 65006. I can ping all the Lo0's. Anyone sees anything wrong from the output? I am not sure why the vpnv4 neighbor are not coming up. Thanks R1# show run | s bgp router bgp 65001 bgp router-id 10.255.1.1 bgp log-neighbor-changes no bgp default ipv4-unicast neighbor IBGP peer-group neighbor IBGP remote-as 65001 neighbor IBGP update-source Loopback0 neighbor 10.255.1.3 peer-group IBGP neighbor 10.255.1.4 peer-group IBGP neighbor 10.255.1.5 peer-group IBGP neighbor 10.255.1.6 peer-group IBGP neighbor 10.255.1.7 peer-group IBGP neighbor 10.255.1.8 peer-group IBGP neighbor 172.30.1.50 peer-group IBGP neighbor 172.30.1.51 peer-group IBGP neighbor 172.30.1.52 peer-group IBGP ! address-family ipv4 neighbor IBGP route-reflector-client neighbor 10.255.1.3 activate neighbor 10.255.1.4 activate neighbor 10.255.1.5 activate neighbor 10.255.1.6 activate neighbor 10.255.1.7 activate neighbor 10.255.1.8 activate exit-address-family ! address-family vpnv4 neighbor IBGP send-community extended neighbor IBGP route-reflector-client neighbor 10.255.1.3 activate neighbor 10.255.1.4 activate neighbor 10.255.1.5 activate neighbor 10.255.1.6 activate neighbor 10.255.1.7 activate neighbor 10.255.1.8 activate neighbor 172.30.1.50 activate neighbor 172.30.1.51 activate neighbor 172.30.1.52 activate exit-address-family R1# R1#ping 172.30.1.50 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.30.1.50, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms R1# R1#ping 172.30.1.51 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.30.1.51, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms R1# R1#ping 172.30.1.52 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.30.1.52, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms R1#show bgp vpnv4 unicast all summary Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 172.30.1.50 4 65001 0 0 1 0 0 01:19:05 Idle 172.30.1.51 4 65001 0 0 1 0 0 never Idle 172.30.1.52 4 65001 0 0 1 0 0 never Idle R1# R50# show run | s bgp router bgp 65006 bgp router-id 172.30.1.50 bgp log-neighbor-changes no bgp default ipv4-unicast neighbor 10.255.1.1 remote-as 65001 neighbor 10.255.1.1 local-as 65001 neighbor 10.255.1.1 update-source Loopback0 neighbor 172.30.1.51 remote-as 65006 neighbor 172.30.1.51 update-source Loopback0 neighbor 172.30.1.52 remote-as 65006 neighbor 172.30.1.52 update-source Loopback0 ! address-family ipv4 neighbor 172.30.1.51 activate neighbor 172.30.1.51 next-hop-self neighbor 172.30.1.52 activate neighbor 172.30.1.52 next-hop-self exit-address-family ! address-family vpnv4 neighbor 10.255.1.1 activate neighbor 10.255.1.1 send-community extended exit-address-family ! address-family ipv4 vrf GREEN neighbor 172.18.253.2 remote-as 65005 neighbor 172.18.253.2 activate exit-address-family R50#ping 10.255.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.255.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms R50# R50# show bgp vpnv4 unicast all summary BGP router identifier 172.30.1.50, local AS number 65006 BGP table version is 1, main routing table version 1 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.255.1.1 4 65001 0 0 1 0 0 never Idle 172.18.253.2 4 65005 0 0 1 0 0 never Idle R51# show run | s bgp router bgp 65006 bgp router-id 172.30.1.51 bgp log-neighbor-changes no bgp default ipv4-unicast neighbor 10.255.1.1 remote-as 65001 neighbor 10.255.1.1 local-as 65001 neighbor 10.255.1.1 update-source Loopback0 neighbor 172.30.1.50 remote-as 65006 neighbor 172.30.1.50 update-source Loopback0 neighbor 172.30.1.52 remote-as 65006 neighbor 172.30.1.52 update-source Loopback0 ! address-family ipv4 neighbor 172.30.1.50 activate neighbor 172.30.1.50 next-hop-self neighbor 172.30.1.52 activate neighbor 172.30.1.52 next-hop-self exit-address-family ! address-family vpnv4 neighbor 10.255.1.1 activate neighbor 10.255.1.1 send-community extended exit-address-family ! address-family ipv4 vrf GREEN neighbor 172.18.253.6 remote-as 65005 neighbor 172.18.253.6 activate exit-address-family R51#ping 10.255.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.255.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms R51#show bgp vpnv4 unicast all summary BGP router identifier 172.30.1.51, local AS number 65006 BGP table version is 1, main routing table version 1 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.255.1.1 4 65001 0 0 1 0 0 never Idle 172.18.253.6 4 65005 0 0 1 0 0 never Idle R51# R52# show run | s bgp router bgp 65006 bgp router-id 172.30.1.52 bgp log-neighbor-changes no bgp default ipv4-unicast neighbor 10.255.1.1 remote-as 65001 neighbor 10.255.1.1 local-as 65001 neighbor 10.255.1.1 update-source Loopback0 neighbor 172.30.1.50 remote-as 65006 neighbor 172.30.1.50 update-source Loopback0 neighbor 172.30.1.51 remote-as 65006 neighbor 172.30.1.51 update-source Loopback0 ! address-family ipv4 neighbor 172.30.1.50 activate neighbor 172.30.1.50 next-hop-self neighbor 172.30.1.51 activate neighbor 172.30.1.51 next-hop-self exit-address-family ! address-family vpnv4 neighbor 10.255.1.1 activate neighbor 10.255.1.1 send-community extended exit-address-family ! address-family ipv4 vrf BLUE neighbor 172.18.253.21 remote-as 65005 neighbor 172.18.253.21 activate exit-address-family R52#ping 10.255.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.255.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms R52#show bgp vpnv4 unicast all summary BGP router identifier 172.30.1.52, local AS number 65006 BGP table version is 1, main routing table version 1 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.255.1.1 4 65001 0 0 1 0 0 never Idle 172.18.253.21 4 65005 0 0 1 0 0 never Active
  19. Can someone confirm whether H2 LAB has any requirement for Jacobs pre-merge requirements as Jamesons premerge. Example If we are allowed to do summary or summary only for 172.18.0.0 network. I have checked spoto and other solution no where questions mentioned about premerge config we need to do on R55,R56,R58 like aggregation or we need to allow all specific subnets
  20. Hi Guys! I'm looking for last actual unl/eve file for A5/H2. Where I can find it? Thanks.
  21. Hi Friends, I have some doubts and issues in A5 H2 topology. I have following CCIEMAN material. Please have a look and answer if you know. I need them urgent. R101 is able to get Ip from DHCP R15 but I am not able to ping anything from R101 even the default address 10.2.1.1. In R16 I am not able to see 239.1.1.1 in show ip igmp groups. I want to know if there is any issue with the VM or image in the routers or I am missing any config(apart from given in pdf by CCIEMAN) Guys please answer. I have my lab on this month end.
  22. Hi guys, I usually see INE Brian did the ping test by using tclsh and I think that's a good way to verify the connectivity in CFG Lab. Did you do the same? If yes, please share the following info for both H1 and H2. 1. When did you do ping test by using tclsh to confirm the overall connectivity? For example, after done Section 2. 2. Which did you ping? For example, the lo0 of all device. 3. Which result did you get? For example, ping was good for all routers other than the ones in MPLS backbone. Let's discuss!
  23. Got this from Internet and do not know if it is real...missing the workbook though. Hope someone can help sharing the workbook soon. [Hidden Content]
×
×
  • Create New...