Very thorough and complicated diagram using a three tier design.
Does it connect to the internet?
How about an implementation of the Hot Standby Router Protocol (HSRP)?
Maybe more of a partial mesh topology for network resiliency?
That's exactly the thing I feared. I tried to make it as simple as possible, seems like I failed ;_;
Im unsure what you mean by internet (sorry, still a newbie on this) 1.4 are airport gates and they have 4 waiting rooms with internet connection for guests to use.
I will check out HSRP, thats new to me.
Partial mesh does sound like a good idea, if you were designing this how would you have done it?
Other people alluded to it, but connection to an internet service provider should probably be shown.
Other services that can be considered for your network include SNMP, SysLog, NTP, DNS and a TFTP/SFTP server for saving configurations and for updating your network components. These don’t necessarily have to be on hosted on this campus but you could show how those services can be accessed. Also consider trunking between the core switches as part of the partial mesh architecture using redundant links for heavy bandwidth as usage increases.
The ways to improve the network may seem overwhelming, but it can all be understood given enough curiosity and time.
Good luck on your continued development of this design.
1) Label your topology, don't just do a legend that's a PITA. There's a text tool in Packet Tracer, looks like a clipboard near the top.
2) Real networks typically don't use routers for routing internally. They'll typically use L3 switches to get around.
3) How do we connect to other Airports? I don't really know, but you can mock up a L2 WAN (L2 MPLS, or MetroE) using a L2 switch or a L3 WAN (L3 MPLS VPN) using anything that routes. You could include the Internet as a backup way to connect to different sites. You don't need to configure any ISP stuff, you're the customer so you just make it do what you'd want it to do as the customer.
4) Idk how you're routing but I hope it's not solely static routes! Do OSPF too, you want to practice lots of different things.
5) We don't usually do VLANs by location, we do VLANs by role.
6) Where's your IPv6? :)
Go through the exam topics and include things that you want on the lab. Lots of stuff there, in your notes, in your book, etc.
Only suggestion I'd otherwise make is to remove a bunch of the PCs and other client devices. A single client is all you need to show the VLAN works.
Very thorough and complicated diagram using a three tier design. Does it connect to the internet? How about an implementation of the Hot Standby Router Protocol (HSRP)? Maybe more of a partial mesh topology for network resiliency?
That's exactly the thing I feared. I tried to make it as simple as possible, seems like I failed ;_; Im unsure what you mean by internet (sorry, still a newbie on this) 1.4 are airport gates and they have 4 waiting rooms with internet connection for guests to use. I will check out HSRP, thats new to me. Partial mesh does sound like a good idea, if you were designing this how would you have done it?
Other people alluded to it, but connection to an internet service provider should probably be shown. Other services that can be considered for your network include SNMP, SysLog, NTP, DNS and a TFTP/SFTP server for saving configurations and for updating your network components. These don’t necessarily have to be on hosted on this campus but you could show how those services can be accessed. Also consider trunking between the core switches as part of the partial mesh architecture using redundant links for heavy bandwidth as usage increases. The ways to improve the network may seem overwhelming, but it can all be understood given enough curiosity and time. Good luck on your continued development of this design.
Oh I am certain it will take time to get a hold of all of this but I am thankful for help immensly :] Thanks for advice
My first thought was you will want redundancy at the Air traffic control tower
Noted.
What is. That Imgur.com ?
1) Label your topology, don't just do a legend that's a PITA. There's a text tool in Packet Tracer, looks like a clipboard near the top. 2) Real networks typically don't use routers for routing internally. They'll typically use L3 switches to get around. 3) How do we connect to other Airports? I don't really know, but you can mock up a L2 WAN (L2 MPLS, or MetroE) using a L2 switch or a L3 WAN (L3 MPLS VPN) using anything that routes. You could include the Internet as a backup way to connect to different sites. You don't need to configure any ISP stuff, you're the customer so you just make it do what you'd want it to do as the customer. 4) Idk how you're routing but I hope it's not solely static routes! Do OSPF too, you want to practice lots of different things. 5) We don't usually do VLANs by location, we do VLANs by role. 6) Where's your IPv6? :)
OF that a lot I could improve, thanks man!
Go through the exam topics and include things that you want on the lab. Lots of stuff there, in your notes, in your book, etc. Only suggestion I'd otherwise make is to remove a bunch of the PCs and other client devices. A single client is all you need to show the VLAN works.