Developing an optimum Design for Layer 3 - Revision history

Heth: /* OSPF Scalability best practise */

2018-05-23T16:29:23Z

‎OSPF Scalability best practise

2012-08-22T06:31:13Z

‎Role-Based addressing

2012-08-22T06:15:36Z

‎At designe avancerede IP adresserings løsninger

2011-09-06T18:51:20Z

‎Bidirectional forward detection

2011-09-06T18:40:56Z

‎Incremental SPF

2011-09-06T18:20:59Z

‎At designe avancerede IP adresserings løsninger

2011-09-06T18:20:29Z

‎At designe avancerede IP adresserings løsninger

2010-09-06T18:21:39Z

‎Migrating Between Routing Protocols

2010-09-02T15:04:09Z

‎OSPF Hierachy

2010-09-02T15:03:16Z

‎Designing Scalable BGP Designs

@@ Line 66: / Line 66: @@
 *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
+*Any one Router should not be in more 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.

@@ Line 23: / Line 23: @@
 <br/>
 <source lang=cli>
-access-list 101 pemit ip any 172.16.0.0 255.255.1.192
+access-list 101 pemit ip any 172.16.0.0 0.0.254.63
 .16.xxxxxxx0.00xxxxxx
 </source>
 Hvis access listen bliver placeret på vlan interfacet INGRESS så ville de enkelte vlans ikke kunne snakke med de andre Roler, men kun deres egne i de andre krydsfelter.
 == NAT ==
 Nat mellem private adresser anbefales ikke<br/>

@@ Line 4: / Line 4: @@
 = At designe avancerede IP adresserings løsninger =
 Design en ip adresseplan.
 == NAT ==
 Nat mellem private adresser anbefales ikke<br/>

@@ Line 71: / Line 71: @@
 |}
 ==Bidirectional forward detection==
 =Designing Scalable BGP Designs=

@@ Line 70: / Line 70: @@
 |[[Image:ScreenShot309.jpg|800px|left|thumb|SPF & iSPF comparison]]
 |}
 =Designing Scalable BGP Designs=
 '''Vis BGP slide...'''

@@ Line 3: / Line 3: @@
 __TOC__
 = At designe avancerede IP adresserings løsninger =
-Design en op adresseplan.
+Design en ip adresseplan.
 == NAT ==
-nat mellem private adresser anbefales ikke<br/>
+Nat mellem private adresser anbefales ikke<br/>
 Nat gør netværksfejlfinding mindre overskueligt.<br/>
 Nat til eksterne partnere.

@@ Line 3: / Line 3: @@
 __TOC__
 = At designe avancerede IP adresserings løsninger =
+Design en op adresseplan.
 == NAT ==
+nat mellem private adresser anbefales ikke<br/>
 === 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
@@ Line 12: / Line 14: @@
 * En kombination af flere faktorer der beskriver servernes belastning
 For eksempel [http://www.cisco.com/en/US/products/hw/contnetw/ps792/index.html Cisco CSS 11500 Series Content Services Switch]
 = Designing avanceret Routning =
 ==Inappropriate Transit Traffic==

@@ Line 30: / Line 30: @@
 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 2: Enable OSPF in company 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 ==

@@ Line 53: / Line 53: @@
 |}
-==OSPF Hierachy==
-[[Image: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.<br/>