IBM Nortel Networks L2/3, Руководство пользователя

Страница: 174 / 190

160
Nortel Networks L2/3 Ethernet Switch Module for IBM
Eserver
BladeCenter
Network logs
Review the network logs to help you determine possible errors:
򐂰 Console log messages
Last 10 messages only
򐂰 Syslog messages
Highly recommended to use
򐂰
SNMP trap messages
Highly recommended to use
򐂰 Server logs
Packet traces
Collect packet traces as needed:
򐂰 Client side
򐂰 Server side
9.3.3 Data analysis
You should consider specific causes and narrow down the list to the most likely issue or
problem. If necessary, gather more data based on your analysis.
9.3.4 Action plan creation
When you have determined the cause of your problem, you should ask the following:
򐂰
What are you going to do to resolve the problem?
򐂰 Who will do the work?
򐂰 When will the work be done?
򐂰 Can configuration changes be made during core business hours or is a maintenance
window required?
򐂰 Who needs to approve the change?
򐂰 What is the back-out plan if the problem is not resolved or something goes wrong with the
change?
9.3.5 Action plan implementation
Make the planned changes to the environment in an attempt to resolve the problem.
9.3.6 Observation of results
Review your efforts to resolve the problem:
򐂰
Did the changes resolve the problem? If not, then you may need to go back a few steps
and gather more information or formulate a new action plan.
򐂰 Verify that the problem has been resolved. If it has not been resolved, collect more data,
analyze, and revise implementation plan.
򐂰
Ensure that your changes have not inadvertently caused other problems. If another
problem is created, try to troubleshoot that problem (if you have time and approval).
Otherwise, initiate the back-out plan.