Wednesday, December 29, 2010

Split Horizon, Routing update, Distance Vector, Poison Route, Periodic Update, Routing Table, metric, passive interface, auto summary

Split Horizon:

Split horizon is a method of preventing a routing loop in a network. The basic principle is simple: Information about the routing for a particular  packet is never sent back in the direction from which it was received.

Routing  Update:

A message defined by routing protocol  that lists routing information, including the subnet number, subnet mask, and metric.etc.

 

Distance Vector:

Distance Vector means that Routers are advertised as vector of distance and direction. 'Direction' is represented by next hop address and exit interface, whereas 'Distance' uses metrics such as hop count.

Routers using distance vector protocol do not have knowledge of the entire path to a destination. Instead Distance Vector uses two methods:
  1. Direction in which or interface to which a packet should be forwarded.
  2. Distance from its destination.

 

Poison Route:

A route listed in a routing update that the routing protocol purposefully assigns a metric value considered to be infinite, meaning that the route has failed.

Periodic Update:

A routing protocol behavior in which the routing protocol sends Update messages on a regular interval (the period).

 

Routing Table:

A list kept by routers that lists the best IP routes known to the router. Each entry lists a subnet or network, the associated mask, possibly the outgoing interface and/or IP address of the next-hop router, and other related info.


Metric :
A numeric value that a routing protocol uses to imply how good a particular route is, so that when a router learns more than 1 route for the same network/subnet, the router can choose the best route as the route with the lowest metric.

Passive Interface:

An interface local to a router, for which the routing protocol does not send routing protocol messages out to that interface. Different routing protocol has different view about Passive interface , in RIP  when passive interface command applied in a interface  , router will not send any update through  that interface however will receive update . in EIGRP if passive interface command applied router will not form any adjacency , because the command will not allow EIGRP hello .

 

Auto Summary:

If auto summary is enabled , router will automatically summary all routes in their class full boundaries .let say you have used a class B ip address 172.16.0.0/16 and subnet ed into many network ( 172.16.1.0/24  , 172.16.2.0/24 ) , however if auto summary is enable in your configuration ,  you will see only   one summary  route (172.16.0.0/16)  in your routing table .

Tuesday, December 28, 2010

Friday, December 24, 2010

Concise notes Load Balancing HSRP, VRRP, GLBP

Hot Standby Router Protocol (HSRP) :   Download this
provides network redundancy for IP networks, ensuring that user traffic immediately and transparently recovers from first hop failures in network edge devices or access circuits .HSRP allows multiple routers to share a virtual IP and MAC address so that the end-user hosts do not realize when a failure occurs.
 
Some of the key HSRP features are as follows:

Virtual IP address and virtual MAC active on the Master routerf

Standby routers listen for Hellos from the Active router, defaulting to a 3-second hello interval and 10-second dead interval

Highest priority ( default is 100, range 1–255) determines the Active router, with preemption disabled by default

Supports tracking, whereby a router’s priority is decreased when a tracked object (interface or route) fails

Up to 255 HSRP groups per interface, 

Virtual MAC of 0000.0C07.ACxx, where xx is the hex HSRP group

Virtual IP address must be in the same subnet as the routers’ interfaces on the same LAN

Virtual IP address must be different from any of routers’ individual interface IP addresses

Supports clear-text and MD5 authentication (through a key chain)

HSRP, VRRP, and GLBP, can  track interface states.can track based on the line protocol  or the IP routing table. 

Because HSRP uses only one Active router at a time, any other HSRP routers are idle. To provide load sharing in an HSRP configuration, the concept of Multiple HSRP, or MHSRP, was developed.In MHSRP, two or more HSRP groups are configured on each HSRP LAN interface, where the configured priority determines which router will be active for each HSRP group.

MHSRP requires that each DHCP client and statically configured host is issued a default gateway corresponding to one of the HSRP groups and requires that they’re distributed appropriately. Thus, in an MHSRP configuration with two routers and two groups, all other things being equal, half of the hosts should have one HSRP group address as its default gateway, and the other half of the hosts should use the other HSRP group address. 

HSRP is Cisco proprietary, 

Virtual Router Redundancy Protocol (VRRP) :

VRRP (RFC 3768) provides a standardized protocol to perform almost the exact same function. VRRP implementation has the same goals in mind as HSRP but with these differences:

VRRP uses a multicast virtual MAC address (0000.5E00.01xx, where xx is the hex VRRP group number).

VRRP uses the IOS object tracking feature, rather than its own internal tracking mechanism, to track interface states for failover purposes.

VRRP defaults to use pre-emption, but HSRP defaults to not use pre-emption. Both can be configured to either use pre-emption or not.

The VRRP term Master means the same thing as the HSRP term Active.
In VRRP, the VRRP group IP address is the interface IP address of one of the VRRP routers.

Gateway load balancing Protocol (GLBP) : 

is  a newer Cisco-proprietary tool that adds load-balancing features in addition to gateway redundancy features. Hosts still point to a default gateway IP address, but GLBP causes different hosts to send their traffic to one of up to four routers in a GLBP group. To do so, the GLBP Active Virtual Gateway (AVG) assigns each router in the group a unique virtual MAC address, following the format 0007.B400.xxyy, where xx is the GLBP group number, and yy is a different number for each router (01, 02, 03, or 04). When a client ARPs for the (virtual) IP address of its default gateway, the GLBP AVG replies with one of the four possible virtual MACs. By replying to ARP  requests with different virtual MACs, the hosts in that subnet will in effect balance the traffic across the routers, rather than send all traffic to the one active router.Cisco IOS devices with GLBP support permit configuring up to 1024 GLBP groups per physical interface and up to four hosts per GLBP group.


Tuesday, December 21, 2010

How to configure Cisco ROUTER as DHCP server

WHAT is a DHCP server :

DHCP : Dynamic Host Control Protocol

In a network, a DHCP server manages a pool of IP addresses, as well as default gateway details, DNS details and other information for the clients’ network configuration. When a new computer is introduced into a DHCP server-enabled network, it will send a query to the DHCP server requesting all the necessary information. When the query reaches the DHCP server, it will grant the new computer a new IP address and a lease - a time frame for which the computer can use this IP address, as well as other configuration details. The whole process takes place immediately after the new computer boots, and to be successful, it has to be completed before initiating IP based communication with other hosts in the network. 



Saturday, December 18, 2010

How to do Router ON-A-STICK

WHAT is router on-a-stick ? watch the VIDEO , you will have good understanding on topics !!!


concise Multicast notes CCNA/CCNP/CCIP/CCIE


Multicast :

What is IP Multicast :
 IP multicast is a bandwidth-conserving technology that reduces traffic by simultaneously delivering a single stream of information to potentially thousands of corporate recipients and homes. Applications that take advantage of multicast include video conferencing, corporate communications, distance learning, and distribution of software, stock quotes, and news.
IP multicast delivers application source traffic to multiple receivers without burdening the source or the receivers while using a minimum of network bandwidth. Multicast packets are replicated in the network at the point where paths diverge by Cisco routers enabled with Protocol Independent Multicast (PIM) and other supporting multicast protocols, resulting in the most efficient delivery of data to multiple receivers.

Reverse Path Forwarding (RPF)

PIM uses the unicast routing information to create a distribution tree along the reverse path from the receivers towards the source. The multicast routers then forward packets along the distribution tree from the source to the receivers. RPF is a key concept in multicast forwarding. It enables routers to correctly forward multicast traffic down the distribution tree. RPF makes use of the existing unicast routing table to determine the upstream and downstream neighbors. A router will forward a multicast packet only if it is received on the upstream interface. This RPF check helps to guarantee that the distribution tree will be loop-free.

Multicast operation :

 sparse mode :  shared tree concept . explicit join , no traffic unless you ask for it
employs rendezvous point (RP) to process join request .uses pull technology.

Dense mode : source tree concept .implicit join , all traffic unless you say you want it, uses push technology , flood and prune behavior .

Sparse-Dense : sparse for a group with an RP , dense for all other .


If sparse mode assign a RP ...

to configure Statically  RP use : ip pim rp-address  command
to dynamically assign RP use :  Auto-rp ( cisco proprietary )
                                                   bootstrap router(BSR) pim version 2 (industriy standard )


S,G  :   S  meaning source  ,G meaning group

*.G  : don’t  care about the source if there is an * meaning any source

show ip pim neighbor   command will  multicast neighbor router

shortest path tree  : DR sends uni cast to RP

shared path tree : request goes to RP and come back

multicast uses UDP port


some well-known multicast address :

224.0.0.1  all multicast systems on the subnet

224.0.0.2 all multicast router on the subnet

global multicast address range 224.0.1.0 -238.255.255.255

private range 239.0.0.0  -  239.255.255.255

IGMP internet group management protocol , client use this protocol to join
a multicast group . three version available v1, v2, v3 .

using v2 client can use leave message  to router , so router can drop the multicast flow.

using v3 client can specify by a join message to a multicast enable router which multicast stream they want to listen to meaning the source, by v2 it was not possible .


Cisco group management protocol (CGMP ) router tells to switch about multicast Mac address.

IGMP snooping : IGMP snooping allows switch to see IGMP query message , join message , leave message ,

What is multicast assert message :

with in multicast router if there is two path to a multicast source , client will use one path based on unicast routing table , when that route goes down ,the other router takes over and when the failed router come back online it will send an assert message to replace the backup router .

The assert election criteria are as follow in decreasing order of priority:

1- Administrative distance to the source S (10.10.10.1)

2- Cost of the route to S (10.10.10.1)

3- Highest multicast interface IP address.

When multiple PIM routers are connected to a LAN subnet, they send Assert messages
to determine which router will be the forwarder of the multicast traffic on the LAN.
Both PIMDM and PIM-SM routing protocols use assert messages.

A PIM-DM router sends Prune and Graft messages based on the demand for multicast
group traffic. If nobody wants the group traffic, the PIM-DM router sends a Prune
message to its upstream router. If somebody requests group traffic and the router is not
receiving the traffic from its upstream router, it sends a Graft message to its upstream router.

 DOWNLOAD this notes    Download now

Friday, December 17, 2010

How to do port forwarding DynDNS and Dynamic IP

concise MPLS notes CCNP/CCIP/CCIE



M PLS :

What is MPLS (Multi-protocol label switching ) : MPLS is a packet-forwarding technology which uses labels to make data forwarding decisions. With MPLS, the Layer 3 header analysis is done just once when the packet enters the MPLS domain. MPLS impose a label in a packet between data link layer  and network layer . label 0-15 are reserved label.

LSR : label switching router /provider router which called as P router

edge LSR / provider edge (PE) router :  which is called as PE router

Label distribution protocol (LDP)

TDP : tag distribution protocol by Cisco    uses TCP /UDP port 711 uses 224.0.0.2 all router in multicast subnet

LDP : uses TCP/UDP port 646 and 224.0.0.2


Forwarding information  base (FIb) which CEF  table    :  “show ip cef” will show you details

label information Base (LiB) “show MPLS  ldp binding” command will show details of LIB.

label forwarding information base (LFIB )  which is action table,  “ show MPLS forwarding-table” command will show forward table .

MPLS default hello interval is 5 sec and hold time is 15 second

MPLS control plane :

where L3 routing protocol exist

where label exchange protocol exist LDP/TDP

control plane take care of exchanging routing information conjunct with LDP.
LDP assigns a label to a route for its incoming and outgoing interface, for
instance network 10.0.0.0/8 gets a label 24 for incoming interface and 25 for outgoing
interface

only PE router looks routing lookup and does label removal .


MPLS Data plane /forwarding plane:

sends data based on L3 or L2 information

takes care of label swapping in other word  data plane take cares of LFIB


MPLS process :

1.router build routing table by routing protocol

2. the mpls-enabled routers assign label to each route

3. the routers advertise the route to other LSRs

4. all LSRs build their FIBs, LIBs and LFIBs table


Some Important command :

shw mpls ldp discovery details

show mpls ldp parameters

show mpls forwarding table

show mpls ldp binding

show mpls ip binding


PHP = penultimate hop popping  does not work in ATM ( a label gets remove by the P router before it sending to PE router , to reducing table lookup in PE router)

VRF = virtual routing and forwarding

MPLS VPN terms :

Route Distinguisher : (RD) keep customer routes unique with a number

Route Target (RT) : route target number can be use for import and export routes , has to be identical on PE router

.
PE /Edge LSR router keeps following information :

control plane :  routing protocol
                         ip routing table
                         label distribution protocol

Data plane     :  ip forwarding table
                         label forwarding table

in ATM VPI and VCI is used  as label , and its called cell mode MPLS

MPLS traffic engineering require OSPF or is-is routing protocol

LSP = label switch path  , LSP build by routing protocol

in MPLs VPN  route summarization should not be use , because in vpn end to end LSPs are required

the LSR assigns a label to a network connected locally and advertise the to all neighbor , saying  this is the label for my network .

MPLS is defend on IGP protocol for loop prevention although it has 8 bit TTL value , when time to leave value decrease to 0 the packet gets drop , to prevent endless loop. TTL value by default on in Cisco router.

but can be disable , the benefit is if some one does trace route it will show core LSR in trace if TTL blocked in LSR. if TTL disable , should have to disable in all Router .


MPLS  frame mode uses per platform labels , this is not secure , and causes label spoofing attack , can call it unsolicited downstream label distribution

MPLS ATM mode uses per interface labels , ATM  use downstream on demand approach

router with higher ip address initiate TCP session , loopback beats physical interface , higher is batter

uni-cast IP address also can be used to form neighbor , instead 224.0.0.2 .

How to install Gns3 in windows machine CCNA/CCNP/CCIP

Wednesday, December 15, 2010

concise BGP notes CCNP/CCIE


BGP :
BGP is a path vector routing protocol

EBGP  route  has the distance of 20

IBGP route  has the distance of 200

BGP private autonomous system range 64512-65535

TTL value is 1 by default for EBGP session
use EBGP multi hop command to increase TTL value  it will   increase  to 255 .


in EBGP loop prevention happens based on AS-path information


if IBGP neighbor learns a network from another IBGP neighbor , it can not
advertise the same   route to another IBGP  neighbor if it does not have neighbor configured , that is where route reflector  comes into play.

BGP routers only advertise best path route to their  neighbor

BGP  route based on TCP  port 179 and it does not show in routing table
that the route  learn through an interface , unlike IGP protocols
, BGP  always shows that route learned from an ip address.

in BGP  ( ? )  mark in origin code shows that route either redistributed to BGP
or route injected through BGP  inject map.



weight and local preference typically used to effect outbound traffic coming in

As-path and MED  used to manipulate to inbound traffic going out to neighbor


in BGP neighbor ship who ever having highest router id , will initiate a TCP session to port 179 to its neighbor from a random port , meaning it will act as BGP  client,
to its neighbor , and neighbor will reply from TCP port 179 to a random port to its destination, that will act as TCP server.

BGP  update are incremental , meaning if there is change it triggers an update


BGP packet type :

open :  start the session

keealive :

update :  network reach ability exchange

notification: something bad has happened close session


BGP Tables :

neighbor table : connected peers

BGP table :  all routes router know about

routing table : list of  best route


EBGP multi hop command required when peering with EBGP neighbor if neighbor not connect directly . if neighbor connected directly no need EBGP multi hop command .


Rule BGP synchronization :

A BGP speaking router do not use or advertise a EBGP route via IBGP , until there is a valid route learned for that   through IGP. 

BGP next-hop processing :

for EBGP peers :  change next hop address on advertise routes.

for IBGP peers : do not change next hop address on advertise routes



BGP split horizon :

BGP split horizon rule , if a route  receive via IBGP update from a IBGP peer
don’t send it back to other IBGP peer.


BGP neighbor relationship status:


1. idle : verifying route to neighbor

2. active : attempting connectivity to neighbor

3.open sent : open message (hello) sent to neighbor

4. open confirm : neighbor replied to open message

4.active : neighbor failed to reply or mismatched parameters

5.Establised  


BGP well know attribute :


weight

as=path

next hop address

origin

local preference

MED  :   to influence other autonomous system routing path , meaning updates are going out can be modified through MED


the difference between weight and local preference is weight locally significant
with in the router , local preference gets advertise with in Autonomous system
by a router .

Tuesday, December 14, 2010

OSPF summary notes CCNA/CCNP/CCIE

OSPF : 

OSPF  is  link state IGP protocol

OSPF uses IP  protocol  89

OSPF uses a shorted path first algorithm in order to build data path  and ... The shortest path is calculated with the use of the Dijkstra algorithm.

OSPF send trigger update if there is change in network

OSPF  send periodic update of entire routing table every 30 minute

in OSPF  all area must connect to area 0

all router in an area have the same topology table

all area must have hierarchical ip addressing design , so that summarization with in the area would be easier.

in OSPF     ABR and ASBR can only do summarization

Rule  :  OSPF router  id

all ip address configured with in interfaces in a  router  , the highest ip will elect as ospf router id. however loop back interface will beat physical interface , even loop back has a lowest ip address .if there is multiple loop back , highest loop back gets elected .OSPF router id  keep changing  if a router or process gets reboot .always better to hard code router id .

OSPF neighbor states :

OSPF down state :  if router send out a hello message  on a interface still did not hear back , this is called down state

OSPF init state :  if router receive  a hello message ( receive hello) , the router goes to init state .

OSPF 2 way state : when a router reply to hello message , router goes to 2way state .

OSPF  ex-start state : if hellos and all are agreed it comes to  master and slave selection process , where router goes to  ex-start state . the master sends DBD packet ( database description packet ) and then slaves sends its DBD back  to master .

OSPF  Loading state  :  once DBDs  received and acknowledged router goes to loading state .


OSPF  full state  : once neighbor synchronized with database router goes to full state .


hello message are send out once very 10 second in broadcast/point2point network , and every 30 second in no broadcast network

dead time is 4 times to hello timer


to form a neighbor OSPF router must match  hello and dead timer , network mask , area id and authentication .
OSPF maintains  3 table :

neighbor table :

topology table :  knows about network with in a area

routing table :


on a OSPF  broadcast segment,  OSPF  DR/BDR gets elected

 all OSPF speaking router communicate on multicast address 224.0.0.5

 DR/BDR  routers communicate on 224.0.0.6

OSPF  packet type :

hello

Database description DBD

LSR  :  link state request

LSA   : link state advertisement

LSU  : link state update

LSACK :  link state acknowledgement


OSPF network type :

broadcast multi-access


non-broadcast multi-access   default on serial interface

 point to  multipoint RFC standard  advertise /32 for each link
                                                    
 point-2-point Cisco proprietary default mode on sub interface
                                                      
  broadcast    
                                                       
 point 2 multipoint non broadcast   Cisco proprietary  static neighbor configuration required


OSPF  ABR summarization happen with “  area --- range “ command , and it creates a summary route or null 0 route in local router .

OSPF ASBR summarization happen with “ summary address”  command in OSPF process .
                                                         

OSPF LSA type :


LSA type 1 : router LSA (routing update )*****

LSA type 2 : network LSA (DR generated )

LSA type 3 : summary LSA ( ABR summary route) route from ABR

LSA type 4 : summary LSA ( ASBR location ) ip address of ASBR advertise

LSA type 5 : External LSA (ASBR summary route )

Some OSPF handy command :

show ip ospf nei

show ip ospf int

clear ip ospf process

show ip ospf database

LSA (link state advertisement )  1 --  originated by every router in an area

In  OSPF  broadcast segment hellos are send as multicast

In OSPF  non broadcast segment hellos are send as unicast

on OSPF non-broadcast network , neighbor has to be configured on
OSPF  DR router manually by neighbor command.



In general loopback interface route will be treated as host route in OSPF

if loopback need to  advertise as a network , use  ip ospf network point-to-point
command on loopback interface .

for OSPF network type point to point  hello time 10 dead time 40

for OSPF  network type multipoint hello time 30 dead time 120

point to multipoint network does not have DR/BDR election send hellos as multicast to
224.0.0.5, its change the next hop value .

inter area route is LSA 3  shows as  OIA in routing table

intra area routes are LSA 1 & 2  shows as O in routing table

                              100
OSPF cost =  -----------------------
                   Interface bandwidth in Mbps


every shared network should have DR and a BDR

DR BDR election :

Highest priority on interface is better
if it is tie then highest OSPF  router ID better 


OSPF area :

stub area :  block type 5 lsa entering into this area instead gets a default route from neighbor O*IA mark, along with inter area route, this is industry standard

totally stub area : block type 3 , 4 and 5 LSA entering to this area , this is Cisco proprietary , to enable this use 'area x no-summary’ on border router command
 router gets only a default route o*IA.

not-so-stuby area : passes external (type 5) LSA via type 7 LSA to the backbone area 0 and once it passes not so stuby area converted by ABR, the LSAs shows as type 5
                  meaning external route . router receive a O*IA default route



OSPF  does not use key chain method of authentication ,  it uses authentication on interface , support two type authentication , md5 and clear text .if we use ip OSPF authentication-key command , we are using clear text authentication.

OSPF  routes type :

E1    :  cost of route increments as it passes through the autonomous system .

E2 (default) : cost of route remain same as it passes through autonomous system this is default type for OSPF  external route

use auto-cost reference bandwidth to adjust cost as require in OSPF process .

Default-information originate ' command will send a default route to the network o*E2  mark , router should have a static route, if there is no static route use ' default-information originate always ' command to advertise a default route.





Monday, December 13, 2010

EIGRP summary notes : CCNA/CCNP/CCIE

EIGRP  :

It’s a hybrid protocol .

AS number has to match in all EIGRP router

EIGRP does not support VLSM by default , to support VLSM must use no auto-summary command

split horizon always on ,

EIGRP uses own protocol 88  and DUAL algorithm

EIGRP uses multicast address 224.0.0.10


EIGRP manual summary address command  on interface  creates a null 0 route on local router routing table , and it gives administrative distance of 5 to  summary route .

EIGRP uses administrative distance 90 for normal routes  and 170 for external routes 

EIGRP will load balance across 4 equal cost path .by default unequal load balancing is off to enable unequal load balance use variance command  with value .

EIGRP routers use query message to find backup route around the network ,

a router send query message to its neighbor for its connected network , even if it is goes down , which is unrealistic , because it is sending a query for its own network to a neighbor .

EIGRP  (SIA ) stuck in active comes into play when a router wait to hear for a query , which is for 3 minute . and neighbor get re-initiated .

EIGRP stub ,  stub router does not receive a query message from neighbor.  Stub command  mostly used in hub-and-spoke network.


when EIGRP stub command  applied in a router by default it will advertise summary and connected routes to its neighbor .

EIGRP  stub receive-only  command ,,,,,, only  receives routes from neighbor   does not send anything to its neighbor .

when a router goes down in EIGRP send a final hello message which is called good bye message ..



if we use neighbor command update are send through unicast , both neighbor have
to have neighbor command in place

if you use passive interface command  , router will not exchange hellos , hence no neighbor relationship .


if u use split horizon on hub , to get the router from spoke to spoke
use neighbor command on all router .


EIGRP maintains a topology table , if a route goes down other route comes back from topology table

EIGRP does unequal cost load balancing

EIGRP router maintains 3 table   : neighbor table ,   topology table , routing table ,


EIGRP table and terminology :

Feasible Distance  (FD) : how far a route is from  me (router)

Advertise Distance (AD) : how far a route is from my neighbor router

Successor : which goes to routing table meaning a primary path

Feasible Successor : backup route  

Rule      :   to be consider a feasible successor the advertise distance must be less
than feasible distance of the successor . its a loop prevention mechanism

eigrp active   : meaning bad route,   router is trying to find an active route by sending query

eigrp passive :  good route , everything ok




EIGRP  uses 5 packet type for peering neighbor and route exchange:

hello   : forms relationship

update : sends update to each other

query : asks  about routes

reply : response to a query

ack  : acknowledges the update, query , and reply messages .


EIGRP  metric calculation :

  by default metric based on bandwidth and delay

Bandwidth  : can be configured manually on interface

Delay     :  can be configured manually on interface

reliability :

loading :

MTU :


ip default network ---- command   flag a default route to its neighbor