Maintenance Objects - Avaya G250 Maintenance Manual

Media gateways
Hide thumbs Also See for G250:
Table of Contents

Advertisement

Figure 14: CDR log example
G250-SLS(super)# show logging cdr file content
02/18/2005,10:46:35:CDR-Informational: 10:46 00:00 A 700 50029555 52001 v301
02/18/2005,10:45:46:CDR-Informational: 10:45 00:00 A 700 50029 52001 v301
02/18/2005,10:45:14:CDR-Informational: 10:45 00:00 A 700 52 52001 v301
02/18/2005,10:44:35:CDR-Informational: 10:44 00:00 A 700 445200 52001 v301
02/10/2005,13:20:23:CDR-Informational: 13:20 00:00 A 700 50029 52001 v301
02/10/2005,13:20:15:CDR-Informational: 13:20 00:00 A 700 50029 52000 v301
02/10/2005,13:20:05:CDR-Informational: 13:20 00:00 A 700 44 52000 v301
02/10/2005,13:19:59:CDR-Informational: 13:19 00:00 A 700 44500 52000 v301

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 port field in the Alarm and Error logs and as output of various
commands such as test board (see
Figure 15: Display of test board command
Maintenance Objects
on page 94).
Issue 1.1 June 2005
93

Advertisement

Table of Contents
loading

This manual is also suitable for:

G350

Table of Contents