Difference between revisions of "Developing an optimum Design for Layer 3"

From Teknologisk videncenter
Jump to: navigation, search
m (OSPF Hierachy)
m (Designing avanceret Routning)
Line 13: Line 13:
 
For eksempel [http://www.cisco.com/en/US/products/hw/contnetw/ps792/index.html Cisco CSS 11500 Series Content Services Switch]
 
For eksempel [http://www.cisco.com/en/US/products/hw/contnetw/ps792/index.html Cisco CSS 11500 Series Content Services Switch]
 
= Designing avanceret Routning =
 
= Designing avanceret Routning =
 +
==Inappropriate Transit Traffic==
 +
{|
 +
|[[Image:ScreenShot306.jpg|800px|left|thumb|Dont do the job of your ISP]]
 +
|}
 +
 +
==Defensive filtering==
 +
{|
 +
|[[Image:ScreenShot304.jpg|800px|left|thumb|Trust no-one]]
 +
|}
 +
==Route redistribution==
 +
{|
 +
|[[Image:ScreenShot303.jpg|800px|left|thumb|Prefix-list, Route-maps or Tagging of routes]]
 +
|}
 +
==Migrating Between Routing Protocols==
 +
Two companies have been merged. Company A are running EIGRP and Company B are running OSPF.<br/>
 +
Step 1: Redistribute between A & B<br/>
 +
Step 2: Enable OSPF in comapny A, and make sure it has the highest Administrativ Distance<br/>
 +
Step 3: When OSPF is running and is fully converged, Remove EIGRP<br/>
 
== Route Summarization og Default Routing ==
 
== Route Summarization og Default Routing ==
 +
 
=Designing Scalable OSPF Design=
 
=Designing Scalable OSPF Design=
 
==OSPF  Scalability best practise==
 
==OSPF  Scalability best practise==

Revision as of 15:10, 2 September 2010

Kapitel 3 fra CCDP ARCH bogen.

Kate.png This article is under development....

At designe avancerede IP adresserings løsninger

NAT

Content Load-Balancing Device

En enhed der fordeler belastningen mellem flere Servere. For eksempel en enhed der fordeler forespørgsler fra WEB-brugere mellem ti identiske WEB-servere. Det kan være baseret på forskellige faktorer

  • Antallet af forbindelser til hver server
  • CPU belastning på Serverne
  • En kombination af flere faktorer der beskriver servernes belastning

For eksempel Cisco CSS 11500 Series Content Services Switch

Designing avanceret Routning

Inappropriate Transit Traffic

Dont do the job of your ISP

Defensive filtering

Trust no-one

Route redistribution

Prefix-list, Route-maps or Tagging of routes

Migrating Between Routing Protocols

Two companies have been merged. Company A are running EIGRP and Company B are running OSPF.
Step 1: Redistribute between A & B
Step 2: Enable OSPF in comapny A, and make sure it has the highest Administrativ Distance
Step 3: When OSPF is running and is fully converged, Remove EIGRP

Route Summarization og Default Routing

Designing Scalable OSPF Design

OSPF Scalability best practise

  • Any one Router should have no more than 60 adjacent neighbors
  • An area should have no more than 50 Routers
  • Any one Router should not be in mothe than three areas
  • Already heavily loaded Routers should not be DR and BDR

Designing Areas

Network topology and addressing should be designed initially with division of areas in mind.

General advice about OSPF design is:

  • Minimize the routing information advertised into and out of the area.
  • Experience shows that you should be conservative about adding routers to the backbone area.
  • Make it simple
  • Make nonbackbone areas stub or totally stubby areas
  • Make it summarized

OSPF Hierachy

ScreenShot302.jpg

Yada yada OMG OSPF

If hello timers are set to 1/3 second for 300 interfaces, each with 10 neighbors, the router would have to generate 900 hellos per second.
When the 3000 neighbors send 3 hellos per second back to the router, it has to process a total of 9900 hellos per second.

Det er jo ikke realistisk, Cisco tag dig sammen