Dear sir/madam,

Scenario

You are a technician who is working at XYZ , which is one of a leading higher education institute in Sri Lanka. XYZ currently has three schools, Computing, Business in XYZ1 and Law in XYZ2 are located in two separate buildings, Both has a Local Area Network which provides all the required IT facilities to more than 1000 students and more than 100 staff members.

XYZ is planning to expand their operations in 2015 by starting a new Engineering School within the XYZ1 premises. For this new Engineering schools XYZ needs another academic staff room and two small sized computer labs with 20 computers each.

As a technician hired by XYZ, it is required to study the existing XYZ network, identify required hardware devices and write a proposal to expand the network with the above mentioned requirements.

*XYZ1 has 7 floors which are wanted to be network together. I need to know how to use RIP networking protocol in this scenario as well as how the routers and switches are being connected each other successfully to communicate with each other.

*The proposed system in 5th floor should include academic staff room and two small sized computer labs with 20 computers each.

*I want be aware how the proposed network(Engineering section) will be connected with the rest.

Please be kind enough to solve this problem as a great help. I will be grateful if you reply to me as soon as possible with a good solution.

Thank You.

Dani AI

Generated

A focused, practical plan is to treat the expansion as a small campus segment with a three‑layer logical design: access (edge switches on each floor), distribution (L3 switching / aggregation per building) and core/router (inter‑building link, Internet/firewall). Segment labs and staff into separate VLANs with their own small subnets, terminate those VLANs as SVIs on a distribution L3 switch (or router), and run RIP‑2 only between routers/distribution devices if RIP is a course requirement. asked about RIP and physical connections; and are right that drawing the logical and physical diagrams first simplifies cabling and addressing decisions.

Example addressing and VLAN approach for the 5th‑floor engineering area (two 20‑host labs + staff room):

  • VLAN 205 — LabA — 10.1.5.0/27 (30 hosts)
  • VLAN 206 — LabB — 10.1.5.32/27 (30 hosts)
  • VLAN 207 — Staff — 10.1.5.64/27 (30 hosts)
    Give each SVI the first usable address and run DHCP scoped to each VLAN. Use fiber uplinks (or GigE) from each floor access switch to the distribution switch and configure those uplinks as 802.1Q trunks carrying the lab/staff VLANs.

Minimal Cisco‑style examples (illustrative only):

interface Vlan205
 ip address 10.1.5.1 255.255.255.224
 no shutdown

interface Gig1/1
 switchport trunk encapsulation dot1q
 switchport mode trunk
 switchport trunk allowed vlan 205,206,207

RIP v2 sketch on the building router (if mandated):

router rip
 version 2
 no auto-summary
 network 10.1.0.0
 passive-interface Gig1/1   ! on interfaces that shouldn't send updates

Notes and cautions: RIP is simple but limited—max 15 hops, slow convergence and weak authentication—so for resilience or larger drops OSPF/EIGRP is preferable. Enable portfast on access ports, use SNMP/NetFlow for monitoring, and test connectivity with ping/traceroute and show ip route/show ip rip database. A quick logical diagram (VLANs, SVIs, uplinks) followed by a physical wiring sheet will make implementation and troubleshooting straightforward.

Recommended Answers

All 2 Replies

If this is an academic exercise you should solve it yourself. The process of solving hard problems is what education is all about; having others provide a simple solution (that you fail to understand) breaks that process.

If you are a professional and are directly asking others to do your work I'd suggest you resign. In a professional capacity, you risk not only your reputation but the success of your employer if you are untruthful about your abilities.

Ditto previous writer. There are vatriety of tools that can be used to shown this network.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.