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 7 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. Primary path between 10.2.100.0/24 and 172.18.1.0/24 should go over backup R18<--->R57: SPOTO/C4C Solution is uing route-map, but in the questions is said not to use "route-map" or "access-list". router bgp 65002 bgp router-id 10.255.1.18 bgp log-neighbor-changes network 10.2.100.0 mask 255.255.255.0 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 unsuppress-map LEAK <------ route-map LEAK permit 10 match ip address prefix-list LEAK ip prefix-list LEAK seq 5 permit 10.2.100.0/24 R57: router bgp 65005 bgp router-id 172.30.1.57 bgp log-neighbor-changes network 172.18.1.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 unsuppress-map LEAK <------ route-map LEAK permit 10 match ip address prefix-list LEAK ip prefix-list LEAK seq 5 permit 172.18.1.0/24 I cannot think of something else other than unsuppress-map at the moment. Do someone remember if on the real exam it was asked not to use Route-maps?
  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. Hi all Please share the H2+ initial config if anyone has. Kind regards
  5. hi Guys, Task 2.8 asked to route traffic between 10.2.100.0/24 and 172.18.1.0/24 as primary via backdoor, and MPLS as backup. We can not use route map and access list to achieve that. One of the solution used in WB is to use prefix list with route map and use route-map in unsuppress map in aggregation. But that against rules because it uses route map. Anybody has other idea? We can also manipulate metric in redistribution, but that would set all routes to be same metric and we are asked only to routes mentioned subnets...
  6. Hi, I have applied the solution in section 2.11 multicast in cfg H2+ , completed whole lab properly just not getting output of this multicast section. Suggestions please. Solution : SW3 -Configuration ip multicast-routing interface vlan 34 ip pim sparse-mode exit interface vlan 100 ip pim sparse-mode exit interface vlan 153 ip pim sparse-mode exit interface vlan 173 ip pim sparse-mode exit SW4 -Configuration ip multicast-routing interface vlan 34 ip pim sparse-mode exit interface vlan 100 ip pim sparse-mode exit interface vlan 164 ip pim sparse-mode exit interface vlan 184 ip pim sparse-mode exit R15 -Configuration ip multicast-routing interface loopback 0 ip pim sparse-mode exit interface ethernet 0/0 ip pim sparse-mode exit interface ethernet 0/2 ip pim sparse-mode exit ip pim bsr-candidate loopback 0 ip pim rp-candidate loopback 0 R16 -Configuration ip multicast-routing interface ethernet 0/0 ip pim sparse-mode exit interface ethernet 0/2 ip pim sparse-mode exit R17 -Configuration ip multicast-routing ip multicast-routing vrf Corp interface tunnel 0 ip pim sparse-mode exit interface ethernet 0/0 ip pim sparse-mode exit interface ethernet 0/1 ip pim sparse-mode exit R18 -Configuration ip multicast-routing interface ethernet 0/1 ip pim sparse-mode exit R19 -Configuration ip multicast-routing ip multicast-routing vrf Corp interface tunnel 0 ip pim sparse-mode exit interface ethernet 0/1 ip pim sparse-mode ip igmp join-group 239.1.1.1 exit R20 -Configuration ip multicast-routing ip multicast-routing vrf Corp interface tunnel 0 ip pim sparse-mode exit interface ethernet 0/1 ip pim sparse-mode ip igmp join-group 239.1.1.1 exit   R21 -Configuration ip multicast-routing ip multicast-routing vrf Corp interface tunnel 0 ip pim sparse-mode exit interface ethernet 0/1 ip pim sparse-mode ip igmp join-group 239.1.1.1 exit
  7. This conifiguration should resolve connectivity for the variation having R17's E0/1 (To Corp) ,Lo0, and Tunnel in the VRF, but not E0/0 (To ISP). interface Ethernet0/1 vrf forwarding CORP ip address 10.2.0.38 255.255.255.252 ip nat inside ! interface Ethernet0/0 ip address 192.0.2.2 255.255.255.0 ip nat outside ! interface Loopback0 vrf forwarding CORP ip address 10.255.1.17 255.255.255.255 ip nat inside ip virtual-reassembly in ! interface Tunnel0 vrf forwarding CORP ip address 10.100.0.1 255.255.255.0 no ip redirects ip nhrp map multicast dynamic ip nhrp redirect ip ospf network point-to-multipoint ip ospf hello-interval 10 ip ospf 1 area 51 no-summary tunnel source Ethernet0/0 tunnel mode gre multipoint ! ip nat inside source list all interface Ethernet0/0 vrf CORP overload ! ip route vrf CORP 0.0.0.0 0.0.0.0 192.0.2.1 global The ip ospf 1 area 51 no-summary will cause problems if you the Spokes have their WAN and LAN interfaces in the same route table. It will send a default route that conflicts with the IPCP learned default. You can solve this by using a specific route to the NMBA interface 0/0 of R17 instead of learning a default from IPCP, or having the dialer in a separate route table from the Tunnel.
×
×
  • Create New...