Maintenance Objects - Avaya G350 Maintenance Manual

Execute reset system 4
In order to force Media Gateways and IP endpoints to re-register with the primary server, execute a
system 4 command on each media gateway containing an LSP, thus forcing any media gateways and IP
endpoints registered to the LSP to search for and re-register with the primary server. The expectation is
that these endpoints will correctly perform the search and find the primary server; however, there is no
guarantee that this will be the result.
Shut down Communication Manager on every LSP
The only way to be certain that media gateways and endpoints re-register with the primary server is to
shut down Communication Manager on every LSP in the network, using the Linux command
Afterward, the primary server SAT commands
whether all the network endpoints re-registered with the primary server. The Linux command
sent to each LSP will then restart Communication Manager on each of those platforms.

Maintenance Objects

The maintenance subsystem is partitioned into separate entities called Maintenance Objects (MOs). A
maintenance object can be:
•
An individual Media Module
•
A hardware component that is part of a Media Module
•
An entire subsystem
•
A set of monitors
•
A process (or set of processes)
•
A combination of processes and hardware
"Maintenance names" are recorded in the Error and Alarm logs. Individual copies of an MO are assigned
an address that defines the MO's physical location in the system when applicable. These locations display
as the field in the Alarm and Error logs and as output of various commands such as
port
Figure 10, Display of test board command,
Maintenance of the Avaya G350 Media Gateway
June 2004
Avaya Communication Manager controlled maintenance
list media-gateway or status media-gateway
on page 70).
Maintenance Objects
reset
stop -acfn .
can verify
start -ac
(see
test board
69