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
continues to create a new log file with incremental sequence number on the internal flash for
logging.
Log file transfer
The system logs contain important information for debugging and maintaining the switch. After the
current log file reaches the configured maximum size, the system creates a new log file for logging.
The system transfers old log files to a remote host. You can configure up to 10 remote hosts, which
creates long-term backup storage of your system log files.
Of the 10 configured remote hosts, 1 is the primary host and the other 9 are redundant. Upon
initiating a transfer, system messaging attempts to use host 1 first. If host 1 is not reachable, system
messaging tries hosts 2 to 10.
If log file transfer is unsuccessful, the system keeps the old log files on internal flash. The system
attempts to transfer old log files after the new log file reaches the configured maximum size. The
system also attempts to transfer old log files periodically (once in one hundred log writes) if the disk
space on the flash is more than 75% full.
You can log system log messages to external system log hosts with both IPv4 and IPv6 addresses
with no difference in functionality or configuration.
With enhanced secure mode enabled, authorized users can use SFTP to transfer files to a remote
server with the content encrypted.
You can specify the following information to configure the transfer criteria:
• The maximum size of the log file.
• The IP address of the remote host.
• The name prefix of the log file to store on the remote host.
The system appends a suffix of .xxxxxxxx.sss to the file name. The first six characters of the
suffix contain the last three bytes of the chassis base MAC address. The next two characters
are 01. The last three characters (sss) denote the sequence number of the log file. For
example, if you configure the name prefix as mylog, a possible file name is mylog.
90000001.001.
• The user name and password, if using File Transfer Protocol (FTP) for file transfer. Use the
following commands to configure the user name and password:
boot config host user WORD<0–16>
boot config host password WORD<0–16>
Be aware of the following restrictions to transfer log files to a remote host:
• The remote host IP address must be reachable.
• If you transfer a log file from a host to the system, (for example, to display it with a show
command), rename the log file. Failure to rename the log file can cause the system to use the
recently transferred file as the current log, if the sequence number in the extension is higher
than the current log file. For example, if bf860005.002 is the current log file and you transfer
bf860005.007 to the system, the system logs future messages to the bf860005.007 file. You
Log and trap fundamentals
80 Managing Faults on Avaya VSP 7200 Series and 8000 Series June 2015
Comments on this document? infodev@avaya.com










