# data[].attributes.headline
D1 - Justify the inclusion of routine performance management activities within a network manager's role

# data[].attributes.subject
D1 - Justify the inclusion of routine performance management activities within a network manager's role

# data[].attributes.body
When establishing a network, it's always important to establish a consistent and routine performance management activity. The reason why this is important is because it's in a networks best interest to always be performing above a certain standard. If a network is not performing above this standard, it's likely that the network's components are deteriorating due to long term use. It's the job of a network manager to ensure that a network is functioning at a good standard. This 'good standard' is usually defined by the response time speed of the network. A lot of this data can be accessed an analyzed using some of the tools I mentioned prior (e.g. LibreNMS and WireShark). Tools like LibreNMS especially are useful for providing routine performance management tasks, along with data from these tasks to the network manager. Generally, the majority of the activities involved in performance checking is accomplished by the network monitoring tools that are used. Some of these performance management activities include:
- Performance/Response time Checking: Carries out test connections throughout the network in order to check user response time. If there are any incongruities between the standard performance log, the network management will have to configure, repair, or even replace the network device that is at fault. Useful for noticing the early signs of network hardware deterioration.
- Standard performance logging: As mentioned previously, the network will often used a standard performance log as a reference for how fast the network should be running. The creation of this reference log is another activity that the network management is required to do. Thankfully, many network management tools can carry out this activity seamlessly.

Routine performance activities, while on the surface may seem pointless, are actually much more important than people give it credit for. This value and importance can be justified by looking at some of the problems that can pop-up if this routine check isn't done. Examples include:
- Steady decline in network performance: Overlooking a slight dip in network performance is relatively fine, but these dips in performance can stack up, causing a significant and obvious decline in network performance. The more problems there are, the harder and more tedious it becomes to resolve these issues
- Missing network problems: A lack of routine performance checks can often lead to a network manager missing problems that can prick up in a network. This is especially troublesome if the problem turns out to involve the hardware of a network (especially if it involves an integral network device, like a server). Missing these networking problems can lead to overlooking severe issues that could end up detrimental for a network
-  Loss of money/time: Routine performance checks are very effective at preventing networking problems. Therefore, it also goes without saying that the absence of these routine performance checks causes more issues to pop-up. Correcting these issues often costs a lot of time and money, especially if the error involves a faulty hardware device that goes unnoticed. The entire point of a network, is to establish a time-saving system that brings in money to the organisation/company that is backing it.

In conclusion, the inclusion of routine performance activities in thenetwork managers role is important, and can be justified by looking at the benefits that occur if it's included, and the problems that can occur if it's not included.

# data[].attributes.headline
M2 - Explain the goals of fault management

# data[].attributes.subject
M2 - Explain the goals of fault management

# data[].attributes.body
Fault management is, arguably, one of the most important levels within the FCAPS model. As explained prior, the fault level corrects any network errors/problems that spring up. However, this is somewhat of a vague explanation regarding the goals of the fault level. Generally, the fault level is defined by the following key goals:
- Reduce the amount and severity of network errors
- Detect the early signs of a network issue
- Remove the errors before they have caused any damage
- Record the prevented issue for future reference
These are the goals of fault-based network management.
Fault management generally accomplishes this through the following steps:
STEP 1 - Detect the fault
STEP 2 - Troubleshoot the cause of the fault
STEP 3 - Resolve the fault
STEP 4 - Record the fault and solution that was used to resolve it
Through these means, fault management is able to successfully accomplish its goals.
[END]

# data[].attributes.headline
P4 - Explain the functions of network management

# data[].attributes.subject
P4 - Explain the functions of network management

# data[].attributes.body
Network management systems are often comprised of multiple functions. These functions are very useful when it comes to carrying out a network managements tasks. These network management tasks are often categorized into a model/framework called FCAP. FCAP stands for: Fault, Configuration, Accounting, Performance, and Security. Each of these words act as the five levels of network management tasks. The reason why FCAPS is used is because it's useful for setting the requirements of a functional network management system. It's helpful for use as a reference model. The reason why FCAPS is broken into 5 levels is because the developers pf the model believed that any network management system could be categorized into five levels. The fault level defines the functions that find and correct any network problems. The configuration level defines the functions that monitor and control network operation activity. The accounting level is made up of functions that control the management of costs and payment between a customer and a service provider. The performance level manages the overall performance of a network, and the security level manages the defences of a network (e.g. user rights, firewalls, etc.)
----------------------------------------------------------
The most common application of NMS functions is to control the variables that are involved in a network in order to avoid any FAULTS. Some of these function-controlling-variables include:
- network throughput: Deals with the 'amount of data that has successfully moved from one part of a network to another' variable (e.g. traffic/bandwidth)
- User response time: (self-explanatory) Deals with the 'amount of elapsed time that occurs between the beginning of a response, and the end of an inquiry within a network' variable.
- Line utilisation: Deals with the 'total amount of bits transferred between physical network devices divided by the time taken to transfer those bits' variable.
-------------------------------------------------------------
When CONFIGURATING a NMS, The following activities need to be considered:
- Planning: It's important to plan a network out before investing in the development of it. If this activity is not done, it's likely that a lot of errors and problems will be encountered, which will end up being costly in the long run.
- Designing: It's important to have a robust and secure design solution when implementing a network. It also has to be designed so that it can handle how the network will end up being used day-to-
- Installing: It's important to correctly install a NMS using the correct components , services, and applications. This mainly involves installing the relevant services (communication services, manufacturing services, sales services, etc.)
------------------------------------------------------------
It's vitally important to use a number of network operations in order to carry out the function of network security (NOTE: The fault level corrects already present errors, whilst the security level prevents the errors from ever occurring in the first place). Some of these network operations include:
- Data Logging: This application is used to collect and record user data over a period of time. This is useful for preventing potential resource over usage. It is also used to track all interactions between storage devices and data, allowing for network admins to more easily trace any suspicious activity
- Performance/Traffic Tracking: This application is useful for collecting and recording monitoring network packets. This is commonly carried out through the process known as packet sniffing. This, like data logging, is useful for reviewing and preventing any malicious incoming data packets.

# data[].attributes.body
Almost all tasks
- Ref 1 -
Allen Kaye, J. P. (2010). Btec Level 3 National It Student. In J. P. Allen Kaye, Btec Level 3 National It Student (p. 424). Pearson Education Limited.
P2
https://www.webopedia.com/TERM/M/Microsoft_Operations_Manager.html
P3
- Ref 1 -
https://www.techopedia.com/definition/688/server-virtualization
- Ref 2 -
https://www.techopedia.com/definition/24844/remote-monitoring-rmon
P4
- Ref 1 - http://searchnetworking.techtarget.com/definition/FCAPS
- Ref 2 -
http://www.erg.abdn.ac.uk/users/gorry/course/intro-pages/tput.html
D1
http://www.techsoupforlibraries.org/planning-for-success/networking-and-security/monitoring-the-performance-of-your-network

# data[].attributes.body
The purpose of networking tools are to manage, monitor and modify a networks resources (e.g. applications, memory storage, bandwidth, etc.).

---------------------------------------------------------------

HP OpenView - HP OpenView is a collection (or suite) of networking applications that can be used to manage a network’s software and storage. It can also provide information on network, server, and storage performance.

Cisco works – Cisco works is another suite of management tools that are designed to monitor Cisco-based networks. Included in this suite are a number of CiscoWorks tools, including IPM (Internetwork Performance Monitor), Cisco View and DFM (Device Fault Manager).  Additionally, Cisco bundles these tools together into the packages SNMS (Small network management solution) and LMS (LAN management solution). All in all, these tools are used to maximise a network’s security, increase network efficiency/accuracy, and improve network availability.

WireShark – Wireshark is a networking tool that is used to analyse network packets. It allows admins to see background information on the data that is being sent across their network by inspecting oncoming packets of data. It can also be used to troubleshoot any network traffic and/or transmission problems, using the same process.

System Software (MS Operating Manager) – MSOM is a network monitoring application developed by Microsoft. Like other network monitoring tools, it provides various network management tools, some of which include: event management, performance management, and application monitoring.

LibreNMS – Like MSOM, LibreNMS is a network monitoring application. Unlike the Cisco Works suite, LibreNMS supports multiple network operating systems. LibreNMS is used to monitor network activity. LibreNMS also allows the data gathered from a network to be formatted into a different graph, and it has customisable alerting, making it easier for an admin to be notified of any problems.

# data[].attributes.body
In our modern day, network technologies are advancing more and more. This advancement has not only affected already existing technologies, but it has also created new and emerging technologies. These emerging technologies can include modern trends (e.g. working from home) and technology developments (e.g. remote monitoring, and big data handling). The following is some examples of these emerging technologies.

---------------------------------------------------------

Server Virtualisation
Server virtualisation is an emerging network technology that can be used to partition physical servers into virtual servers. These virtual servers can be used to establish virtual layers, allowing network devices to store their own resources (with their own permissions) separately, without having to actually use multiple physical servers. Beneficial for easily establishing server-client relationships.

Video on Demand
Video on demand is an emerging network technology that is used to store multiple TV shows and films. These TV shows are stored on an interactive system, allowing users to watch their favourite shows/films whenever they want, without having to wait for a scheduled broadcasting time.

Remote Monitoring (RMON)
Remote monitoring is an emerging networking protocol that allows different networking systems to share network-monitoring-data. This technology provides network admins more freedom.

IPv6
IPv6 is an emerging technology and acts as the protocol for the Internet. IPv6 is the most recent version of the IP protocol. The biggest addition to this version, is the identification and location systems which were integrated, which make Internet communication much more secure than previous versions.

# data[].attributes.headline
M1 - Describing the potential impacts of emerging network technologies

# data[].attributes.subject
M1 - Describing the potential impacts of emerging network technologies

# data[].attributes.body
Emerging technologies will, by their very nature, always have an impact on the networking field as a whole. The following are examples of the potential impacts of emerging network technologies.

-------------------------------------------------------------

Enhanced Capabilities
There are a lot of emerging technologies that enhance the capabilities of already existing processes. One example of this includes the newest version of the IP protocol: IPv6. IPv6 establishes an enhanced location and security capability. Older versions of the IP protocol didn't have these enhanced capabilities, making them much more obsolete as a result. Another example includes server virtualisation, which reduces the overall amount of processing power than networks not using them. Of course, it's also important to make sure that you're enhancing a capability instead of degrading it.

New Work Methods
Besides enhancing the capabilities of an already existing process, new emerging technologies often impact common work methods by making them redundant. Emerging technologies often create new working methods that are much more effective and less time consuming. Examples of this impact include the modern trends home working and mobile working. Both of these trends allow employees to work from their home or from their mobile. This new work method makes it that much easier for a business to function smoothly. Other examples include many web-centric applications like Google Drive or Padlet, which make it easier to share files through a IP-based connection.

Ease of Use
Finally, emerging technologies often make processes, that were initially tedious and difficult, easier to do. An example of this includes server virtualisation. Server Virtualisation makes it easier to configure and administrate multiple servers. Besides this, there's also video on demand, which reduces the tedium of having to wait for a show to be broadcasted.

# data[].attributes.body
P2 Screenshot WireShark

# data[].attributes.body
Keep it up. You might want to include the other NMS protocol, but nice one
Include referencing.

***********************************
Included other NMS protocol, and added referencing
- Connor

# data[].attributes.body
------------------------------------------------------
Network Operating System
Definition: A NOS is a computer operating system that is designed to support network functions, specifically over a LAN. It is often used to implement network protocols, establish user login and authentication, provide email support, and for providing mechanisms and facilities for security and file sharing functions
Example 1:Windows NT - One of the most popular Network operating systems
Example 2: Solaris - A network operating system for OS devices

---------------------------------------------------

Protocols
Definition: A protocol is a set of rules that computers abide by in order to communicate. It is used to establish a standard for connections, thereby allowing computers to communicate 'correctly'.
Example 1: SNMP - a protocol that manages and monitors network devices and their functions. Specifically, it is used to govern how a network manager collects information from network devices and configures network devices.
Example 2: FTP - a protocol that governs how files are transferred between a client and server on a computer network
Example 3 (BONUS): NTP (Network Time Protocol) – a protocol that is used to synchronize the internal clocks of a networks (typically packet-switched) computers. This is useful for making sure that both workstations and servers of a network are working at the same time

-----------------------------------------------------

Layout
Definition: Layout is term which describes the positioning of network devices and other networking implements. It's important that a layout is established, because it is often directly linked to how a network performs.
Example 1: Topology - a term which describes the physical arrangement of a network, nodes and connecting lines included
Example 2: Cabling is a term which describes the way in which cables are laid out, when being piped (computing term that means sending data) between network devices
Example 3 (BONUS): Wireless connections also have a layout, but the need for wired infrastructure will typically still exist.

------------------------------------------------------

Devices
Definition: The devices of a network describes all the hardware that a network is comprised of. Without the hardware, a network is purposeless.
Example 1: Workstation - refers to a computer system (also sometimes called a client). There are two types of client: thick (all applications on computer just using recourses on computer) and thin (applications hosted on server, you connect to it and all processes will be running on server).
Example 2: Server (General) - a server is a computer or computer program that manages access to a resource or service. Examples include: mail server, file server, print server (manages print queues), application servers, and proxy server (provides an intermediary link in order to mask a client's IP address).