IT Technology/Network III/Design Project - Revision history

Rael: /* Task */

2014-11-10T06:06:44Z

‎Task

Rael: /* Task */

2014-11-10T06:06:36Z

‎Task

Rael: /* Task */

2011-02-04T08:20:16Z

‎Task

Rael: /* Task */

2011-02-04T08:19:59Z

‎Task

Rael: /* Organizational information */

2011-01-31T19:56:18Z

‎Organizational information

Rael: /* Organizational information */

2011-01-31T19:52:30Z

‎Organizational information

Rael: /* Technical information */

2011-01-31T19:51:38Z

‎Technical information

Rael: /* Technical information */

2011-01-31T19:47:29Z

‎Technical information

Rael: /* Technical information */

2011-01-31T19:36:47Z

‎Technical information

Rael: /* Organizational information */

2011-01-31T13:44:21Z

‎Organizational information

@@ Line 21: / Line 21: @@
 ==Task==
 #Create a design document. Remember to collect the information from the company you think is required to complete the Design Document.
-<<!--#Count the number og needed AP on [[Campus_Viborg| Campus Viborg]] and find the proper WLC for the number.-->
+<!--#Count the number og needed AP on [[Campus_Viborg| Campus Viborg]] and find the proper WLC for the number.-->
 =Design Document=

@@ Line 21: / Line 21: @@
 ==Task==
 #Create a design document. Remember to collect the information from the company you think is required to complete the Design Document.
-#Count the number og needed AP on [[Campus_Viborg| Campus Viborg]] and find the proper WLC for the number.
+<<!--#Count the number og needed AP on [[Campus_Viborg| Campus Viborg]] and find the proper WLC for the number.-->
 =Design Document=

@@ Line 21: / Line 21: @@
 ==Task==
 #Create a design document. Remember to collect the information from the company you think is required to complete the Design Document.
-#Count the number og needed AP on [Campus_Viborg| Campus Viborg] and find the proper WLC for the number.
+#Count the number og needed AP on [[Campus_Viborg| Campus Viborg]] and find the proper WLC for the number.
 =Design Document=

@@ Line 20: / Line 20: @@
 ==Task==
-Create a design document. Remember to collect the information from the company you think is required to complete the Design Document.
+#Create a design document. Remember to collect the information from the company you think is required to complete the Design Document.
 =Design Document=

@@ Line 11: / Line 11: @@
 **E-Learning
 **Unified Communications
-*Wireless coverage in all public areas
+*Wireless coverage in all public indoor areas(10.000 m<sup>2</sup>)
 ==Technical information==

← Older revision		Revision as of 19:47, 31 January 2011
Line 14:		Line 14:
	Maakia uses static routing but the technical employees knows OSPF.<br>		Maakia uses static routing but the technical employees knows OSPF.<br>
	The current design is based on daisy-chained switches throughout the entire campus.		The current design is based on daisy-chained switches throughout the entire campus.
		+	==Task==
		+	Create a design document. Remember to collect the information from the company you think is required to complete the Design Document.
		+
		+	=Design Document=
		+	The design document describes the business requirements; old network architecture; network
		+	requirements; and design, plan, and configuration information for the new network. The network
		+	architects and analysts use it to document the new network changes, and it serves as
		+	documentation for the enterprise. The design document should include the following sections:
		+	* '''Introduction''' describes the project’s purpose and the reasons for the network design.
		+	* '''Design Requirements''' lists the organization’s requirements, constraints, and goals.
		+	* '''Existing Network Infrastructure''' includes logical (Layer 3) topology diagrams; physical topology diagrams; audit results; routing protocols; a summary of applications; a list of network routers, switches, and other devices; configurations; and a description of issues.
		+	* '''Design''' contains the specific design information, such as logical and physical topology, IP addressing, routing protocols, and security configurations.
		+	* '''Proof of Concept''' results from live pilot or prototype testing.
		+	* '''Implementation Plan''' includes the detailed steps for the network staff to implement the new installation and changes.
		+	* '''Appendixes''' contains additional information and configurations.

← Older revision		Revision as of 19:36, 31 January 2011
Line 13:		Line 13:
	==Technical information==		==Technical information==
	Maakia uses static routing but the technical employees knows OSPF.<br>		Maakia uses static routing but the technical employees knows OSPF.<br>
		+	The current design is based on daisy-chained switches throughout the entire campus.

← Older revision		Revision as of 13:44, 31 January 2011
Line 11:		Line 11:
	**E-Learning		**E-Learning
	**Unified Communications		**Unified Communications
		+	==Technical information==
		+	Maakia uses static routing but the technical employees knows OSPF.<br>