Administration Using MetaASSIST View
User Log file data is provided in clear ASCII text format. Support Log file data is provided in
ASCII format but may be scrambled. Each log has a size limit of 1MB and is cyclical; i.e.
when the limit is reached, the oldest 500KB of data are deleted automatically. Only users
with Admin privileges can access the Log files.
NOTE: The Audit log file size is 500KB (with 50% Threshold to flash overloaded file, 0.5MB and
0.25MB accordingly).
User Log files and Support Log files can be observed directly from ML via a Web browser.
For more details see Using Web Browser.
Syslog Client on ML
Each ML NE has a Syslog Client mechanism that operates according to RFC 3164. The
Syslog client on ML NE supports up to four Syslog Server Destinations, with configurable IP
and UDP ports. The Syslog client on ML NE can be configured per destination with three
types of events to be sent:
Audit (identical to events collected in AUDIT Log file on the ML)
TL1 Alarm
TL1 Commands (identical to events collected in COMMAND log file on the ML)
NOTE: TL1 Command log can be additionally controlled for level of details to be sent, see
Configuring the COMMAND log file (on page 14-9).
Syslog Content
For successful integration of ML Syslog Client with Syslog Server, the following format and
content of standard Syslog fields that appear in ML records should be taken into account.
Table 85: Syslog Fields Description
For CR/SA: 1
For CR/NSA: 1
Triggered upon REPT ALM
<AIDTYPE>.
Example of the record
content:
10.2.7.17 "ETH-
2:CL,LOS,NSA,10-05,13-
01-42,NEND,RCV:\"Loss Of
Signal\""
For MJ/SA: 2
For MJ/NSA: 2
For MN/SA: 3
For MN/NSA: 3
Triggered upon Clearance
of TL1 alarm.
Unsupported, as
duplicated in COMMAND
log
To Next Page