KINDLY ANSWER FOR NUMBER 1 AND TWO FROM THE TUTOR VIEWPOINT ITS OK NOT TO PUT ANY REFERENCES FOR THE ANSWER TO THIESE
1)
I have work with routers when I worked at Marriott International as a FOSSE support analyst helping Marriott support their properties to keep the guest check in system “FOSSE” online to hold guest information. When network performance is degraded in any piece of technology this can cause a slowdown, customer complaints, outages and loss of income from a company and customer standpoint. When supporting a company that expects when they have issues, they should be fixed with no future issues you have to fix the issue immediately and find the route of the problem. There was daily maintenance that was conducted to prevent the devices from experiencing things such as packet lost ordefective interface, physical errors, etc. When there were issues where the properties were down because of the router losing connection, I would shut down the server. I would log into the router to check for error or any logs that could show where the connection was lost.
Somethings as little as an IP change or router address issue can cause the router to shut down or have outages. It is very important that when we install or configure the routers the information entered is slowly. One error can cause an entire property to crash randomly, and the only fix is to find the issue or reboot to flush out the glitch. Technology will never be perfect, but it has advanced beyond many of our beliefs helping many people have successful and safe companies. It can be the server causing the router to run slowly so its important to get the server technicians involved as well. One of the worst issues is that a switch or cables has gone bad where a local technician may need to go onsite same day to fix issue.
References
Binther, L. (2020, May 12).The top 10 causes of network performance degradations. Accedian. Retrieved April 3, 2022, fromhttps://accedian.com/blog/top-10-causes-network-performance-degradations/
2)
This third unit discussion board is about troubleshooting te network and the devices connected on it. We must understand that monitoring communications at the host level is mo longer enough. That worked fine back when individual services ran on stand-alone machines. Now days networks are so fast and there are so many users that companies today must have many devices and machines ro run teir business. So a network administrators it is our job to troubleshoot the network.
We have to take into consideration how old is the network and the devices connected to it and determine ow the expansion of the business will take place. The features that were available earlier are notavailable, but have been enhanced with features that are far more versitile and are 10 times faster. The older machines will run at slower speed and would not be efficientfor the company now.
We must understand that with technology advancing at the rate that it is we must prepare the network within the organization for the expansion that is needed.
Issues can arise at numerous points along the network. Before you start trying to troubleshoot any issue you want to have a clear understanding of what the problem is, how it came up, who it it affectig\,and how long its been going on. By gathering the right information and clarifying the problem, you'll have a much better chance of resolving the issue quickly without wasting time trying unnecessary fixes.
Here are some steps to help determine where the problem is:
First check the hardware. When you begin the troubleshooting process check the hardware first to make sure it works and connected correctly.
Use IP Config. At a command prompt type ipconfig into the terminal the defaut gateway is your computers IP Address is the number next to IP ADDRESS
Use PING and TRACERT. If you router is working fine, and you have an IP address starting with something other than 169, the problem is mostly located between the router and the internet. At this time use the ping tool. You can the tracert command to do the same as Ping does by typing tracert 8.8.8.8.
erform a DNS check. Use the command"nslookup" to determine whether there is a problem with the server youre trying to connect too.
Contact the ISP all the above turn up no problem
Check the virus and malware protection.
Review Database logs to make sure the databases are functioning as expected.
Once steps are taken then we must make sure that we have the correct flow that should be taken:
Collect information
Customized loops
Check access and security
Follow an escalation framework
Use monitoring Tools