Configuring Dhcp Client Logging Messages; Configuring Lldp - Avaya G250 Administration

Configuring Ethernet ports

Configuring DHCP client logging messages

To configure DHCP client logging messages to the terminal:
1. Use the set logging session enable command to enable logging to the CLI terminal.
G350-001# set logging session enable
Done!
CLI-Notification: write: set logging session enable
2. Use the set logging session condition dhcpc command to view all DHCP client
messages of level Info and above.
G350-001# set logging session condition dhcpc Info
Done!
CLI-Notification: write: set logging session condition dhcpc Info
Note:
You can also enable logging messages to a log file or a Syslog server. For a full
Note:
description of logging on the G250/G350, see
page 103.

Configuring LLDP

IEEE 802.1AB Link Layer Discovery Protocol (LLDP) simplifies troubleshooting of enterprise
networks and enhances the ability of network management tools to discover and maintain
accurate network topologies in multi-vendor environments. It defines a set of advertisement
messages, called TLVs, a protocol for transmitting and receiving the advertisements, and a
method for storing the information contained in the received advertisements.
The LLDP protocol allows stations attached to a LAN to advertise information about the system
(such as its major capabilities and its management address) and information regarding the
station's point of attachment to the LAN (port ID and VLAN information) to other stations
attached to the same LAN. These can all be reported to management stations via IEEE-defined
SNMP MIBs.
LLDP information is transmitted periodically. The IEEE has defined a recommended
transmission rate of 30 seconds, but the transmission rate is adjustable. An LLDP device, after
receiving an LLDP message from a neighboring network device, stores the LLDP information in
an SNMP MIB. This information is valid only for a finite period of time after TLV reception. This
time is defined by the LLDP "Time to Live" TTL TLV value that is contained within the received
packet unless refreshed by a newly received TLV. The IEEE recommends a TTL value of 120
seconds, but you can change it if necessary. This ensures that only valid LLDP information is
stored in the network devices and is available to network management systems.
100 Administration for the Avaya G250 and Avaya G350 Media Gateways
Chapter 7: Configuring logging on