Sim Part 2
- Submitted by: darthsolo
- Views: 252
- Category: Science
- Date Submitted: 01/16/2016 11:53 AM
- Pages: 3
- Report this Essay
Diagram Current Local Campus Network in SIM Part II
Team D
NTC/362
December 21, 2015
Professor Lawrence Master
South Dakota Campus Network Analysis
The South Dakota network is composed of a Cisco 3500 Router, a Cisco Switch that is wired to access points in each classroom. This is the information that was presented as the hardware for our problem, but I am not able to find the Cisco 3500 Router as a valid product number that exist on the internet. So I’m going to assume that the hardware is actually a Cisco 3500 managed 10/100 Mbps autosensing switch that was released around the year 2000. This is the switch that connect the access points to the router, the router, a possible typo, is a 2500 series router. It’s a router that is also from around the year 2000.
In our campus network, we have isolated the possible choke points of network slow down to be around the firewall which was not stated as part of the problem, the Router, and the single Cisco switch that connects the entire campus network. The focus of our choke points are based on the physical, data link, network, and application OSI layers. The physical layer addresses the NICs and cabling. Based on the age of the router and switch, I suspect the cabling is CAT5. The data link layer provides for the flow of data, the choke point here is express by the MAC addresses managed by switches. Next, the Network layer addresses the possibility of a choke point occurring with IP, IPX data that is managed by the router. Finally, the firewall which we assumed the campus has to have is a possible choke point in the application layer.
When viewing the problem from the TCP/IP model, it takes a familiar view of the OSI model. We look at our first choke point from a network access layer, which is our NIC’s, switches, and cabling. The internet layer choke point can be viewed from the router, and finally the application layer choke point is the firewall.
To resolve these possible chokepoints, my...
Team D
NTC/362
December 21, 2015
Professor Lawrence Master
South Dakota Campus Network Analysis
The South Dakota network is composed of a Cisco 3500 Router, a Cisco Switch that is wired to access points in each classroom. This is the information that was presented as the hardware for our problem, but I am not able to find the Cisco 3500 Router as a valid product number that exist on the internet. So I’m going to assume that the hardware is actually a Cisco 3500 managed 10/100 Mbps autosensing switch that was released around the year 2000. This is the switch that connect the access points to the router, the router, a possible typo, is a 2500 series router. It’s a router that is also from around the year 2000.
In our campus network, we have isolated the possible choke points of network slow down to be around the firewall which was not stated as part of the problem, the Router, and the single Cisco switch that connects the entire campus network. The focus of our choke points are based on the physical, data link, network, and application OSI layers. The physical layer addresses the NICs and cabling. Based on the age of the router and switch, I suspect the cabling is CAT5. The data link layer provides for the flow of data, the choke point here is express by the MAC addresses managed by switches. Next, the Network layer addresses the possibility of a choke point occurring with IP, IPX data that is managed by the router. Finally, the firewall which we assumed the campus has to have is a possible choke point in the application layer.
When viewing the problem from the TCP/IP model, it takes a familiar view of the OSI model. We look at our first choke point from a network access layer, which is our NIC’s, switches, and cabling. The internet layer choke point can be viewed from the router, and finally the application layer choke point is the firewall.
To resolve these possible chokepoints, my...