in this module, we will dive into the core responsibilities and network operation management.
Let's start by defining network operations. What exactly are we managing?
Network operations Management aims to achieve optimum efficiency in their work, performance and availability to end users. The activities include monitoring, analyzing, controlling and maintaining systems on your network. It is a commonly 24 7 duty
which is done at a NFC facility
or this curable access from home.
What are other scopes of work involved?
Submitting reports on a periodic basis, which can be either daily, weekly, monthly, etcetera
and many managed services include agreements. Commonly s a lease or service level agreements as a criteria to maintain never performance levels to end users.
So, for example, if there's a monthly s a layoff 99 form 5%. It is the job of the never operations management team
to ensure the performance levels or criteria can be equal to or more than 99.5%.
The core responsibilities involved in the work operations management include monitoring and to end, for example, a system reach ability and that work traffic.
One Turing equipment Conditions System health, for example,
Analyzing network traffic
device configuration and change Management i p. Address management
and reports and documentation.
Monetary and to end is basically the enter and monitoring of network services or communication link,
for example, from an office
to branch a
to remote site.
This ensures life operations meet or exceed minimum service requirements and fully satisfies and user expectations.
Common variables monitored are never clean. C To know how long it takes for data to travel across your network to the intended destination hosts, for example, here you can see fiber optics and the set involved in the day. The trouble, which is to milliseconds and 500 milliseconds
and by monitoring network bandwidth utilization, were able to identify possible congestion in the network or identify certain trends, such as the time when life operators are most active during day. These variables are great references when producing reports
by monitoring the equipment conditions, you're also monitoring the systems lifetime.
This keeps track of a systems condition.
The insurance optimal efficiency, off services,
monetary assistance up time is equivalent to determining the availability of the system or service availability in the system. Health conditions on your network you can plan well for preventive maintenance actions. This can include identifying faults in the system or its components.
Be aware of when the replacements or armies need to be done.
Understand the level of capacity and system is able to function with current operations and facility conditions.
There are times when just monitoring bandwidth utilization isn't enough.
When your network becomes congested, you may want to know a lot more on what our services are running or for future capacity plans. You would like to identify the minimum bandwidth capacity you require.
In other words, you analyze the work traffic for troubleshooting and planning purposes as it can provide a more detailed insight into your network, such as knowing the type of applications and protocols.
Additionally, there usually categorised into top applications, top protocols or top sources in the network based things a little bit easier.
All right, so we're up to our first pop quiz.
What variable can be used to determine system availability If you need more time, feel free to pause the video,
and the answer is
system up Time
system logs helped to monitor system behavior with environment and other systems identify changes in the network whether it be intentional accidental or basically even abnormalities.
It helps with troubleshooting and reporting and critical log events should be recorded.
Logs are very helpful when troubleshooting an issue, and at times you may even need to share logs when you escalate the matter to your service providers.
Laws can also be used as a reference for possible future recurring incidents, and they can also help you to justify better when proposing new or improved implementations.
This is why krill go logs are documented.
Always remember to document all findings, especially the critical ones that made an impact on your current working operations
that were configuration management includes
and inventory management.
To be sure, to control changes applied on a system or network is best to document and track new or modified configurations and systems. Backups of configuration for archiving and recovery purposes.
Risk assessment and roll back plans should be prepared,
record hardware replacements or software upgrades and do a pre testing before implementation on the Life Network.
Intentional and accidental changes must have a rollback plan so that in the event where a Braun configuration to a rather into faces made, for example, or if a configuration may not be working as expected, you're able to restore back to its last working condition.
Abnormalities may take more time to troubleshoot. However. Logs can definitely help identify the root cause.
I be addressed management. It's important to document because it allows the administrated to plan well on I p address allocations when there is a need to install new equipment or to apply changes and i p addressing on the network.
This helps to mitigate risk of i p address conflicts. You can simply prep up an Excel file for this, or if you are looking for something a little bit more sophisticated. There are available tools such as solar winds i p. Address manager
Reports are based on the continuous timely submission, usually monthly to keep record off the conditions of the network and service operations.
These monthly reports may include network and to end services. To ensure that the minimum requirement for life operations is met.
The conditions of all network equipment and facilities to determine the equipment is working at optimum efficiency and in a suitable cooling environment.
The possible number of incidents detected, which are usually tracked by the use of tickets This helps to document types of incidents, level of severity, level of impact on operations and whether these incidents are recurring
and also the number of service requests by customers.
Managing documentation ensures reliable re sources of information used in that work operations.
Such documents include intervention procedures used for troubleshooting,
backup and recovery in the event of a system failure, or the loss
configurations and changes
I P. Addressing
and full escalation with focal point information.
Next Pop Quiz
which corn network operations responsibility is most crucial to perform backups and roll back planning,
and the answer is
device configuration and change management.
Remember, before making any changes to your systems. Always prepare backup configurations for archiving and if record to roll back to previous working systems in the event where a system implementation may not be working as intended
into these video, we discussed the core responsibilities in the corporation's management.
Tracking changes and keeping documentations up to date is essential to the job, and the role contributes to future planning of improved and long term use of systems and services.
Up next is module to where you will learn about the essential technologies commonly used in their work operations management. This includes an M S S and then P
sis log and that flow. We will discuss the features of these technologies and their functions when used to monitor and manage their work operations.