CMIT 265 UMUC Revision of Network Virtual Storage Technologies Research Paper Hello, The attached research paper (Draft Version 1) needs to be edited with

CMIT 265 UMUC Revision of Network Virtual Storage Technologies Research Paper Hello, The attached research paper (Draft Version 1) needs to be edited with the notes marked in red. I am attaching the original instructions for your reference. Below are additional notes from the Professor. Thank you.Professor Notes:Great Start! Remember, when you write a document define all Geek stuff, spell out acronyms on first use in each paragraph and try to write for management personnel who are not necessarily technically inclined. Pictures and diagrams are a good thing. See attached for additional comments. Running Head: Network Research Paper
NETWORK RESEARCH PAPER
Student Name
UNIVERSITY OF MARYLAND GLOBAL CAMPUS
Running Head: Network Research Paper
Research outline
A. PURPOSE OF VIRTUAL STORAGE TECHNOLOGIES
I.
Storage visualization (?) allows for the increase of storage facilities
depending on demand.
II.
The technologies permit the manipulation of the storage without
tempering (?) with the storage devices when adding or reducing
storage space.
B. DATA RECOVERY PLAN
I.
There are challenges to storage visualization(?) for some possible
loss of data due to the SAN mismanagement.
Running Head: Network Research Paper
I.
INTRODUCTION
Storage virtualization is a technique that enables the physical information organization of hardware
through its logical representation. The method allows users not to worry about the location of their data
because it can easily be identified using a logical path. It enables the use of different hardware, which can
be accessed using a single logical file system. There various (grammar) types of storage visualization, but
one (you are showing two, not one?) of the widely used is Storage Area Network and the Network
Attached Storage [1]. SANs(define) allow the integration of hardware contained in different networks and
data locations into a single logical view (define). A SAN system has disks (define) grouped separately on
a network then managed in an array, where the server can access the array in a similar way to a local
storage device. NAS(define) allows the storage system to be accessed by network devices, usually done
by installing a NAS device onto a Local Area Network. Storage visualization(?) helps in reducing
administration costs of managing SANs by creating a flexible environment that allows for secure
backup(define), archive, and recovery of data [1]. The NAS technology is sophisticated as compared to
SAN because it contains unique protocols(define) such as fiber channel(define), Info band(define), and
iSCSI(define).
II.
PURPOSE OF VIRTUAL STORAGE TECHNOLOGIES
Storage visualization(?) allows for the increase of storage capacity depending on demand. Storage
visualization(?) can be combined with sever visualization(?) to permit the creation of disk pools whose
storage capacity can be increased depending on application needs. Before the advent of visualization(?)
and network storage technologies, the host system had its storage that was a waste to the unused or
excess storage capacity(define) [2]. Network storage technologies avail (?) storage capacity on demand.
(grammar) It facilitates applications that are part of the host system that required ample storage to use it
appropriately(define). visualization(?) and network storage technologies promote data location
independence(define) by abstracting the data’s location (define)from the logical representation (define)
used to access data. The virtualization system creates logical entities, (define) usually known as volumes
Running Head: Network Research Paper
(why?), that facilitate the mapping of the capacity to the exact location of the physical data(define). The
technology creates Metadata(define) because the mapping can range from a section of the physical disk
to a single full disk. (How? Why is that important?) Also, the above act improves efficiency as compared
to traditional storage arrays. According to [2], storage visualization(?) can increase storage efficiency by
up to 70%. This can employ the Jumbo frame(define), a high-performance network that can help improve
the SAN system’s performance. The jumbo frame is an Ethernet link(define) that encouraged overcoming
congestion(define) on the SAN resulting from IP(define) traffic. (How? What about NAS? How about
some diagrams to show what you are trying to describe?)
The technologies permit the manipulation of the storage without tempering (?) with the storage devices
when adding or reducing storage space. Host systems(define) are no longer used in storage
management and shielded from data changes such as data upgrades (why does that matter?) [2]. It has
enabled the simplification of data protection methods because assigning storage classes for
application(define) has been made easier by the technology. For instance, data migration from older
arrays to new devices can be done without interfering with application access. Remote offices have
embraced storage visualization(?) because it facilitates access to cloud storage that is not accessible
from the branches but depends on local servers for data. (Why would they embrace it if they don’t have
access?)
III.
DATA RECOVERY PLAN
There are challenges to storage visualization(?) for some possible loss of data due to the SAN
mismanagement(like what?). It is, therefore, critical to the data recovery plan (define the plan and
contents. Why is this a challenge to storage?) to help in the resumption of the standard functionality of the
system as soon as possible. Some of the cost recovery options include the hot site, cold site, and warm
site. A hot site is a parallel data center to the production environment that takes the place of the impacted
site in case of an outage [3]. A cold site is data center space without any installed servers, but will only
require installment of servers to be functional. A warm site contains servers ready for installation in case
there is an outage to the data center [2]. (How do you determine which one to use and what do they have
to do with a SAN? What about a NAS?) The continuity of the operations(define) depends on the
Running Head: Network Research Paper
availability, and the time is taken for specific features of a network system to be availed for continued
normal functioning. Some systems are designed for high availability, which means they include features
such as load balancing(define), redundant hardware. The recovery from a possible loss of data in the
data center has a backup(?) [3]. There are various types of backups, such as full, differential, or
incremental backup, depending on the user’s priorities(like what?). The network system should have a
low mean time to repair. MTTR(define) is crucial for a data center to back to(grammar) regular operation,
and therefore for efficiency, proper measures(define) should be taken to ensure that there is a small
MTTR. (define)
IV.
CONCLUSION
Virtualization and network-based storage technologies are various elements that need to be considered
for proper functionality. A virtual-based storage system is crucial in the management of volume because it
facilitates data location independence by abstracting the location of the data from the logical
representation used to access data. Although there enhance (?) the efficiency of application systems,
there can encounter challenges such as possible loss of data. In averting such problems, there needs to
be a data recovery plan to ensure that operations are not brought to a standstill. Data recovery
encompasses several aspects that are vital to the management of data centers. (You did not really
discuss NAS in your paper.)
Running Head: Network Research Paper
REFERENCES (A little light on references)
[1]M. Agrawal and N. Vani, “Server Virtualization using Cloud Environment for Data Storage & Backup,”
International Journal of Science and Research (IJSR), vol. 5, no. 6, pp. 449-452, 2016. Available:
10.21275/v5i6.nov164021.
[2]S. Patil and K. Honwadkar, “Unified Virtual Storage: Virtualization of Distributed Storage in a Network,”
International Journal of Computer Applications, vol. 1, no. 22, pp. 30-33, 2010. Available: 10.5120/447681.
[3]C. Tankard, “Streamlining data discovery,” Network Security, vol. 2018, no. 6, p. 20, 2018. Available:
10.1016/s1353-4858(18)30059-x.
ORIGINAL INSTRUCTIONS
You have been hired as part of the networking team at UMGC. After completing orientation and
training, your manager calls you into a meeting to discuss your first project.
The University is interested in creating a repository of networking knowledge based on research
papers. The research papers will be drafted by all employees, and you may select from a list of
approved topics. As a junior network engineer, you are asked to prepare a research paper that best
aligns with your interests. The approved research topics include:
•
•
•
•
•
•
•
•
•
Compare and contrast the characteristics of network topologies, types and technologies.
Summarize cloud concepts and their purposes.
Explain devices, applications, protocols and services at their appropriate OSI layers.
Explain the functions of network services.
Explain the purposes of virtualization and network storage technologies.
Compare and contrast business continuity and disaster recovery concepts.
Explain common scanning, monitoring and patching processes and summarize their
expected outputs.
Explain authentication and access controls.
Compare and contrast network policies and best practices.
The research paper represents a great opportunity to focus additional study towards a networking
topic of your interest. It is also an opportunity for you to gain further expertise about a particular
aspect of networking fundamentals that you will be asked about in the certification exam.
After speaking to your manager, you are excited about the research project, but realize you will have
a busy schedule. As you are writing the research paper, you will also have to prepare for the
CompTIA Network+ Certification exam. To prepare, you will perform the activities and labs within
the TestOut LabSim environment following the proposed weekly schedule. One of the conditions of
your employment at this University is that you obtain this certification within 60-days of being hired.
The Network Research Project Requirements:
The Network Research Project (NRP) expectations are to explain the concepts you are learning as
part of this Networking Fundamentals course. This is not an extensive review of the topic areas, but
instead a cursory exploration of any approved topic you find most interesting.
You should consider the additional details below to guide you through completion of the NRP.
•
•
Quality is valued over quantity, but quantity is necessary for a quality paper. It is estimated
that 3 – 5 pages (not including the title page) would be necessary to address each Network
Research Project (NRP) topic.
Each Network Research Project (NRP) must have an Introduction. The introduction should
address the purpose of your project, and an overview of what you will convey to the reader.
Each NRP must have a Conclusion. The conclusion should summarize your findings in a
succinct manner. The remaining format will be at your discretion. It is suggested that you
•
•
•
•
review the NRP details under each approved topic and outline their paper accordingly. You
should maintain a consistent format throughout the entirety of the document.
All sources must be cited using the IEEE format. This is an excellent guide that covers all
aspects of citing in IEEE style. Why do we use IEEE format? IEEE format is used in technical
fields when writing research papers. Do not plagiarize any material or content. The use of
figures and diagrams is encouraged where appropriate. Students should contact UMUC
Effective Writing Center for any required writing assistance.
You will be allowed to submit the NRP three times. The first two draft submissions are not
graded, but will receive feedback from your Professor. Draft version 1 should be submitted
by Sunday of Week 3. Draft version 2 should be submitted by Sunday of Week 5. You should
address the feedback in the context of the NRP grading rubric. The final draft of the NRP is
submitted in Week 8. It must first be uploaded to Turnitin, and then the Assignment folder.
Submitting a draft in Week 3 and 5 is not mandatory, but highly encouraged. You will not
receive feedback or have an opportunity to resubmit a draft in Week 8. A submission in
Week 8 will be your final, graded version of the NRP. If you are satisfied with your feedback
prior to Week 8, you have the ability to submit you final draft early by uploading it to Turnitin,
and submitting it to the Week 8 Assignment folder.
You should use proper terminology and expand acronyms in each paragraph they are used.
For example, the first time in a paragraph an acronym is used it should be expanded (e.g.,
University of Maryland Global Campus (UMGC)). Thereafter, and as long as you are in the
same paragraph, the acronym (e.g., UMGC) can be used. When starting a new paragraph,
the rule begins anew.
Review the Network Research Project (NRP) grading rubric to understand the expectations,
and how the final draft will be graded.
Project Details:
Details on each topic area are provided below to provide further understanding of expectations for
the Network Research Project (NRP). You will select one topic area to conduct the NRP. At a
minimum, you should address the details provided for each topic area. However, you are not limited
by these additional details. You are encouraged to research and discuss additional aspects under
any of these approved topic areas.
•
•
•
Compare and contrast the characteristics of network topologies, types and technologies.
o Wired Topologies (logical vs physical, star, ring, mesh, and bus)
o Wireless Topologies (mesh, ad hoc, other infrastructure)
o Types (LAN, WLAN, MAN, WAN, CAN, SAN, and PAN)
o Technologies that facilitate the Internet of Things (Z-Wave, Ant+ Bluetooth, NFC, IR,
RFID, and 802.11)
Summarize cloud concepts and their purposes.
o Types of services (SaaS, PaaS, IaaS)
o Cloud delivery models (Private, Public, and Hybrid)
o Connectivity methods
o Security implications / considerations
o Relationships between local and cloud resources
Explain devices, applications, protocols and services at their appropriate OSI layers.
o Layer 1 (Physical)
o Layer 2 (Data Link)
o Layer 3 (Network)
o Layer 4 (Transport)
o Layer 5 (Session)
o
o
•
•
•
•
•
Layer 6 (Presentation)
Layer 7 (Application)
Explain the functions of network services.
o DNS service (record types, internal vs external DNS, third-party/cloud hosted DNS,
hierarchy, forward vs reverse zone)
o DHCP service (MAC reservations, pools, IP exclusions, scope options, lease time,
TTL, DHCP relay)
o NTP
o IPAM
o VoIP
o Simple Network Management Protocol
o File sharing
o WWW
o Printing
Explain the purposes of virtualization and network storage technologies.
o Virtual Networking Component (Virtual switch, firewall, NIC, router, hypervisor)
o Network storage types (NAS, SAN)
o Connection Type (FCoE, Fibre Channel, iSCSI, InfiniBand)
o Jumbo Frame
o Compare and contrast business continuity and disaster recovery concepts.
o Availability Concepts (Fault tolerance, high availability, load balancing, NIC teaming,
port aggregation, clustering)
o Power Management (Battery backups/UPS, power generators, dual power supplies,
redundant circuits)
o Recovery (Cold sites, warm sites, hot sites)
o Backups (Full, differential, incremental, snapshots)
o MTTR
o MTBF
o SLA requirements
Explain common scanning, monitoring and patching processes and summarize their
expected outputs.
o Process (log reviewing, port scanning, vulnerability scanning, patch management,
reviewing baselines, packet/traffic analysis)
o Event management (notifications, alerts, SIEM)
o SNMP monitors (MIB)
o Metrics (Error rate, utilization, packet drops, bandwidth/throughput)
Explain authentication and access controls.
o Authorization, authentication, and accounting (RADIUS, TACACS+, Kerberos, Single
sign-on, Local authentication, LDAP, Certificates, Auditing and logging)
o Multi-factor authentication (something you know, have, are, do, or somewhere you
are)
o Access Control (802.1x, NAC, port security, MAC filtering, captive portal, access
control lists)
Summarize common networking attacks.
o DoS (Reflective, amplified, distributed)
o Social engineering
o Insider threat
o Logic bomb
o Rogue access point
o Evil twin
o War-driving
o Phishing
o Ransomware
o
o
o
•
DNS poisoning
Brute force
Exploits vs. Vulnerabilities
Compare and Contrast network policies and best practices.
o Privileged user agreement
o Password policy
o On-boarding/off-boarding procedures
o Licensing restrictions
o International export controls
o Data loss prevention
o Remote access policies
o Incident response policies
o BYOD
o AUP
o NDA
o System life cycle (asset disposal)
o Safety procedures and policies

Purchase answer to see full
attachment