Nov
30

PLEASE NOTE: This is a partial list of potential configuration options for various hypothetical sections of the lab exam. Do not allow this list to constrain your own creative thinking when it is time to solve actual lab tasks! Please suggest additions using the comments feature.

3550
Load Balancing with STP
Option 1 – STP cost – use on the downstream device
Option 2 – Port Priority – use on the upstream device

OSPF
Advertising Masks for Loopbacks in OSPF
Option 1 – OSPF network command
Option 2 – Redistribute connected – Watch for Later Redistribution Issues
Option 3 – Area Range command

Troubleshooting Neighbor Relationships in OSPF over NBMA
Option 1 – OSPF network command
Option 2 – Hello timer manipulation

Connecting Area 0s in OSPF
Option 1 – Virtual link
Option 2 – GRE Tunnel – often needed when area between is a stub area
Option 3 – Redistr between different OSPF processes on the same router

Sending Unicast Updates in OSPF
Option 1 – neighbor command and change network type/hello interval

Load Balance in OSPF – change to equal cost
Option 1 – use the bandwidth command
Option 2 – ip ospf cost command

Introducing a Network into OSFP without Updating Neighbor’s LSDB
Option 1 – no-advertise
Option 2 – area filter-list

BACKUP

PPP

PPP Multilink
Bring up second link regardless of utilization
Option 1 – dialer load-threshold 1
Option 2 – ppp multilink links minimum 2 mandatory

MULTICAST

Assigning RP in Multicast
Option 1 – Static
Option 2 – Auto-RP
Option 3 – BSR Candidates

QOS

Setting the Frame-Relay DE Bit
Option 1 – DE List
Option 2 – Set action in policy map
Option 3 – Police action

Limiting Bandwidth in QoS for a Specific Host
Option 1 – Rate-Limiting
Option 2 – Policing
Option 3 – Shaping
Option 4 – Storm Control

EIGRP
Do Not Accept Prefixes – EIGRP
Option 1 – offset-list
Option 2 – distribute-list – can reference route-maps as well
Option 3 – administrative distance
Option 4 – metric maximum-hops

RIP

Changing RIP updates to Unicast
Option 1 – Passive interface and neighbor command
Option 2 – NAT the multicast address to a unicast

Do Not Accept Prefixes – RIP
Option 1 – Distribute list
Option 2 – Offset list
Option 3 – Administrative Distance
Option 4 – Mismatch on RIP version

BGP

Device in Transit Path Not Running BGP
Option 1 – GRE Tunnel
Option 2 – Redistribute BGP into IGP

BGP Traffic Flows
Manipulate outbound traffic flows
Option 1 – weight inbound
Option 2 – Local preference inbound
Option 3 – Next-Hop IGP metric manipulation

BGP Traffic Flows
Manipulate inbound traffic flows
Option 1 – AS-path prepend outbound
Option 2 – MED outbound
Option 3 – Origin manipulation
Option 4 – Router-ID manipulation

Advertise Prefix into BGP
Option 1 – network statement
Option 2 – Aggregate address statement
Option 3 – Redistribution
Option 4 – Conditional Route Injection
Option 5 – Default Route

REACHABILITY

Basic Reachability
Option 1 – NAT
Option 2 – Aggreagate
Option 3 – Static
Option 4 – Redistribution
Option 5 – Policy Routing
Option 6 – Default Route Generation
Option 7 – Default Route
Option 8 – Route-map
Option 9 – Tunnel

REDISTRIBUTION

Route failures/feedback caused by multiple mutual redistribution points…

Option 1 – Route tagging 
Option 2 – Adjusting administrative distance
Option 3 – Distribute-list filtering
Option 4 -Adjusting metrics or metric types


You can leave a response, or trackback from your own site.

20 Responses to “R/S 3.0 Configuration Options”

 
  1. Pierre-Louis says:

    Ouah…
    What a good idea to post this update, I’m going to take the exam on Tuesday. This a good refernce to take into account.

    Good !
    Thank you.

  2. NTllect says:

    I would add about this:

    Connecting Area 0s in OSPF
    Option 3
    redistribution between different OSPF processes on the same router

    EIGRP

    Do Not Accept Prefixes – EIGRP

    >Option 2 – distribute-list – can reference route-maps as well, but set operations not allowed.
    Set operation is only allowed when referenced in re-distribution.

    Here is my test:
    Rack1R2(config-router)#do sh ip ro ei
    D 204.12.1.0/24 [90/2195456] via 183.1.23.3, 05:28:40, Serial1/1
    Rack1R2(config-router)#access-l 24 per 204.12.1.0 0.0.0.255
    Rack1R2(config)#route-map TEST
    Rack1R2(config-route-map)#match ip add 24
    Rack1R2(config-route-map)#set met 1 1 1 1 1
    Rack1R2(config-route-map)#router ei 1
    Rack1R2(config-router)#distribute-list route-map TEST in s1/1
    Rack1R2(config-router)#
    *Mar 1 05:48:47.406: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 183.1.23.3 (Serial1/1) is resync: route configuration changed
    Rack1R2(config-router)#do sh ip ro ei
    D 204.12.1.0/24 [90/2560000256] via 183.1.23.3, 00:00:20, Serial1/1

    as you can see the metric for BB3′s segment has raised due to the ‘set’ operand in route-map.

    Option 4
    Rack1R2(config-router)#metric maximum-hops ?
    Hop count

    as a measure to constrain network diameter and filter ‘remote’ networks.

    RIP

    Do Not Accept Prefixes – RIP

    Option 4
    Version mismatch, i.e. sending 2 and receiving 1 and vice-versa

    BGP

    BGP Traffic Flows
    Manipulate outbound traffic flows
    Option 3 – Next-hop’s IGP metric manipulation

    BGP Traffic Flows
    Manipulate inbound traffic flows
    Option 3 – ORIGIN manipulation
    Option 4 – Router-ID manipulation

    Device in Transit Path Not Running BGP

    Option 3 … MPLS ;)

  3. Thanks – your updates were integrated.

  4. Sesano says:

    Thanks for this.

    This is quite useful as it allows me to know whcih of the options I might be leaving out for each of the sections in my preparation.

    Please expand on this as it is a good reference guide !!

  5. Muhammad says:

    this is quite a collection….like that..

    Keep up the good work guys…

  6. Ivan says:

    Hi,
    Many thanks for the above config tips.

    From myside please add the Redistribution Rules.

    Redistribution from Lower to Higher admin distance is no problem.

    From Higher to Lower admin distance is a problem in route selection.

  7. noairbag says:

    Stuff like this should be posted on a wiki

  8. Amandeep Mann says:

    Thanks a lot,

    It would be nice to have some more throughts about why/where to select a a particular options. or illustrating these decision making in a MindMap way.

    I have a feeling that this article/thread gonna become a very valuable and popular one.

  9. Sesano says:

    Hi,

    WIll you like to add ways to fix BGP synchronization issues. A situation that arises when a transit router is not running BGP.

    3 ways to fix this (AFAIK) are;

    - Run BGP on transit
    - Create tunnels between BGP speakers
    - Redistribute BGP into IGP

  10. Hi Sesano!

    I have that one in the BGP section already called Device in Transit Path Not Running BGP.

    I do not have Run BGP on transit because typically you CANNOT do this and pass the task. Cisco does not have you run BGP there to see if you can arrive at the solution.

    Thanks so much for your contributions to our site!

  11. Sesano says:

    Thanks,

    I have one rather simple (or silly question here).

    When asked to enable logging to syslog server,

    What is the difference between the 2 command below in enabling this on a router

    - logging

    - logging host

    Also, when asked to rate limit traffic with police command in an MQC, what is the difference between the following 3 options

    - police rate

    - police cir

    - police

    Please help me clear these things in my head !

    Sesano

  12. Please direct these questions to our forum at ieoc.com. Thanks!

    Here is a great thread on the policing forms and I do not believe there is any difference on logging versus logging host.

    http://www.groupstudy.com/archives/ccielab/200508/msg01075.html

    Again, for follow up questions you might have – direct them to our forum.

    Cheers!

  13. kaushal says:

    You are superb..
    This is very useful information…….

    Thank you for your all efforts in putting this togather.

  14. ajn says:

    Hi,
    Consolidating knowledge in one organized structure is an excelent idea!
    Many thanks.

  15. [...] Cost versus Port Priority – Seems pretty simple, right?  Then I cross-referenced it with the R/S 3.0 Configuration Options - where Port Priority shows up under [...]

  16. Bhuvanesh says:

    Really wonderfull

  17. mnantel says:

    Under QOS – rate limiting a single host, you can add “storm-control unicast” as a possible (albeit unclean) way to rate limit a host on a switch.

    Rack13SW1(config-if)#storm-control unicast level ?
    Enter rising threshold
    bps Enter suppression level in bits per second
    pps Enter suppression level in packets per second

  18. arpageddon says:

    Hi,

    Route failures caused by multiple mutual redistribution points…

    1) Route tagging (doesn’t provide redundancy)
    2) Adjusting administrative distance
    3) Distribute-list filtering

  19. arpageddon says:

    Hello again,

    Thought of another for multiple redistribution.
    4) Adjusting metrics or metric types

    Of course the methods that can be used are limited based on whether the route issue is caused by admin distance or improper metrics.

 

Leave a Reply

Categories

CCIE Bloggers