CCDA/Network Structure models - Revision history

Heth at 04:30, 8 May 2012

2012-05-08T04:30:10Z

Heth at 10:16, 17 January 2010

2010-01-17T10:16:56Z

Heth at 10:14, 17 January 2010

2010-01-17T10:14:35Z

Heth: /* Cisco Enterprise Architecture model */

2010-01-17T10:01:17Z

‎Cisco Enterprise Architecture model

Heth: CCDA Network Structure models moved to CCDA/Network Structure models

2010-01-11T13:29:01Z

CCDA Network Structure models moved to CCDA/Network Structure models

Heth: /* Cisco Enterprise Architecture model */

2009-06-30T11:25:40Z

‎Cisco Enterprise Architecture model

Heth: /* Cisco Enterprise Architecture model */

2009-06-30T11:25:23Z

‎Cisco Enterprise Architecture model

Heth: New page: == Core layer == The core layer is the network’s high-speed switching backbone that is crucial to corporate communications. The core layer should have the following characteristics: * F...

2009-06-30T11:24:15Z

New page: == Core layer == The core layer is the network’s high-speed switching backbone that is crucial to corporate communications. The core layer should have the following characteristics: * F...

New page

== Core layer ==

The core layer is the network’s high-speed switching backbone that is crucial to corporate communications. The core layer should have the following characteristics:
* Fast transport
* High reliability
* Redundancy
* Fault tolerance
* Low latency and good manageability
* Avoidance of slow packet manipulation caused by filters or other processes
* Limited and consistent diameter
* Quality of service (QoS)

When a network uses routers, the number of router hops from edge to edge is called the diameter. As noted, it is considered good practice to design for a consistent diameter within a hierarchical network. The trip from any end station to another end station across the backbone should have the same number of hops. The distance from any end station to a server on the backbone should also be consistent.

Limiting the internetwork’s diameter provides predictable performance and ease of troubleshooting. You can add distribution layer routers and client LANs to the hierarchical model without increasing the core layer’s diameter. Use of a block implementation isolates existing end stations from most effects of network growth.

== Distribution Layer ==
The network’s distribution layer is the isolation point between the network’s access and core layers. The distribution layer can have many roles, including implementing the following functions:
* Policy (for example, ensuring that traffic sent from a particular network is forwarded out one interface while all other traffic is forwarded out another interface)
* Redundancy and load balancing
* QoS
* Security filtering
* Address or area aggregation or summarization
* Departmental or workgroup access
* Broadcast or multicast domain definition
* Routing between virtual LANs (VLAN)
* Media translations (for example, between Ethernet and Token Ring)
* Redistribution between routing domains (for example, between two different routing protocols)
* Demarcation between static and dynamic routing protocols You can use several Cisco IOS Software features to implement policy at the distribution layer:
* Filtering by source or destination address
* Filtering on input or output ports
* Hiding internal network numbers by route filtering
* Static routing
* QoS mechanisms (for example, ensuring that all devices along a path can accommodate the requested parameters)
The distribution layer provides aggregation of routes providing route summarization to the core. In the campus LANs, the distribution layer provides routing between VLANs that also apply security and QoS policies.

== Access Layer ==
The access layer provides user access to local segments on the network. The access layer is characterized by switched and shared-bandwidth LAN segments in a campus environment. Microsegmentation using LAN switches provides high bandwidth to workgroups by reducing collision domains on Ethernet segments. Some functions of the access layer include the following:
* High availability
* Port security
* Broadcast suppression
* QoS
* Rate limiting
* Address Resolution Protocol (ARP) inspection
* Virtual access control lists (VACL)
* Spanning tree
* Trust classification
* Power over Ethernet (PoE) and auxiliary VLANs for VoIP
* Auxiliary VLANs
You implement high-availability models at the access layer. The later section ''Network Availability'' covers availability models. The LAN switch in the access layer can control access to the port and limit the rate at which traffic is sent to and from the port. You can implement access by identifying the MAC address using ARP, trusting the host, and using access lists.

For small office/home office (SOHO) environments, the entire hierarchy collapses to interfaces on a single device. Remote access to the central corporate network is through traditional WAN technologies such as ISDN, Frame Relay, and leased lines. You can implement features such as dial-on-demand routing (DDR) and static routing to control costs. Remote access can include virtual private network (VPN) technology.

{|
|[[Image:Switched Hierarchical Design.png|thumb|300px|Switched Hierarchical Design]]
|[[Image:Routed Hierarchical Design.png|thumb|300px|Routed Hierarchical Design]]
|}
== Cisco Enterprise Architecture model ==
[[Image:Enterprise Architecture Model.png|800px|thumb|Enterprise Architecture Model]]

← Older revision		Revision as of 04:30, 8 May 2012
Line 1:		Line 1:
		+
		+
		+	=Materialer=
		+
		+	*[[Media:Netværksdesign_I_-_Chapter_2.pdf\|Netværksdesign kapitel 2]] (Loads PDF)
	== Core layer ==		== Core layer ==

@@ Line 75: / Line 75: @@
 === Proxy ARP ===
 Proxy arp<ref>http://www.cisco.com/application/pdf/paws/13718/5.pdf</ref> er en protokol der kan anvendes på Routere. Hvis den defaulte gateway går ned kan en anden Router svare på ARP requests selvom den har en anden IP adresse.
-== RDP - Router Discovery Protocol ==
+=== RDP - Router Discovery Protocol ===
 Ikke at forveksle med ''Remote Desktop Protocol'' er en udvidelse af ICMP protokollen og tillader en arbejdsstation at lære en Routers IP-adresse.
-== RIP ==
+=== RIP ===
 En arbejdsstation kan anvende [[RIP]] til at lære om eksterne router.
-== HSRP ==
+=== HSRP ===
 [[HSRP]]
-== GLBP ==
+=== GLBP ===
 [[GLBP]]
 = References =
 <references/>

@@ Line 57: / Line 57: @@
 |}
 == Cisco Enterprise Architecture model ==
-[[Image:Enterprise Architecture Model.png|left|800px|thumb|Enterprise Architecture Model]]
+{|
 === Internet Edge ===
 {|
@@ Line 71: / Line 73: @@
 *Redundante Router - både logiske og fysiske - mellem netværksenheder.
 == Redundans fra arbejdsstation til Router ==
-=== ARP ===
+=== Proxy ARP ===

@@ Line 58: / Line 58: @@
 == Cisco Enterprise Architecture model ==
 [[Image:Enterprise Architecture Model.png|left|800px|thumb|Enterprise Architecture Model]]
 [[Category:Network]][[Category:Cisco]][[Category:CCDA]]

@@ Line 57: / Line 57: @@
 |}
 == Cisco Enterprise Architecture model ==
-[[Image:Enterprise Architecture Model.png|800px|thumb|Enterprise Architecture Model]]
+[[Image:Enterprise Architecture Model.png|left|800px|thumb|Enterprise Architecture Model]]
 [[Category:Network]][[Category:Cisco]][[Category:CCDA]]

← Older revision	Revision as of 13:29, 11 January 2010
(No difference)

← Older revision		Revision as of 11:25, 30 June 2009
Line 58:		Line 58:
	== Cisco Enterprise Architecture model ==		== Cisco Enterprise Architecture model ==
	[[Image:Enterprise Architecture Model.png\|800px\|thumb\|Enterprise Architecture Model]]		[[Image:Enterprise Architecture Model.png\|800px\|thumb\|Enterprise Architecture Model]]
		+	[[Category:Network]][[Category:Cisco]][[Category:CCDA]]