• ip rip triggered is an interface command to only send rip updates when there is a change. Only works on P2P links
  • passive interface in RIP only stops the router sending updates out, it’ll still receive updates in from neighbours. If you have configured a static neighbour it’ll send unicast updates even if passive-interface has been configured. i.e. if you want to limit the neighbour relationship out an interface, you can use passive-interface as well as the neighbour command
  • ip rip v2-broadcast is an interface command to allow you to broadcast RIPv2 updates out
  • Use the no validate update-source interface command if the neighbour is speaking to the router using an IP not on the local subnet (secondary address is an example)


  • k1 = bandwidth
  • k2 = load
  • k3 = delay
  • k4 = reliability
  • k5 = MTU
  • By default, only bandwidth and delay are used
  • K values need to match in EIGRP AS domain in order for neighbours to form
  • Many ways to allow EIGRP to use equal or unequal paths. Can use offset-lists to increase metric, change bandwidth/delay, add additional K values into metric, increase K multiplier and so on
  • IOS allows up to 16 paths to be used, but only 4 by default. Changed using the maximum-paths eigrp process command
  • eigrp stub receive-only tells the local router to receive eigrp routes, but don’t send anything


  • FLOOD-WAR means that 2 routers (not directly connected) share the same router-id. If they were directly connected the neighbour relationship would not form
  • Router-id’s can change depending on the lab, this is important as virtual-links and certain other filtering mechanisms are configured using the RID. If the RID changes, your configuration needs to change
  • Virtual-links are in Area 0, hence if you need to authenticate all Area 0 links, you need to authenticate the virtual-link
  • Authentication is configured on the interface, however virtual-link authentication is configured under the ospf process itself using area (x) virtual-link (x.x.x.x) (message-digest-key|authentication-key) (…)
  • If you need to configure an interface in area 0, but not allowed to use area 0 command, you can always use area – More info on this 32bit area number here:
  • Virtual links are on-demand links. Hence if you don’t do authentication on one side, you’ll not notice until packets actually needs to go down the link.
  • When router A sends router B an LSA, it includes router B’s cost to the destination. It does NOT include the local shared link. Router A will add the local link cost itself. This is the same as spanning-tree costs
  • max-lsa (options) – configured the maximum amount of non self generated lsa’s the local router can have. Can drop peer or warn when lsa amount is breached
  • ip ospf flood-reduction – stops an OSPF speaker from updating LSA’s every 30 minutes. If configured you’ll need to do it on all OSPF speakers
  • show ip ospf border-routers is a handy command to use when checking costs to border routers (perhaps for load-balancing to external destinations)
  • Watch out for strange frame-relay set ups. You may need to have frame-relay maps to certain other spokes, depending on the ospf network type
  • OSPF routes are always chosen in the order: O; O IA; E1; E2; N1; and N2 regardless of metric. You can however tell ospf to use different ADs for each of these types with the distance ospf [options] command which is handy for complex redistribution labs


  • distribute-list out on DV protocols will of course affect what DV routes go INTO another protocol
  • Use debug ip routing
  • Use tags wherever possible
  • When redistributing from OSPF into BGP, it will only redistribute internal OSPF routes by default. You need to specify the external routes if you want them redistributed
  • When reditributing through a route-map, you can specify in the route-map that certain routes will be E1 and others E2. Can also specify the metric itself

Policy-based routing:

  • ip policy route-map will be configured on the interface in which traffic is coming in on
  • ip local policy route-map is used for policy routing locally generated traffic by the router

Changing AD:

  • router (eigrp|rip|ospf)
    • distance (#) x.x.x.x x.x.x.x (ACL)
  • RIP – x.x.x.x = advertising neighbours IP address
  • EIGRP x.x.x.x = advertising neighbours router-id
  • OSPF x.x.x.x = router-id of router originating the LSA into the area
  • If you use then you’re telling the router not to care WHERE the route came from

CCIE R&S PPP notes

PPP Multilink:

  • You can configure the router to force at least 2 or more link to be up for the multilink interface to be up by using the ppp multilink links minimum (#) (mandatory)
  • The mandatory keyword will tear the link down if the minimum # of links is less than the active links, while not using mandatory will wait for the required links to bring up the interface at first, but keep the link up if the active number of interfaces goes below
  • Int sx/x
  • ppp multilink
  • ppp multilink group 1
  • int multilink 1
  • ip address x.x.x.x x.x.x.x


  • show controllers int serialx/x will show you if it’s the DCE or DTE
  • If you are the DCE, and the task states that links are 64k, ensure you set the clock rate to 64000
  • ppp authentication (type) configured on the interface, tells the current router to authenticaticate the OTHER side
  • Can use PAP (clear text), CHAP (secure) or EAP (secure)
  • EAP usually uses radius. Can tell router to use local database though using the interface command ppp eap local

CCIE R&S Frame-Relay notes


  • LMI runs between the router and the FR switch.
  • Cisco LMI is supported by other vendors
  • 3 types, but autosensed by default
  • Router gets DLCI’s via LMI. ACTIVE is good, INACTIVE means local link to FR switch is good, but a problem further on, DELETED means the switch is trying to use a DLCI which the FR switch does not have

Interface types:

1. Physical

  • May need to disable split-horizon for EIGRP/RIP
  • Will need frame maps if inverse-arp is off

2. Point-to-pont

  • Will need DLCI configured on the subinterface
  • No frame-maps needed

3. Point-to-multipoint

  • Requires frame map or frame-relay interface-dlci
  • May need to disable split-horizon for EIGRP/RIP

Back to back frame-relay:

  • Switch off LMI by issuing the no keepalive interface command
  • DLCIs must match (i.e. if using 701 on one side, need 701 on other side)
  • Can still run subinterfaces

Frame-relay multilink (FRF.16):

  • Uses mfr interface. All layer3 config, including frame-maps will be configured on the mfr interface. Can use mfr subinterfaces as well
  • Interface mfr 1
  • ip address x.x.x.x x.x.x.x
  • Tie physical interfaces into the mfr interface
  • Interface Serial0/0
  • encapsulation frame-relay mfr 1
  • show frame-relay multilink

PPP over FR:

  • Uses virtual-template. All layer3 config will be configured on the virtual-template interface.
  • PPP is needed when you need to run multiple point-to-point links over a physical interface
  • Can be used for authentication
  • Interface virtual-template 1
  • ip address x.x.x.x x.x.x.x
  • ppp authentication (x)
  • Interface Se0/0.1 point-to-point
  • frame-relay interface-dlci 101 ppp virtual-template 1
  • Interface Se0/1
  • Frame-relay interface-dlci 102 ppp virtual-template 2

End-to-end keepalives:

  • Keepalives are from local router to FR switch only, so no end to end keepalive by default
  • Can run E2E keepalive with map-class
  • Create map-class specifying EEK, then apply map-class to interface
  • map-class frame-relay EEK
  • frame-relay end-to-end keepalive mode (x)
  • Interface Se0/0
  • frame-relay class EEK
  • show frame pvc will show you if the EEK is up or not


  • frame-relay maps (xxx) (xxx) ietf – The ietf option is the industry-standard option
  • Can mix and match. So on a single interface you can use the physical interface, P2P subinterface and a P2MP subinterface at the same time
  • To bridge over frame-relay, you need the frame-relay map bridge (dlci) broadcast command, as well as the regular bridging commands
  • sh frame PVC | include ACT
  • sh frame map

CCIE R&S BGP notes


  • BGP neighbour addresses have to be in the local routing table. Following a default route will NOT work
  • Next-hop for eBGP routes will NOT follow a default route. i.e. if you have a BGP speaker advertising eBGP routes to it’s iBGP peers, those iBGP will not install that route into their rib if they don’t have a route to the next-hop. A default route doesn’t count!
  • When advertising a network in BGP via the network command, there has to be a match in the local RIB, otherwise it won’t be advertised – An Inject-map can be used to change this slightly
  • By default eBGP neighbours are expected to be directly connected. If not, or peering via loopbacks, there are 3 ways to change this behaviour
  1. ebgp multihop (ttl)
  2. disable-connected-check
  3. ttl-security hops
  • ebgp multihop will increase the ttl to whatever value you want it to be
  • disable-connected-check does not increase the ttl, but will allow routers to peer if the peer address is directly connected (like a loopback)
  • ttl-security hops will send BGP requests out with a ttl of 255, but the incoming value needs to be 255 minus the value you set


  • ip bgp-community new-format is a global config command that will show the communitys in the new x:x format
  • Communities are NOT sent to neighbours by default. You need to configure the send-community option on the nieghbour statement
  • no-export – route not sent outside AS, but will be sent to confederation peers
  • local-as – as above, but NOT advertised to confederation peers
  • no-advertise – don’t advertise to anyone
  • If you set a community via a route-map, it WILL overwrite all previous communities, unless you set the additive keyword

2 easy ways of stopping your AS becoming a transit AS:

  • Create an incoming route-map from eBGP peers that adds the no-export community
  • Create an as-path access-list matching ^$ and filter on that outbound to eBGP peers

Regular expressions:

  • show ip bgp regexp (expression) is handy to work out what your expressions will match in your current BGP table
  • ^    beginning of string
  • _    Contains (anything before or after)
  • $    End of string
  • []    Range of numbers
  • –     Used to specify range [0-9]
  • ()     Logical grouping
  • \     Special character to follow (confederations)
  • .     Single character wildcard
  • *     0 or more of the preceeding character
  • +    1 or more of the preceeding character
  • ?     0 or 1 of the preceeding character

Peer groups:

  • Peer groups are used to simplify your BGP configuration by confguring options under a group, and then assigning neighbours to a group
  • Neighbours in a single group must have the same outbound policies
  • neighbor (group name) peer-group
  • neighbor (group name) remote-as xxx
  • neighbor (group name) (options)
  • neighbor x.x.x.x peer-group (group name)


  • If you have more than 1 route-reflector in a single AS for fault-tolerence, ensure both have matching cluster-id’s BEFORE you set up the clients.
  • If set up before, reboot the route-reflector
  • If you only have a single route-reflector, it’s unnecessary to set the cluster-id


  • inter-sub-as neighbours will need ebgp multihop configured if not directly connected!
  • bgp confederation peers x x x only really needs to be configured on the confederation BGP speakers that connect to different confederation AS numbers in the same confederation. It doesn’t hurt to configure it all on all of them though
  • bgp confederation identifier (external AS) needs to be configured on all confederation BGP speakers


  • bgp dampening is a global command that enabled dampening
  • bgp dampening (half-life) (reuse) (supress) (max-suppress) [route-map](map)
  1. Half-life – Time before penalty cut in half (15min default)
  2. Reuse – Low threshold where route reused (750 default)
  3. Supress – High threshold where route supressed (2000 default)
  4. Max-supression – Max time to be supressed (60 min default)
  • The default penalty for a flap is 1000
  • These are sliding scales. i.e. if a route flaps it’ll get 1000 points, but will start losing points 1 by 1 straight away
  • If you want to ensure certain routes are NOT dampened, create a route-map that denys the routes you don’t want dampened, and allow everything else
  • When dampening though a route-map, you need to set the dampening values in the route-map itself, even if they are the defaults!


  • When reditributing from BGP into an IGP, by default no iBGP routes will be reditributed, ONLY eBGP. To ensure iBGP routes are distributed, you need to configure bgp redistribute internal under the BGP process. This can VERY easily cause loops so be careful!


  • Supress-maps are configured under the aggregate command, while unsuprsess maps are configured under the neighbour statements (check this though, supress might also be for neighbour as well)
  • When configuring an aggregate, the AS numbers of the source addresses part of that aggregate are lost. You can keep sending them as an as-set by adding the as-set command at the end of the aggregate
  • An aggregate will inherit the community values of it’s parent routes when using as-set configured above. This includes communities like no-export. You can override this with an attribute-map at the end of an aggregate command. The attribute-map calls a route-map in which you can remove the communities, or set new ones
  • Exist and non-exist maps will match routes in the BGP table, not the RIB
  • When using an inject map, the exist map MUST have both a match route term AND a match route-source term
  • You can see the effects of a filter before applying it by doing a show ip bgp filter-list (filter); show ip bgp community-list (filter) etc etc
  • An extended ACL actually acts like a prefix list in BGP. The source bits tell what IP address/range to match, while the destination bits tell what subnet mask to match. The protocol is ignored. – permit ip – matches 172.16.1.x/24 only – permit ip matches only – etc…
  • When configuring maximum prefix values to receive from a neighbour, the first variable is the amount of prefixes while the second number is the percentage to warn on, not the number received!
  • BGP timers can be configured under the bgp process, or neighbour-specific timers

CCIE R&S Multicasting notes

Sparse mode:

  • When user joins, connected router will have *,G entry, as it knows the group joined by the user, but not the source of that feed yet. This is the SHARED tree.
  • The RP WILL have an S,G entry. Once the router connects it will stay on the *,G shared tree at first, then switch over to the S,G source tree.
  • While on the shared tree, the RPF check will be towards the RP, NOT the source! This will change to the source once the router connects to the source tree
  • ip pim spt threshold controls when the router will switch from the *,G to the S,G tree. A value of infinity means it’ll NEVER switch to the S,G tree

Dense mode:

  • In dense mode you’ll always see S,G entries as the source has been flooded through the network. i.e. all PIM routers will already have the feed, and hence will know the source

Sparse-Dense mode:

  • Sparse-dense mode is mainly like sparse mode, but any group that cannot be registered with the RP becomes dense mode
  • This is good for Auto-RP, but it also means that mis-configurations on the RP could cause lots of groups to be dense mode instead of sparse mode

Rendezvous point:

All modes:

  • You need to run PIM on the interface that you are advertising as the RP. i.e if you’re running it on a loopback interface, run PIM on that loopback!
  • Auto assignments OVERRIDE static assignments! You can use ip pim rp-address (rp_address) (acl) override to override this default behaviour

Static RP:

  • Easiest to configure, pretty much like a static route
  • ip pim rp-address (rp_address) (acl)
  • (acl) determines what groups the router will be the RP for
  • The RP router ALSO needs to have the above configured. i.e the RP does not automatically know it is the RP, you need to tell the router that it is!

Auto-RP (Cisco proprietary):

  • Auto-RP is made up of 1 or more routers announcing themselves as candidate RPs using the command: ip pim send-rp-announce (acl) as well as a mapping agent using the command: ip pim send-rp-discovery
  • Only the mapping agent listens to the RP announcements
  • The MA then determines which RP to use for which groups and advertises that to all other PIM routers
  • The auto-rp process uses the and groups
  • In sparse-dense mode the 2 groups above are automatically in dense mode
  • If running sparse mode only, you need to configure ip pim auto-rp listener on transit PIM interfaces which will ensure that ONLY and are in dense mode
  • If the MA receives 2 announcements from candidate RPs for the same groups, the MA will choose the one with the highest IP address
  • The RP and MA can be the same device if needs be
  • Auto-RP IS supported by a number of Non Cisco devices. Confirm with proctor is question is not clear
  • When specifying an ACL with a RP announcement, the deny statements will create negative entries for groups. However a deny any at the end of the ACL will effectively make ALL groups negative, and hence dense mode, regardless of what’s configured. As an example:

ip pim send-rp-announce Loopback0 scope 15 group-list 12 interval 1
access-list 12 deny
access-list 12 permit
access-list 12 deny any

If you check the mapping agent you see this:

Group(s) (-)
  RP (?), v2v1
    Info source: (?), elected via Auto-RP

Once the deny statement at the end of the ACL is removed, you see this:

  RP (?), v2v1
    Info source: (?), elected via Auto-RP

Bootstrap router – BSR (Open standard)

  • BSR uses the group, but it does NOT need to be in dense mode, unlike auto-rp
  • is the link-local ALL PIM ROUTERS address as well
  • The Bootstrap router is the Mapping Agent in auto-rp, configured using: ip pim bsr-candidate (int) (hash) (pri)
  • The RP uses the same name as in auto-rp, configured using: ip pim rp-candidate (int) (ttl) (pri) (acl)
  • The hash field will allow you to load balance groups over your RPs – A hash value of 31 ensures all even groups are with on RP and odds are with another, if you have 2 RPs
  • You can see which group is mapped to which RP with show ip pim rp-hash (group)
  • BSR has priority fields so you can choose which router does what without having to rely on the high IP taking over
  • If priority is the same, then highest IP will be chosen like auto-rp
  • ip pim bsr-border will allow you to run PIM on an edge interface, but not to share bsr messages

Multicast on Frame-Relay:

  • By default, multicast traffic is process switched over frame-relay. Multicast frames also have the pak-priority set so have the highest priority
  • If you have a hub router connected to 2 spokes over the same interface, you’ll have problem with RPF checks as you are going in and out the same interface. You can also have problem where a spoke says it no longer wants to receive a feed, this would make the hun stop sending to ALL spokes.
  • ip pim nbma-mode fixes both of the above issues. When configuring nbma mode on sparse-dense and dense mode interfaces you’ll get a warning, but it’ll still work.

Multicast Boundry:

  • int# ip multicast-boundry will stop multicast packets getting through an interface.
  • Any address ALLOWED through the acl is ALLOWED through the interface
  • The boundry is bidirectional by default. If you specify the IN option it will prevent multicast control traffic coming into the interface. If you specify the OUT option it will prevent the interface from being added to the OIL

Stub Multicast:

  • Prevent routers from fully participating in PIM. Consider the diagram:

  • R2 has users on the Fa0/0 interface that want to join the multicast feed. However you do not want R2 to fully run PIM. In order to do so, you need to have R1 configured to prevent R2 from becoming a PIM neighbour. You need then to configure R2 to forward IGMP join messages to R1. Note that dense mode is configured on R2 as it needs to flood multicast traffic over to fa0/0 when it gets an igmp join.

access-list 1 deny
int s0/0
ip pim sparse-mode
ip pim neighbor-filter 1

int s0/0
ip pim dense-mode
int fa0/0
ip pim dense-mode
ip igmp helper-address

Multicast/Broadcast conversion:

  • You can convert multicast to broadcast, and from broadcast to multicast. You can also do this multiple times backwards and forwards if you need to. Consider the following example:

  • We have a server with the IP of that is sending out a udp broadcast to port 5000. For whatever reason we need that same frame to be broadcasted onto the network.
  • To convert from broadcast to multicast you configure like so:

access-list 100 permit udp host any eq 5000
ip forward-protocol udp 5000
int fa0/1
ip multicast helper-map broadcast 100

  • Then back from multicast to broadcast like so:

ip forward-protocol udp 5000
access-list 100 permit udp host any eq 5000
int fa0/0
ip multicast helper-map 100
int fa0/1
ip directed-broadcast


  • MSDP is used for inter-domain multicasting as well as to allow RPs in a single AS to share source information if running anycast RP. All you need to configure on the RPs is:

ip msdp peer (peer_unique_address) connect-source (local_unique_interface)

ip msdp originator-id (unique_address_interface)

Bidirectional PIM:

  • You need to configure ip pim bidir-enable on ALL PIM interfaces. Most RP commands will then have the bidir switch added to the end of commands.

IPv6 Multicast:

  • Sparse mode only
  • Enabled using Ipv6 multicast-routing
  • When enabled, Pim will run automatically on all ipv6 interfaces. Need to run no ipv6 pim on the interface to remove
  • Multicast listener discovery (MLD), part of ICMPv6, replaces igmp
  • Mldv1 is equivalent to IGMPv2. Same timers and so on
  • Mldv2 equivalent to IGMP3 for ssm
  • BSR and Static RP only. No auto-rp. You can also use embedded RP which encodes the RP address in the group address
  • sh ipv6 Pim range-list will show you the rp mapping
  • ipv6 mld join-group will join a group on an interface
  • IPv6 mroute is created using ipv6 route (address/prefix) (next_hop) multicast, NOT ipv6 mroute
  • Pretty much everything else is the same as ipv4


  • PIM assert will take the Administrative Distance into account first, and then metric if that AD matches. So in order to force a router to be the PIM assert router, you may need to adjust the AD
  • ip pim accept-rp (acl) will ensure the RP only accepts *,G joins for groups defined in the ACL. In theory you only need to put this on the RP, but it’s more efficient to put it on all routers so they drop the requests before it even gets to the RP
  • int#ip igmp (acl) is used to allow only joins to certain groups through an interface. This interface is pointing towards the receivers as the control packet is igmp
  • int#ip igmp limit is used to limit the amount of igmp states on an interface. Can also configure this globally
  • When configuring source specific multicast, you are required to configure ip pim ssm default or ip pim ssm (acl) on all PIM routers to ensure they do not create *,G entries. SSM does not actually need an RP as they do not connect to shared trees, only source trees.
  • On an ethernet segment a DR will be chosen between the PIM neighbours. By default, the priority is 1. If the priority is the same, the highest IP wins. This can be changed with the int#ip pim dr-priority command. Note that not all switches support this command!
  • If your IGP is load-balancing certain paths, you can load-balanse multicast as well with the ip multicast multipath command. This is essential so that your rpf checks don’t fail.