Managing Faults on Avaya Virtual Services Platform 7200 Series and 8000 Series Version 4.2.1
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: New in this release
- Chapter 3: Fault management fundamentals
- Chapter 4: Key Health Indicators using ACLI
- Chapter 5: Key Health Indicators using EDM
- Chapter 6: Link state change control using ACLI
- Chapter 7: Link state change control using EDM
- Chapter 8: RMON configuration using ACLI
- Chapter 9: RMON configuration using EDM
- Enabling RMON globally
- Enabling RMON on a port or VLAN
- Enabling RMON1 history
- Disabling RMON1 history
- Viewing RMON1 history statistics
- Creating an RMON1 alarm
- Creating an RMON1 port history alarm
- Viewing RMON1 alarms
- Deleting an RMON1 alarm
- Creating a default RMON1 event
- Creating a nondefault RMON1 event
- Viewing RMON1 events
- Viewing the RMON log
- Deleting an event
- Viewing the protocol directory
- Viewing the data source for protocol distribution statistics
- Viewing protocol distribution statistics
- Viewing the host interfaces enabled for monitoring
- Viewing address mappings
- Viewing the data source for host statistics
- Viewing network host statistics
- Viewing application host statistics
- Chapter 10: Viewing statistics using ACLI
- Chapter 11: Viewing statistics using EDM
- Chapter 12: Log and trap fundamentals
- Chapter 13: Log configuration using ACLI
- Chapter 14: Log configuration using EDM
- Chapter 15: SNMP trap configuration using ACLI
- Chapter 16: SNMP trap configuration using EDM
- Chapter 17: RMON alarm variables
- Glossary
can avoid this if you rename the log file to something other than the format used by system
messaging.
• If your TFTP server is a UNIX-based machine, files written to the server must already exist. For
example, you must create dummy files with the same names as your system logs. This action
is commonly performed by using the touch command (for example, touch bf860005.001).
Three parameters exist to configure the log file:
• the minimum acceptable free space available for logging
• the maximum size of the log file
• the percentage of free disk space the system can use for logging
Although these three parameters exist, you can only configure the maximum size of the log file. The
switch does not support the minimum size and percentage of free disk space parameters. The
internal flash must be less than 75% full for the system to log a file. If the internal flash is more than
75% full, logging to a file stops to prevent exhausting disk space.
Log file transfer using a wildcard filename
Log files from VOSS Release 4.1 and earlier were created without access permissions. However,
file transfers using SFTP require file permissions.
The command attribute WORD<1-99> [+/-] R allows you to change the permissions of a file.
To change permissions for log files created in VOSS 4.1 and earlier, use the attribute command
with the wildcard filename log.*. Using the command in the wildcard form attribute log.*
[+/-]R changes permissions for log files with names that begin with the characters “log.”.
Important:
You cannot use a wildcard pattern other than log.* for this command.
Log file transfer
June 2015 Managing Faults on Avaya VSP 7200 Series and 8000 Series 81
Comments on this document? infodev@avaya.com










