Brocade Network OS NETCONF Operations Guide v4.1.1 - Manual (Page 431)

Network OS NETCONF Operations Guide 399
53-1003231-02
Configuring LLDP global options
27
1. Issue the <edit-config> RPC to configure the <protocol> node in the
urn:brocade.com:mgmt:brocade-interface namespace.
2. Under the <protocol> node, include the <lldp> node element, which resides in the
urn:brocade.com:mgmt:brocade-lldp namespace.
3. Under the <lldp> node, include the <profile> node element.
4. Under the <profile> node, include the following leaf elements:
a. In the <profile-name> element, specify the name of the profile.
b. In the <description> element, specify a description for the profile.
c. In the <mode> element, include the delete operation in the element tag to allow
transmission and reception of LLDP frames. Otherwise, set the value to “tx” (for
transmission only) or “rx” (for reception only).
d. In the <hello> element, specify the transmission frequency of LLDP frames in seconds.
e. In the <multiplier> element, specify the hold time for receiving devices.
5. Under the <profile> node, include the <advertise> node.
6. Under the <advertise> node, include the <optional-tlv> node element to advertise the TLV.
7. Under the <optional-tlv> node, include leaf elements enabling the desired optional LLDP TLVs.
These TLVs may include:
• <management-address>
• <port-description>
• <system-capabilities>
• <adv-tlv-system-description>
• <adv-tlv-system-name>
8. Under the <advertise> node, include the following elements to advertise the LLPD
DCBX-related TLVs:
• <dot1-tlv>
• <dot3-tlv>
• <dcbx-tlv>
• <dcbx-fcoe-logical-link-tlv>
• <dcbx-fcoe-app-tlv>
• <dcbx-iscsi-app-tlv>
NOTE
Brocade recommends against advertising dot1.tlv and dot3.tlv LLDPs if your network contains
CNAs from non-Brocade vendors. This configuration may cause functionality problems.
The following example configures an LLDP profile named UK_LLDP_IT. It allows transmission and
reception of LLDP frames, provides a transmit frequency of 10 seconds, specifies a hold time of 20
seconds, and advertises optional and DCBX-related TLVs.
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="1114" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>