Friday, 23 July 2010

BSCI - Study Pointers - IPv6

IPv6

  • FF00::/8 = Multicast prefix for all multicast traffic
  • Link-LSA's and Intra-area LSA's are not used in OSPFv2 (Included in OSPFv3)
  • R2(config-if)#ipv6 ospf cost 50 - this cmd sets the cost of a packet on this interface
  • R2(config)#ipv6 unicast-routing - required when configuring a router for IPv4/IPv6 Dual Stack
  • In a tunnel the header will look like - | ipv4 header | ipv6 header | ipv6 data |
  • In OSPFv3 Type3 and Type9 LSA's carry all IPv6 Prefix info
  • Local-Link LSA's aree flooded through the OSPF area
  • IPv6 autoconfiguration allows a device to connect to a network without further config or the use of a DHCP server
  • Enable a IPv6-to-IPv4 tunnel using: 
          R3(config)#interface tunnel0
          R3(config-if)#tunnel mode ipv6ip
               *apply this on both ends of the tunnel

BSCI - Study Pointers - Multicast

Multicast:

Disadvantages of Multicast:
  • Lack of congestion control results in increased network degradation as the volume of network traffic rises
  • Best effort delivery - can lead to packet drops affecting VOIP/Video delivery
  • Eavesdropping is a security issue due to the nature to the protocol
Further points:

  • 224.0.1.1 = NTP protocol
  • GLOP and Limited scope addresses are types of Multicast address
  • RP-Announce msgs sent to 224.0.1.39
  • RP-Discovery msgs  (group-to-RP mapping msgs) sent to 224.0.1.40

BSCI - Study Pointers - BGP

BGP:

  • When configuring eBGP peers between peers that are not directly connected you use the - 'R2(config-router)#neighbor 192.168.10.1 ebgp-multihop [hops]' - cmd on both peers.
  • On an iBGP router that is a border router configure- 'R2(config-router)#neighbor 172.16.30.1 next-hop-self' -  to advertise the next hop as it's self to the rest of the iBGP peers
  • Send the default route information to a specific peer - 'R2(config-router)#neighbor 172.16.30.1 default-originate'
  • 3 well know mandatory BGP attributes - AS_PATH, NEXT_HOP, Origin


BSCI - Study Pointers - Route Redistribution

Route Redistribution:

  • EIGRP Summary route AD = 5
  • Passive Interfaces - Updates are not sent or received through the interface
  • The cmd R3(config-if)#ip help-address 10.2.2.2 - is applied in the inbound interface on the DFG for the host :
  • i.e  HOST -------*(R3)>>>><<<<(R4)--------DHCP Server1
  • *applied at this interface
  • DHCP Allocation Mechanisms - Automatic, Dynamic, Manual


BSCI - Study Pointers - IS-IS

IS-IS:

  • Level 3 routing - routing between separate routing domains
  • All ES's and Level1 IS's must have a unique system ID area wide
  • IS-IS is able to have more routers in an area compared to OSPF and fewer Link-State PDU's are used.
  • In Frame-Relay, the highest local DLCI is used to elect a designated IS (if all priorities are the same)
  • the cmd R1(config-if)#isis password [password] [level] -sets authentication for a specific link, when level is not specified the default is level 1
  • an INIT state can exist is there is a mis-matched authentication config or mis-matched MTU.

BSCI - Study pointers - OSPF

With my exam fast approaching this post is a simple list of points that for some I'm struggling to commit to memory.

You'll probably cast your eye of these and think 'what's the problem?' or 'D'uh!' but you're not me. And it's only easy if you know the answers.

So here they are:
OSPF:

  • When configuring a virtual link you specify the are to be traversed plus the Router I.D. of the end point.
  •  e.g. - R1(config-router)#area 5 virtual link 3.3.3.3
  •  Then on remote router: R3(config-router)#area 5 virtual-link 1.1.1.1
  • When working on a Frame-relay environment you need to enter the network type cmd under the OSPF process:
  • R2(config-router)#ip ospf network non-broadcast
  • At the interface you need to set OSPF priority to prevent DR election on the routers that will not be a DR:
  • R2(config-if)#ip ospf priority 0
  • An INIT state can exist when a router ID has not been seen in a received Hello Packet
  • A Stub area doesn't accept information from outside of the OSPF AS
  • ABR's maintain a separate link-state database for each area they are attached to.

Wednesday, 21 July 2010

BSCI -IPv6 - 6to4 tunnel addresses

When you create a 6to4 tunnel you need to apply suitable IPv6 addresses to the tunnel interfaces.

To do this you can take your IPv4 IP address which will be the source IP and convert it to an IPv6 address.

1) Using a Global address you know 2 things A) the high order bits always start 001 = 2000::/3 and generally end with 0001 in the first 16bits and B) a Global prefix is 48 bits long ( or /48). With this in mind  you know your first 16 bits, 0010 0000 0000 0001: X:X:X:X:X:X:X, so you are looking for the remaining 32 bits to form the address

2) Copy out into binary the IPv4 address of the physical interface the tunnel will be be associated with then convert it to hex, e.g.) 192.168.99.1
    1100 0000. 1010 1000. 0110 0011. 0000 0001
      c     0        a      8       6     3      0     1

3) Combine this with your first 16 bits and you have your Global IPv6 to apply to your tunnel interface
     2001:c0a8:6301::/48

Practise doing this quickly, again I've not taken the exam, but just like subnetting and Multicast MAC addresses it strikes me as an obvious exam question and an easy mark to pick up quickly leaving you time to work on the harder questions.

BSCI - Multicast - Well known Multicast IP's

Here is a useful list of multicast IP's

224.0.0.1 - All multicast systems on the subnet
224.0.0.2 - All multicast Routers on the subnet
224.0.0.4 - All Distance Vector Multicast Routing Protocol routers
224.0.0.5 - All OSPF routers
224.0.0.6 - All OSPF DR/BDR routers
224.0.0.9 - All RIPv2 routers
224.0.0.10 - All EIGRP routers
224..0.0.13 - All PIMv2 routers
224.0.1.1 - NTP time servers
224.0.1.39 - for Auto-RP rp-announce
224.0.1.40 - for Auto-RP rp-discovery

Tuesday, 20 July 2010

BSCI - Multicast - 224.0.1.40, where did that come from??

When you are configuring PIM in Sparse-Dense mode every router automatically subscribes to the Rendezvous Point Discovery group 224.0.1.40 .

This why when you do #sh run you may have entries for:
!
ip igmp join-group  224.10.50.1
ip igmp join-group  224.10.70.1
!

But when you do  - #sh ip igmp groups
You acually get listed:
Group Address
224.10.50.1
224.10.70.1
224.0.1.40

Confusion cleared!

BSCI - Multicast - Work out IP Multicast MAC addresses

You can work out what the multicast MAC address is for a given multicast IP by using the following steps.

1) First stage is to remember that all multicast MAC addresses start 01-00-5e totalling 25bits (IANA allocated 24 bits plus an extra bit set to zero so this totals 25 bits). What remains is 23 bits to use for the MAC (48bits in total).

2) Take your multicast IP and right it out in binary e.g.
- 224.10.60.3 = 1110 0000. 0 | 000 1010.0011 1100.0000 0011
                                                 23-bits to convert to a MAC

3) Now convert each group of 4 bits to Hex working from right to left
1110 0000. 0 | 000 1010.0011 1100.0000 0011
-                     0     a     3      c     0      3

4) Combine the converted Hex with the fixed multicast MAC bits:
- 01-00-5e-0a-3c-03

There you go. Relatively easy. Just remember that due to the 24 bits plus the zero bits that its best to work from right to left and you shouldn't go wrong.

I don't know, since I've not taken the exam yet, but to me this has exam question written all over it. Practice this so you can create multicast MAC addresses from a given multicast IP and you should have a mark in the bag.