All right, everyone, let's begin learning about the best practices of network maintenance.
How can we maintain our network in the most efficient and effective way possible?
We'll be looking at handling network issues,
managing changes in the network
and determining possible improvements to number, design and operations to prevent or reduce the risk of network interruptions or issues.
So what will be the best way to handle network issue if something happened, what would you do
first? Good practice with handling, and that work issue is to keep calm and not panic. Yes, even it is imperative to restore the network or service as your media as possible.
Remember your procedures. Understand the case or issue being encountered. Identify priority levels. Priority levels may very amongst industries and on the case by case basis.
Do your best to resolve the issue within your expertise and based on the training you received. If you feel the incident is more than you can handle,
escalate the matter to a specialized team or hires here.
Your aim is to restore back to the last stable working condition, which is why you must always have a backup configuration set ready.
What if there is a sudden interruption of the network. The changes were made. Everything seemed fine, but something still went wrong.
Immediately escalate to a specialized team or involve your vendors if necessary.
After all the trouble shooting and the issue still hasn't been resolved.
Always think of a Plan B, which is deciding on an interim or permanent solution. The first Consider
understand the problem and identify the cause of the issue.
Use existing equipment or components in your inventory, for example, using spares or executing redundancy manually
and or modifying their work design if necessary.
An interim solution is usually unstable, but it gets the network up and running to give you a window of opportunity to plan for a better solution.
A permanent solution could be your old equipment failing before having the chance to replace it during your next maintenance window, so you could probably install your new intended equipment. But of course it will be upon approval from your senior management.
There are times, however, of course, where, no matter how much you plan,
a new event will just pop a lot of the blue.
But as previously mentioned, keep calm, and no matter what happens or how limited time you feel. You may have plan your next move and make the best choice carefully.
Part of now operations is to always think fast on your feet when such events arise.
But what if you solve the issue? What next? Conduct a failure analysis such as What was the severity and impact of the problem? Was it the recurring issue?
What caused it? Is there a problem with the current network architecture?
Is it a faulty equipment? Or was a mystery that requires further investigation? An escalation?
All these information will help you to prepare your reports and documentations. That should include your findings,
the solution or solutions to the problem and recommendations to prevent the same incident from happening again in the future.
But what if you encounter the mystery case? How do you handle this?
For starters, gather as much information about the event and she can.
So what systems or services were affected for how long
Check system logs and your monitoring system to identify patterns of the issue?
Did it just happen? Always is a recurring events
discussed findings with necessary parties such as your team and or third party Venters, if needed. solidify your findings and justifications for the event,
whether the event was predicted or not. Always do reports and document your findings. Clue what solution or solutions were implemented. And what are your recommendations to help you or your team with similar future incidents?
Your recommendations can include new tools, hardware software. If you felt there were limitations that restricted you in your investigation,
so our first quizzes you encounter mystery events,
which are the following actions. Do you need to perform for further investigation of the issue?
And it's all options
now on to How can we manage that were changes.
So you're no work is live in running, but you notice improvements need to be made.
When was it decided to make changes in our operations?
You can do so when making routine changes. For example, installing software updates, usually due to bug fixes or feature and security improvements. Non routine changes such as replacing legacy equipment
and only make changes when necessary. For example, when a device failure is detected and it's affected the quality of your services or the efficiency over their work operations,
discuss with your team and raise the matter to see your management on your proposed action plan.
Remember, though, that all these changes needs to be included in your maintenance plans, Richard choir approval and acknowledgment before apply.
Routing changes are predictable events, so it's a little easier to prepare procedures for them and document. The outcome of that change
is worth knowing that any changes should always be tracked and documented.
You can even have the option to automate routine processes. For example, you could enable remote access after office hours using only ssh secure shell.
This way, it gives you more time to focus on priority task and operations
for non routine changes. There are many considerations to be taken to accounts before proceeding with the change,
and you will definitely need clear justifications, such as Is the change necessary?
Will this improve operations?
What is wrong with the current operations? Hence you only very good references, which can be gathered from your N. M S, logs
or even customer feedback to prove why you feel the changes needed
what resources are required? Are there additional costs? How long is the delivery time
plan? How you can use her resource is effectively including your costs and schedule to implement the change.
What are your activities for the change? Prepare a procedure plan and have someone else review it, which is usually your superior for their approval.
What is your role Back plan? There are times when you're implementation. May not work as expected,
so always have a backup plan or roll back to resume previous working configurations.
Then document your findings of what happened or why the implementation failed.
will be a backup plan. If it isn't work,
do a risk assessment to discuss potential wrists and impacts,
and then your action plans and how to solve the issues. If it rises,
what will be affected?
List the systems, services and the end users that will be affected by the change.
Is downtime required? For how long is it acceptable to management and urine users?
If yes, prepared to notify affected and uses of the downtime at least two weeks in advance to avoid surprises and to give them time to plan out what they may need to do during that temporary outage,
how will this be tested? Create a test plan to include the procedures you will perform and how you will test them in an environment that resembles the exact or as comparable is possible with your life. Never. Operations
also include what parameters you will use to determine whether the test is considered a success.
So far, we've discussed how to handle never corporations and how to manage network changes.
Let's move on to how we can improve network operations.
The aspects of this include improving your network architecture, the design of a stable and robust network, and you're operating procedures the way you handle a. Manage your operations effectively and efficiently as possible
with improving that work. Architecture. Avoid single points of failures, implement redundancies and equipment links
proper rolling, etcetera
before making improvements. Remember to keep it simple and keep it consistent. Do not over complicate things for yourself or your team.
think of the future. Making that work scalable to support for new implementations, for example, is your network I. P. V. Six. Ready? Remember, technology nowadays is continuously changing, so always be prepared and read up on the latest updates.
When implementing redundancy, consider that failure may still occur. So plan the possible failures that may arise and always monitor the conditions of your systems because redundancy does that guarantee? Ah, 100% stability and performance.
Keep track of your redundancy configurations as he can get complicated.
Hence why? To keep it simple and consistent throughout your entire network.
Vulnerabilities are possible. Such a suffer bugs. So always be ready to counter such possibilities.
As you plan for scalability,
consider your current services and future services. In other words, ensure your system is sufficient to support future services for maybe the next 3 to 5 years, depending on your organization, however, do not purchase equipment with features or high specs that you do not need.
For example, you were the one that purchase equipment used for data centers into ah, home use environment
use hierarchical network design concept, which are the core distribution and access layers. This, of course, depends on the size of your organization. However, this model is definitely a good reference to consider as you plan for scalability
and plan your progress for the implementation. This is a little bit more to do with project management considering the scope of work. The implementation by fees is which is usually recommended. Budget schedule resource is and so forth,
which all need to be taken into account
now When improving operating procedures, consider the services delivered to end users. Monitor your network instead. Priority alerts. Be proactive in your repairs. Plan well for never changes and conduct audits on your processes using your operations.
If you focus on improving services delivered to end users, consider the following What did your services, For example, Are they accessing your Web or email servers? Are they using Internet or back hold services? Who are your end users? Are they small medium businesses or enterprise customers?
What components are recorded to provide the service?
For example, the power cables, Browder's switches, firewalls, etcetera.
What happens when an issue occurs are all documentations, reliable and up to date?
Are the current tells you have in that
part of improving their work? Operations includes monitoring your network.
This helps you to ensure your assistance. Are working as expected
in delivering quality services to your end users. Hence, consider checking the condition of end to end services and your network capacity from your in the mess and verify in the abnormalities,
component failures or slow user experiences. If redundancy exists, is it working? Have often do you test the redundancy to ensure it's working
and also prioritize your alerts.
Another factor that helps contribute to providing excellent network operation services to end users is to be proactive with repairs. So, for example, and there any problems, schedule a time to fix them and adhere to proper change. Management procedures do not cause sudden outages while making adjustments.
Asked for approvals for the change, and once you're given the go signal, notify the correct people as early as possible before making the change.
Think about what could go wrong. Plan and test for solutions in the event that failure occurs.
An effective method of identifying whether improvements need to be made on your operations is to conduct audits. When auditing, consider what needs to be evaluated. For example, are configurations standardize throughout your entire network? Are the current standards considered at optimal efficiency with current
all redundancy links in equipment working when the failure occurs in the primary system or length?
Have you conducted tests to ensure confidence of making proposed changes into life operations and our old documentations and reports available and updated with the latest information for reference?
I'm sure many of you notice how repetitive thes Rasi *** are but it is very important to consider and to put into practice
in the long run, you will definitely understand how these factors could help you in your operations.
All right, next quiz.
Before implementing a new system into live operations, what would be the best assurance to justify that? The system will most likely to work
conduct tests in a similar environment as life operations always conduct tests before implementing anything new to your running network operations and services?
In summary, we discussed the best practices off handling network issues, known and unknown or mystery events. How we can properly manage network changes.
Whether it is a routine or non routine change, it is best to apply them only when necessary, and how we can improve our never corporations by enhancing network architecture and operation procedures.
We're at the end of module three, and at the end of this course
I want to extend my thanks to everyone who attended this course, and I really hope you learned something out of it that could help in your operations environment and work responsibilities. Finally, I wish everyone all the best in your network operations journey