2 Replies Latest reply: Apr 15, 2019 6:49 AM by Ing_Percy RSS

    Making VLANs with different prefix for each area.

    Francisco

      Hello, im starting to work with cisco packet tracer, and im making a simulation of a campus net. I was thiking on making 3 vlan, managed by a lvl 3 switch.

      My idea is to divide the IPs by campus and inside each campus with the VLANS.

       

      Example:

       

      Physics Area :

      Net 192.160.0.0/24

      Students 192.160.1.X/24

      Teachers 192.160.2.X/24

      Management 192.160.3.X/24

       

      Economics Area :

      Net 192.161.0.0/24

      Students 192.161.1.X/24

      Teachers 192.161.2.X/24

      Management 192.161.3.X/24

      ...

       

      And all the studens can communicate with the other campus.

      I was thinking on putting one level 3 switch in each area, but will be too expensive.

       

      Wich is the best way to make this, if its posible, or if this idea makes no sense.

         
        • 1. Re: Making VLANs with different prefix for each area.
          Sergey

          Francisco,

           

          If by "Net" you actually mean entire area's network, then your subnet mask for it should be wider, because 192.160.0.0/24 doesn't include 192.160.1.0/24, 192.160.2.0/24 and 192.160.3.0/24. To include all these 3 networks, you subnet mask for the summary network should be at least a /22. Also, you say you model this in packet tracer, but say the switches are too expensive In packet tracer devices are free.

          If you are trying to come up with a real life network design, then you need to start with gathering the actual requirements. It is ok to just say you will segregate teachers from students using VLANs and different IP address ranges, but what requirement does it really address? What application you are going to be running in your network is the criteria that should dictate its layout. You need to define what students will use their workstations for and what teachers are going to use them for. Then, I don't see any subnet allocated for servers. What applications are you going to have in your network? In terms of defining your IP addressing plan - that looks ok, although I would use private IP addresses instead of public ones. That's a bad practice to use public IPs in your LAN unless they are really registered to you and you are advertising them to Internet.