Transport Network Design Assignment
Transport Network Design Assignment
Internal Verifier
Date
signature
Programme Leader
Date
signature (if required)
LO2 Implement a network using LAN design principles based on a predefined set of requirements
Pass, Merit & Distinction P3 P4 M2 M3 D1
Descripts
Resubmission Feedback:
* Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and
grades decisions have been agreed at the assessment board.
Action Plan
Summative feedback
Assessor Date
signature
1. A Cover page or title page – You should always attach a title page to your assignment. Use previous
page as your cover sheet and make sure all the details are accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using a word processing software.
4. All the assignments should be printed on A4 sized papers. Use single side printing.
5. Allow 1” for top, bottom , right margins and 1.25” for the left margin of each page.
1. The font size should be 12 point, and should be in the style of Time New Roman.
2. Use 1.5 line spacing. Left justify all paragraphs.
3. Ensure that all the headings are consistent in terms of the font size and font style.
4. Use footer function in the word processor to insert Your Name, Subject, Assignment No, and
Page Number on each page. This is useful if individual sheets become detached for any reason.
5. Use word processing application spell check and grammar check function to help editing your
assignment.
Important Points:
1. It is strictly prohibited to use textboxes to add texts in the assignments, except for the compulsory
information. eg: Figures, tables of comparison etc. Adding text boxes in the body except for the
before mentioned compulsory information will result in rejection of your work.
2. Avoid using page borders in your assignment body.
3. Carefully check the hand in date and the instructions given in the assignment. Late submissions
will not be accepted.
4. Ensure that you give yourself enough time to complete the assignment by the due date.
5. Excuses of any nature will not be accepted for failure to hand in the work on time.
6. You must take responsibility for managing your own time effectively.
7. If you are unable to hand in your assignment on time and have valid reasons such as illness, you
may apply (in writing) for an extension.
8. Failure to achieve at least PASS criteria will result in a REFERRAL grade .
9. Non-submission of work without valid reasons will lead to an automatic RE FERRAL. You will then
be asked to complete an alternative assignment.
10. If you use other people’s work or ideas in your assignment, reference them properly using
HARVARD referencing system to avoid plagiarism. You have to provide both in-text citation and
a reference list.
11. If you are proven to be guilty of plagiarism or any academic misconduct, your grade could be
reduced to A REFERRAL or at worst you could be expelled from the course
I hereby, declare that I know what plagiarism entails, namely to use another’s work and to present it as
my own without attributing the sources in the correct form. I further understand what it means to copy
another’s work.
Unit Tutor
Assignment Title
Issue Date
Submission Date
Submission format
The submission should be in the form of an individual written report. This should be written in a
concise, formal business style using single spacing and font size 12. You are required to make use
of headings, paragraphs and subsections as appropriate, and all work must be supported with
evidence. You must provide in-text citations and the reference list using Harvard referencing
system.
Learning Outcomes
LO1: Explore LAN design principles and their application in the network design process.
LO2: Implement a network using LAN design principles based on a predefined set of
requirements.
LO3: Produce an appropriate WAN solution to a set of organisational requirements.
LO4: Solve a range of network related problems using appropriate troubleshooting techniques
and methods.
Assume you are a trainee network engineer at EMC Solutions. Prepare a network
architectural design and implementation with your suggestions and
recommendations to meet the company requirements.
(Note: Clearly state your assumptions. You are allowed to design the network
according to your assumptions, but main requirements should not be violated)
Task 2
2.1. Select LAN devices based on features and requirements.
2.2. Provide IP allocation plan and design the network for EMC Solutions (including
WAN) applying basic configuration commands for the network connectivity in the
LAN.
2.3. Implement Layer 2 and Layer 3 redundancy using switch and router redundancy
protocols in your network. Analyse the redundancy implementations for IPv4 and
IPv6. *Note: - Screenshots of Configuration scripts should be presented.
Task 3
3.1. Examine various WAN technologies including different VPN types and analyze the
features, benefits and drawbacks of them. Select the appropriate WAN technology
for EMC solutions.
3.2. Configure appropriate WAN protocols for the above scenario.
*Note: - Screenshots of Configuration scripts should be presented.
In addition, a big thank you to our co-ordinator who always motivated us throughout this time
period. I also thank the ESOFT Metro Campus for the guidance and space provided.
Last but not the least I would like to thank my parents for their support and my badge mates
for their valuable comments and suggestions on my assignment which gave me an inspiration
to improve the quality of the assignment.
Sihaf
Task 1.1
Access layer
The first layer in the Cisco three-layer hierarchical architecture is the access layer. Users can
access the network through this layer. Also, this layer links user devices to the network,
including PCs, IP phones, wireless access points, printers, and scanners. For building a
dependable, scalable, and affordable internetwork, the industry has widely used the Cisco
hierarchical (three-layer) internetworking model. The access, distribution, and core layers are
discussed in this section along with their function in the hierarchical network model.
With a hierarchical network design, the network is divided into distinct layers. The exact
functions that each layer, or tier, in the hierarchy performs help to identify its place within the
larger network. This aids the network designer and architect in choosing the best hardware,
software, and features for that network layer to fulfil particular duties. The design of LANs and
WANs can both use hierarchical structures.
Distribution Layer
The second layer of the Cisco three-layer hierarchical architecture is the distribution layer. The
distribution switches are the switches connected in this layer. Distribution switches don't offer
any services to end devices, in contrast to access switches. Access switches are connected via
distribution switches.
The following are the distribution layer switches' primary responsibilities.
• Establishing communication between the switches at the access layer
• Combining links and traffic from LANs and WANs
• Providing upstream services for the access layer switches in the case of a distinct core
layer.
• Using ACLs to control and filter traffic.
• Controlling broadcast using VLANs.
• Provide load balancing and redundancy.
• Delivering routing services across several VLANs and routing domains
• Serving as a boundary between several LANs and broadcast domains
The distribution layer links the access layer to the core layer if the network has a separate core
layer.
Core layer
In summary, the three-tier hierarchical network model is recommended for EMC Solutions due
to its scalability, improved network segmentation and security, redundancy and resiliency,
To ensure high availability, ideal performance, and scalability in a network architecture, LAN
redundancy, bandwidth, and load balancing are crucial factors to take into consideration. These
problems can be solved by layer 2 and layer 3 redundancy techniques as well as link
aggregation.
LAN Redundancy
The ability to sustain network resilience requires redundancy. Redundant pathways are
provided between devices by multiple physical links. When a single connection or port fails,
the network can still function. Additionally, redundant networks help spread out the traffic load
and boost capacity. Layer loops must be prevented by managing multiple pathways. The ideal
routes are picked, and in the event that the primary connection fails, a backup path is readily
available. The management of layer redundancy uses "Spanning tree protocols." If the primary
default gateway fails, a client can utilize an alternative default gateway thanks to redundant
devices such as multilayer switches and routers. Now, a client may have several routes to
various potential default gateways.
Network availability is ensured via LAN redundancy in the event of device or link failures.
There are two standard redundancy protocols:
1. Spanning Tree Protocol – Network loops are avoided by STP by obstructing
superfluous pathways. Although it guarantees there is only one active path in the
network, it may result in less-than-ideal bandwidth usage.
2. Rapid Spanning Tree Protocol – RSTP is an improved form of STP that offers quicker
link failover and convergence.
The most possible solution for LAN redundancy for EMC Solutions can be implementing
RSTP across all switches in the network to provide fast convergence and link failover.
Spanning Tree Protocol (STP) and Rapid Spanning Tree protocol (RSTP) – In Layer 2
networks, STP and RSTP offer loop prevention and link redundancy. In order to avoid loops
and enable failover in the event of link or switch failures, they block duplicate paths. They may
produce sub-optimal bandwidth consumption and slower convergence times in bigger
networks, even though they are successful for small to medium-sized networks.
Virtual Router Redundancy Protocol (VRRP) – By supplying a virtual IP address that is shared
among a group of routers, VRRP enables router redundancy. In order to enable seamless
failover in the event of router failure, it makes sure that one router serves as the primary
Hot Standby Router Protocol (HSRP) and Gateway Load Balancing Protocol (GLBP) – Similar
to VRRP, Cisco's proprietary HSRP and GLBP protocols offer load balancing and router
redundancy. While GLBP offers load balancing across several routers using virtual MAC
addresses, HSRP supports failover to a backup router. By dispersing traffic and offering
redundancy at the router level, these technologies improve network scalability.
Open Shortest Path First (OSPF) Protocol – Dynamic routing protocols like OSPF enable load
balancing, quick convergence, and scalability. Multiple equal-cost paths are possible, allowing
for load balancing over a variety of routes and enhancing network scalability. Scalability is
provided via OSPF's hierarchical structure and regions, which divide the network into smaller
portions.
Border Gateway Protocol (BGP) – BGP is a routing protocol for outside gateways that is used
between autonomous systems. By effectively transmitting routing information and carrying out
path selection based on policies, it provides scalability and resilience in large-scale networks.
Hierarchical routing is made possible by the autonomous system (AS) structure of BGP, which
minimizes the size and complexity of routing tables.
Overall Redundancy protocols for switches and routers are crucial for enabling scalable
networks because they offer fault tolerance, load balancing, and effective resource use. These
protocols allow for network growth without sacrificing availability and efficiency. Networks
can be scaled effectively using protocols like VRRP, HSRP, GLBP, OSPF, and BGP, which
enable redundancy and load distribution among numerous devices and pathways. Scalability is
supported by dynamic routing protocols like OSPF and BGP's hierarchical structure, effective
routing table maintenance, and capacity for handling massive networks. To guarantee that these
protocols are effective in supporting scalable networks, it is crucial to appropriately design and
optimize them based on the size, complexity, and traffic patterns of the network.
In summary, dynamic routing protocols and switch and router redundancy protocols are
essential elements in creating scalable networks. They offer resource utilization that is
effective, load balancing, and redundancy, allowing networks to expand and adjust to changing
demands.
In business networks, data centres, and other settings where high bandwidth, redundancy, and
load balancing are crucial, link aggregation is frequently employed. It offers a practical and
affordable option for enhancing the performance and resilience of networks.
(Prinka, 2021)
Similar capability is offered by both LACP and PAgP, which accomplish link aggregation by
fusing many physical links into a single logical link. To construct a successful aggregation, it
is crucial to make sure that the devices on both ends of the link aggregation group support the
same protocol. While PAgP is exclusive to Cisco devices, LACP is an open standard protocol
that is widely supported by other vendors. When operating in a heterogeneous network
environment or when compatibility with non-Cisco devices is necessary, LACP is advised.
Task 02
So, we can conclude two characteristics about a LAN from its name, its locality and the fact
that its devices are networked. And that local component is what really distinguishes a LAN
from other network types like Wide Area Networks (WANs) and Metropolitan Area Networks
(MANs).
LANs are normally restricted to a single building, though this is not a strict requirement. There
could be only a few devices in that space, which could be your home or a small business. A
much larger space, such as an entire office building with hundreds or thousands of devices,
may likewise exist.
Apart from the LAN devices end devices like PCs are also used here so that it can be connected
to a LAN and communicate with other devices on the network such as servers, switches and
routers.
The requirements of each department will determine the precise type of Computers used.
Developers might need high-performance workstations with powerful CPUs, plenty of RAM,
and dedicated graphics cards, whereas customer care and sales teams might simply need entry-
level desktop or laptop computers.
(Anon., 2018)
Block size 64 32 32 16 16 8 8
Vlan id 10 20 30 40 50 60 70
Variable Length Subnet Mask (VLSM), which is used to assign IP addresses to various
corporate departments, as shown in the IP table. By allocating various subnet masks to
various subnets in accordance with the size needs of each subnet, VLSM enables more
effective utilization of IP addresses.
The company has assigned various subnet sizes to each department based on its own user
counts using VLSM. The subnet sizes are selected to support the user base and offer a
enough number of usable IP addresses.
For instance, the Developers department is given a subnet with a block size of 64, resulting
in 62 usable IP addresses, although having 55 users. The network ID of the subnet is
10.254.1.0, and the first and last usable IP addresses are 10.254.1.1 and 10.254.1.62,
respectively. This subnet's subnet mask is 255.255.255.192. Additionally, VLAN ID 10 is
linked to the Developers department.
Similar to this, VLSM is used to assign IP addresses to other departments based on the
number of users in those departments. As a result, each department has a unique subnet size,
network ID, useable IP address, subnet mask, and VLAN ID.
The blueprint
Configurations
In department switch
Layer 2 redundancy
Layer 3 redundancy
Wide area networks, or WANs, are private networks that link LANs and numerous
geographically dispersed locations together. A company's wide area network (WAN) links its
headquarters with branch offices and other locations so those remote locations can access
corporate resources and applications. A WAN may use wired or wireless connections, privately
owned or those acquired from a service provider, as well as both types of connections.
Enterprises continue to prefer wired WANs. Below are some WAN technologies and VPN
types.
ROBO – The term "remote office/branch office," or "ROBO," refers to a company location
that is not the corporate headquarters. ROBOs might perform the same functions as the main
office or offer a unique, customized service. ROBOs may be just a few kilometres from the
main office or may be located abroad. Since IT employees are typically based in main offices,
problems can be solved and data storage for ROBOs is ensured remotely, which might present
problems for either side.
Benefits of ROBO
• Organizations can better serve local markets, clients, or customers by establishing local
presences in a variety of locales thanks to ROBO.
• Organizations can cut expenditures on travel, logistics, and infrastructure by
decentralizing operations by using ROBO locations. Cost savings and better resource
allocation may result from this.
• By placing staff members closer to their workplaces, cutting down on commuting times,
and offering localized support, ROBO locations can increase productivity. Employee
efficiency and satisfaction may rise as a result.
• Better business continuity and catastrophe recovery planning may be facilitated by
ROBO sites. Other ROBO locations can carry on with business if one location
encounters an interruption or outage, minimizing downtime and guaranteeing ongoing
services.
Drawbacks of ROBO
VPN – A virtual private network is software that establishes secure connections between
authorized remote workers with a company's network and resources. VPN client software
typically uses remote access and site-to-site setups and operates on individual user devices.
Employees in branch offices initially utilized VPNs as a secure, economical way to access
company systems. VPNs are now beneficial for BYOD, mobile workers, remote workers, and
more.
Benefits of VPN
• In comparison to MPLS or dedicated leased lines, Internet VPNs are less expensive.
• They provide adaptability, scalability, and secure connectivity for branch offices and
remote users.
• VPNs are simple to set up and manage, and encryption guarantees data privacy.
Drawbacks of VPN
• Traffic on the internet and variable network circumstances might have an impact on
VPN performance.
• It can be difficult to maintain VPN infrastructure and make sure security settings are
correct.
MPLS – Multiprotocol Label Switching sometimes known as MPLS, is a routing method used
to control and amplify network traffic flows. MPLS uses labels, which carry details about a
packet's predetermined path and priority level, to transport traffic by forwarding data packets
at Layer 2 rather than Layer 3. Due to its superior performance, high level of service, and
dependability, MPLS has maintained its popularity among businesses despite its greater cost.
Additionally, MPLS works with any protocol or mode of transport, including IP and Ethernet.
Benefits of MPLS
• Low latency, minimum packet loss, and consistent and predictable performance are all
features of MPLS.
• For added security, it can be used in conjunction with encryption methods and provides
secure connectivity.
• Multipoint connectivity is supported by MPLS, enabling effective interconnection of
numerous branches.
Drawbacks of MPLS
• MPLS can be expensive, especially for businesses with numerous locations.
• For network improvements or expansions, collaboration with service providers can be
necessary.
(Anon., 2022)
Frame Relay – This is a layer 1 and layer 2 operating open system linking wide area network
(WAN) protocol. Therefore, even if high bandwidth, stability, and flexibility are achievable for
a customer compared with Leased Connections, the value can be minimized through fewer
tools, easier installation, and less complexity. Frame relays are telecom services that use packet
switching for low-cost data transport between local area networks (LAN) and wide area
networks for sporadic traffic (WAN). Frame Relay speeds up data transport by transferring
data to a frame-sized unit and leaving any necessary error correction at the endpoints. Local
area networks (LAN) with T-1 lines on significant backbones, as well as Public Wide Area
Networks (WAN) and Private Network Environments (PNE) with the lease, are frequently
connected via frame relay. Data is transferred to the Private VC Network rather than the open
Drawbacks of SD – WAN
• SD-WAN implementation and management can call for particular training and
experience.
• To suit certain requirements, SD-WAN solutions may need to be carefully evaluated
due to their different capabilities.
• To deploy SD-WAN successfully, additional hardware or software may be required,
depending on the solution.
(Sturt, 2022)
The user chooses to use Frame Relay as the organization's best WAN technology for the
EMC solution. The main benefit of frame relay is that it is a packet-switching method. Each
packet in packet switching networks has a distinct destination address that is used to convey
data from source to destination. After being packetized, data is commonly multiplexed
statistically. Statistical multiplexing enables numerous users to share an equal bandwidth by
assuming that not every subscriber would utilize it at the same time.
This does not include the usage of expensive point-to-point connections that employ circuit
switching, such specialized leased lines. Because they are rented and set aside for sole usage
24 hours a day, 7 days a week, leased lines are expensive. Leased lines are used by
subscribers to acquire bandwidth, whether or not it is actually utilised. Multiple data
connections may be sent via the network simultaneously thanks to statistical multiplexing,
and no one client is charged for exclusivity. As a result, this offers circuit-switched networks
a major cost benefit. The second advantage of frame relay is that it offers exceptional
network throughput and knowledge latency because to its variable-length frames and minimal
overhead. Frame relay may successfully encapsulate protocols due to its variable-length
frames. Its payload may contain a number of higher-layer LAN protocols, including the
Internet protocol (IP), due to its protocol independence.
The Frame relay network has a minimal overhead because it is not concerned with error
correction or flow control. As a result, switching user data takes up the majority of the
network's resources. The Committed Information Rate (CIR) of frame relay is an additional
Colombo
Network Monitoring
The process of continuously checking a computer network for issues like delayed traffic or
component failure is known as network monitoring. In order to immediately alert network
administrators to issues via text, email, or other applications like Slack, network monitoring
systems continuously scan the network. In contrast to network security or intrusion detection
systems, network monitoring software focuses on internal network problems such overloaded
routers, downed servers, or network connection issues that may affect other devices.
Network monitoring systems can also start a failover to remove problematic circuits or devices
from service until the problem can be fixed. A proactive network monitoring solution should
be able to spot anomalies that, if left unchecked, could cause an outage and stop operations
before they start.
Maintaining network integrity requires constant monitoring. The best network monitoring tools
offer a dashboard or visualization that shows the status of the monitored network components
at a glance, highlighting any abnormal parameters that need further investigation or
components like switches, routers, firewalls, servers, and software services, applications, or
URLs that may be the cause of network disturbances. A network monitoring system should
have high availability components for maximum efficacy, allowing a fail-over to a different
network monitoring installation to be used automatically in the event of a hardware or software
failure of systems running the network management tool.
(vmware, 2022)
Importance of network monitoring
Continuous network monitoring enables you to troubleshoot bottlenecks in addition to hard
breakdowns. You can evaluate the condition of your network using metrics like throughput,
latency, packet reordering, and jitters.
• Proactive Issue Detection – Network monitoring enables the early identification of
potential network problems such equipment breakdowns, performance bottlenecks, and
security breaches. Network administrators can resolve issues before they worsen by
keeping an eye on critical indicators and getting real-time notifications, which
minimizes downtime and lessens the impact on users.
Configuration Monitoring – For those in charge of traditional network components that make
use of local configuration files, configuration monitoring checks are absolutely necessary.
From a performance and IT security point of view, automated tools that can compare similarly
configured devices for inaccuracies are essential.
Most of the time, these tools compare the command-line output of a device configuration file
to other files on the network that do the same things. Network teams can look into differences
in configurations to make sure that all network parts work the same way.
Key features of configuration monitoring include automatic rollback for unauthorized
modifications, real-time monitoring of network configuration changes, and configuration
comparison across network devices to identify any inaccuracies. By ensuring transparency,
accountability, and consistency in network configurations, these features minimize risks and
preserve the network infrastructure's integrity and security.
Availability Monitoring – The simplest method for network teams to determine whether a
device is up and running is availability monitoring. Some tools for availability monitoring do
more than just check to see if a device is fully online or offline. This group frequently includes
hardware checks for network devices and specific interface status notifications.
Examples of commonly used protocols that monitor network availability include the following:
Cloud infrastructure Monitoring – Much of the time, private and public cloud occurrences can
utilize similar sorts of organization observing devices carried out on corporate organizations.
However, a number of cloud service providers provide their very own set of integrated network
monitoring tools. Customers often get these cloud monitoring tools for free, but they usually
can't work with other third-party tools that businesses already use.
Installing DU meter
Troubleshooting methodology
Identify the problem – Often, identification is the simplest step. An incoming phone call from
a user, a help desk ticket, an email, a log file entry, or any number of other sources might
achieve it. Users will frequently let you know when there is an issue.
It's critical to understand that not all problems have a clear fundamental cause. An unsuccessful
login attempt, for instance, can appear to point to a username or password issue, but the true
problem might be a lack of network access that prevents the authentication data from being
compared to a remote server.
The very first thing to keep in mind while troubleshooting a problem is that the symptoms are
not the problem. Finding the root cause of the symptoms that are manifesting themselves is
crucial while troubleshooting. You must interrogate the user in order to do that. Ask specific
questions regarding the symptoms’ onset and potential causes. If the user can reproduce the
issue for you, it can be very useful. Find out if anything has changed that could be the problem’s
cause. Make a backup copy of the system before you do anything to ensure that everything will
stay exactly as it is.
Specific steps here may include,
• Gathering information from log files and error messages
Establishing a theory of probable cause – Words like the theory and probability suggest that
you are assuming, even if that assumption is supported by facts. This phase's formatting
respects the possibility that the root cause (step 1) may not have been correctly determined.
However, troubleshooting may be started because the reason is detailed enough.
Make a list of potential reasons after the underlying cause of the symptoms has been identified.
Once all potential reasons have been listed, use your technical expertise to order the list. From
most likely to least likely, the probable reasons should be stated in order of likelihood. Don't
be scared to challenge the obvious either. If a power loss at the workstation is the symptom,
for instance, is the power cable plugged in, and if so, is the outlet getting electricity?
Furthermore, the issue has to be escalated to a higher level if no likely reason can be found.
Test the theory to determine the cause – The first two stages are most intriguing because no
setup modifications are necessary for them. Changes shouldn't be done unless you are at least
somewhat certain that you have a workable answer. The "information-gathering" phase
includes this step.
Experienced administrators frequently proceed through stages one, two, and three swiftly and
casually. Since problems and their symptoms are frequently recognizable, determining the
likely source of an error message or malfunctioning gadget is made easy. You could find
yourself going all the way back to step one at this point: Determine the issue. You might have
to restart your investigation if you test your idea to determine the likely reason and realize that
you were mistaken.
Consider if you can solve the issue on your own or whether it has to be escalated to a higher
authority after developing your theory of likely cause. You should test your theory to discover
whether it is the real cause if it is within your powers. You must choose how to test your idea
since it was founded on the most probable reason. If your theory is proven, you will go on to
Establish plan of action and implement solution – Before taking any remedial action after a
troubleshooting issue's underlying cause has been found, it is essential to make a strategy.
Planning ahead ensures that requirements and possible ramifications are considered, preventing
rash actions that can cause more disruptions. For instance, certain patches could call for system
restarts or prolonged downtime, demanding cautious scheduling to reduce the impact on
business operations. In other situations, downloading applications, updates, drivers, or even the
complete operating system files may be required before moving further with the fix. It may be
necessary to follow change management processes and test alterations in a staging environment
before putting them into use in a production environment.
For future use and knowledge exchange, it is crucial to document the intricate procedures,
instructions, and scripts involved in the resolution. Additionally, securing data integrity and
reducing the likelihood of data loss by backing up important data that could be at danger during
the recovery process. Before making any modifications to the system, it could also be necessary
to get consent from other IT staff members or adhere to particular procedures. Planning ahead
allows IT workers to approach the troubleshooting process methodically and reduce the
possibility of unexpected repercussions or network infrastructure outages.
Simply we must create and implement an action plan after testing the likely reason to identify
the real cause. Most frequently, simple solutions are required for basic situations. To guarantee
that the strategy is followed out properly, you might need to put it in writing if the scenario is
problematic. This is an additional chance to take the issue to a higher level, if required.
Verify Full System Functionality and Implement Preventive Measures – After executing the
plan, one must make sure the system is completely functional. Fantastic if everything goes as
planned. That may find that you have the capacity to, based on observations and the problem.
Put preventative steps in place to make sure the issue doesn't come up again. We must go back
to step one and continue the troubleshooting process if complete system functioning has not
been attained.
Document findings – When a issue develops in the future, keeping a record of the
troubleshooting procedures, adjustments, updates, hypotheses, and research may be helpful.
1. Kandy branch users cannot access the resources in the server located at Colombo
Head office.
Network documentation – Restricting access from Kandy branch to Colombo head office
server
Objective: This network documentation's goal is to describe the setup and security precautions
made to limit access from the Kandy branch to the server at the EMC Solutions headquarters
in Colombo.
Network documentation – To impose access controls for EMC Solutions, where users of
Customer Care may access File Servers at the Kandy branch, but users of Sales and
Marketing cannot access the same servers while still having internet access.
Router configuration: Set up access control lists (ACLs) on the branch router in Kandy. Make
an ACL that permits the subnet of Customer Care users to access the File Servers. To prevent
the subnet of users from Sales and Marketing from accessing the File Servers, another ACL
has to be set. To impose the access limitations, apply the ACLs to the relevant router
interfaces.
Firewall configuration: Set up access control settings on the Kandy branch's firewall. Make a
policy that permits the subnet of Customer Care users to access the File Servers. Implement a
different policy that prevents the subnet of users from Sales and Marketing from accessing
the file servers. Make that the firewall policy permits the subnet of the Sales and Marketing
users to access the internet.
Switch configuration: To divide network traffic, set up VLANs on the switches. Assign the
users of the Customer Care department to a particular VLAN with access to the file
servers. A distinct VLAN that does not have access to the file servers but does enable internet
access should be given to the users of sales and marketing.