Avaya Troubleshooting Routers Instrukcja Naprawy Strona 33

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
Przeglądanie stron 32
Introduction
308656-14.00 Rev 00
1-9
However, displaying the debug messages can help you to understand the
systematic process the software uses to load and initialize discrete software
components. When the software detects a problem, the debug messages can show
you the systematic process the software uses to isolate its components, shut them
down, and restart them to try to fix the problem.
Many debug messages are meaningless in isolation, but when considered in the
context of other messages, they can help you to understand the problem. Debug
messages typically contain words such as “creating,” “dying,” “killing,” “gates,”
and “gate handles.”
The name of the router’s operating system is GAME (Gate Access Management
Entity). In addition to assuming the typical responsibilities of an operating system,
GAME creates gates.
Each gate is a process. The process may perform a discrete action for a software
entity, such as IP; or, it may create child gates responsible for their own processes.
A parent gate keeps track of its child gate by remembering its logical address,
called a gate handle.
If you configure the router to run IP, the gate responsible for creating protocols
creates an IP gate. This gate in turn creates gates for IP processes, such as RIP or
OSPF. RIP and OSPF gates create gates of their own to handle RIP and OSPF
processes. Thus, each time the operating system starts, it creates gates that form a
hierarchy resembling a family tree.
If the software detects a problem, it instructs the parent gate to “kill” (eliminate
from memory) the gate associated with the problem, and then re-create it. If the
problem recurs, the software instructs the grandparent gate to kill its children and
re-create them. When a gate “dies” (is eliminated), all of its children also die. The
grandparent re-creates the parent gate, and the parent gate re-creates its children.
This process expands to the next generation and continues until the problem is
resolved or the software entity reinitializes. GAME generates a fault event
message when it reinitializes a software entity. This system of creating and killing
gates allows the software to try to correct a problem, but minimizes the impact to
the network because it resets only the components that are associated with the
problem.
See Appendix A for examples and explanations of debug messages.
Przeglądanie stron 32
1 2 ... 28 29 30 31 32 33 34 35 36 37 38 ... 267 268

Komentarze do niniejszej Instrukcji

Brak uwag