LLDP OpenConfig Translation

OcNOS DC : OpenConfig Command Reference : LLDP OpenConfig Translation

Enable Management Attributes

This XML configuration snippet is used to enable LLDP and all the management TLV attributes.

Release

This configuration was introduced in OcNOS version 5.0.

OpenConfig NETCONF Payload

Here is a sample OpenConfig NetConf Payload to enable LLDP and all the management TLV attributes.

</config>

</lldp>

OcNOS CLI command

The below CLI command is used to enable LLDP and all the management TLV attributes.

lldp run

lldp tlv-select basic-mgmt port-description

lldp tlv-select basic-mgmt system-name

lldp tlv-select basic-mgmt system-capabilities

lldp tlv-select basic-mgmt system-description

lldp tlv-select basic-mgmt management-address

OcNOS NETCONF Payload

Here is a sample OcNOS NetConf Payload to enable LLDP and all the management TLV attributes.

<global-tlv-control>

<global-basic-management>

<port-description>true</port-description>

<management-address>true</management-address>

<system-capabilities>true</system-capabilities>

<system-description>true</system-description>

<system-name>true</system-name>

</config>

</global-basic-management>

</global-tlv-control>

</config>

</global>

</lldp>

Validation with NETCONF get

Here is a NetConf validation response that provides detailed information about enabling LLDP and all the management TLV attributes.

</config>

<state>

<entries-aged-out>0</entries-aged-out>

<frame-discard>0</frame-discard>

<frame-out>0</frame-out>

<frame-in>0</frame-in>

</counters>

<system-name>OcNOS</system-name>

</state>

</lldp>

Restrictions

None

Configure chassis-id

This XML configuration snippet is used to set the locally assigned chassis name for the LLDP interface.

Release

This configuration was introduced in OcNOS version 5.0.

OpenConfig NETCONF Payload

Here is a sample OpenConfig NetConf Payload to set the locally assigned chassis name for the LLDP interface.

<chassis-id>host7028_AS5912-54X</chassis-id>

</config>

</lldp>

OcNOS CLI command

The below CLI command is used to set the locally assigned chassis name for the LLDP interface.

set lldp chassis locally-assigned host7028_AS5912-54X

OcNOS NETCONF Payload

Here is a sample OcNOS NetConf Payload to set the locally assigned chassis name for the LLDP interface.

<management-if>

<locally-assigned-chassis-id>host7028_AS5912-54X</locally-assigned-chassis-id>

</config>

</management-if>

</global>

</lldp>

Validation with NETCONF get

Here is a NetConf validation response that provides detailed information about setting the locally assigned chassis name for the LLDP interface.

<chassis-id>host7028_AS5912-54X</chassis-id>

<chassis-id-type>MAC_ADDRESS</chassis-id-type>

</config>

<state>

<entries-aged-out>0</entries-aged-out>

<frame-discard>0</frame-discard>

<frame-out>0</frame-out>

<frame-in>0</frame-in>

</counters>

<system-name>OcNOS</system-name>

<chassis-id>host7028_AS5912-54X</chassis-id>

<chassis-id-type>MAC_ADDRESS</chassis-id-type>

</state>

</lldp>

Restrictions

The chassis type MAC_ADDRESS is fixed and assumed by default.

Configure suppress advertisement

This XM configuration snippet is used to configure suppress TLV advertisement for one or more attributes.

Release

This configuration was introduced in OcNOS version 5.0.

OpenConfig NETCONF Payload

Here is a sample OpenConfig NetConf Payload to configure suppress TLV advertisement for one or more attributes.

<suppress-tlv-advertisement>SYSTEM_DESCRIPTION</suppress-tlv-advertisement>

</config>

</lldp>

OcNOS CLI command

The below CLI command is used to configure suppress TLV advertisement for one or more attributes.

no lldp tlv-select basic-mgmt system-description

OcNOS NETCONF Payload

Here is a sample OcNOS NetConf Payload to configure suppress TLV advertisement for one or more attributes.

<global-tlv-control>

<global-basic-management>

<system-description>false</system-description>

</config>

</global-basic-management>

</global-tlv-control>

</global>

</lldp>

Validation with NETCONF get

Here is a NetConf validation response that provides detailed information about configuring suppress TLV advertisement for one or more attributes

<suppress-tlv-advertisement

xmlns:oc-lldp-types="http://openconfig.net/yang/lldp/types">oc-lldp-types:SYSTEM_DESCRIPTION</suppress-tlv-advertisement>

<chassis-id>host7028_AS5912-54X</chassis-id>

<chassis-id-type>MAC_ADDRESS</chassis-id-type>

</config>

<state>

<entries-aged-out>0</entries-aged-out>

<frame-discard>0</frame-discard>

<frame-out>0</frame-out>

<frame-in>0</frame-in>

</counters>

<suppress-tlv-advertisement

xmlns:oc-lldp-types="http://openconfig.net/yang/lldp/types">oc-lldp-types:SYSTEM_DESCRIPTION</suppress-tlv-advertisement>

<system-name>OcNOS</system-name>

<chassis-id>host7028_AS5912-54X</chassis-id>

<chassis-id-type>MAC_ADDRESS</chassis-id-type>

</state>

</lldp>

Restrictions

By default, all basic tlvs are disabled and can be configured using this leaf. The default behavior is 'suppressed', so this leaf-list will only show up if at least one advertisement is enabled.

As OpenConfig and OcNOS have a reverse logic for the TLV (suppress vs enable), when the suppress is present on OpenConfig, the translation forces deletion of the attribute on the Ocnos side. This is equivalent to deleting a configuration that does not exist, in which case, an error may be returned.

Configure system name

This XMl configuration snippet is used to configure the system-name (hostname).

Release

This configuration was introduced in OcNOS version 5.0.

OpenConfig NETCONF Payload

Here is a sample OpenConfig NetConf Payload to configure the system-name (hostname).

<system-name>host7028</system-name>

</config>

</lldp>

OcNOS CLI command

This CLI command is used to configure the system-name (hostname).

hostname host7028

OcNOS NETCONF Payload

Here is a sample OcNOS NetConf Payload to configure the system-name (hostname).

<system-info xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-system">

</config>

</system-info>

Validation with NETCONF get

Here is a NetConf validation response that provides detailed information about configuring the system name (hostname).

Filter:

<system-info xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-system">

</config>

</system-info>

</filter>

</get>

Result:

</config>

</system>

Restrictions

The configuration is same as system hostname, so both are modified when applied.

The same restrictions as for system hostname apply:
Per RFC 952 and RFC 1123, a hostname string can contain only the special characters period (“.”) and hyphen (“-”). These special characters cannot be at the start or end of a hostname. The number of characters in the hostname must be between 1 and 63 characters.

Enable LLDP on an interface

This XML configuration snippet is used to enable LLDP on an interface.

Release

This configuration was introduced in OcNOS version 5.0.

OpenConfig NETCONF Payload

Here is a sample OpenConfig NetConf Payload to enable LLDP on an interface.

</config>

</interface>

</interfaces>

</lldp>

OcNOS CLI command

The blow CLI command is used to enable LLDP on an interface.

interface xe10

lldp-agent

set lldp enable txrx

OcNOS NETCONF Payload

Here is a sample OcNOS NetConf Payload to enable LLDP on an interface.

<agent>

<agent-type>default</agent-type>

<enable-tx-rx>txrx</enable-tx-rx>

<agent-type>default</agent-type>

</config>

</agent>

</interface>

</interfaces>

</lldp>

Validation with NETCONF get

Here is a NetConf validation response that provides detailed information about enabling LLDP on an interface.

</config>

</interface>

</interfaces>

</lldp>

Restrictions

When enabled = true, the configuration mode is tx-rx in OcNOS. When enabled = false, the OcNOS mode is set as rx-only.

LLDP get Attributes

The following attributes are read-only (runtime) for LLDP.

Counters

This command is used to display LLDP counters.

OpenConfig Filter

Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.

<state>

</state>

</lldp>

</filter>

OpenConfig get result

Here is a NetConf validation response that provides detailed information on the configuration and runtime.

<state>

<entries-aged-out>0</entries-aged-out>

<frame-discard>0</frame-discard>

<frame-out>0</frame-out>

<frame-in>1</frame-in>

</counters>

</state>

</lldp>

OcNOS get result

Here is the NetConf response in IPI datamodel representation.

<state>

<remote-ageouts>0</remote-ageouts>

<remote-drops>0</remote-drops>

<remote-deletes>0</remote-deletes>

<remote-inserts>1</remote-inserts>

</counters>

</state>

</global>

</lldp>

Restrictions

Only the counters remote-ageouts, remote-drops, remote-deletes, and remote-inserts are supported.

Interface counters

This command is used to display LLDP interface counters.

OpenConfig Filter

Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.

<state>

</state>

</interface>

</interfaces>

</lldp>

</filter>

OpenConfig get result

Here is a NetConf validation response that provides detailed information on the configuration and runtime.

</config>

<state>

<frame-out>14</frame-out>

</counters>

</state>

</interface>

</interfaces>

</lldp>

OcNOS get result

Here is the NetConf response in IPI datamodel representation.

<agent>

<agent-type>default</agent-type>

<state>

<tx-fast-init>2</tx-fast-init>

<tx-credit-max>9</tx-credit-max>

<message-fast-tx>222</message-fast-tx>

<message-tx-hold-multiplier>88</message-tx-hold-multiplier>

<message-tx-interval>999</message-tx-interval>

<reinit-delay>6</reinit-delay>

<tx-ttl>65535</tx-ttl>

<frames-out>14</frames-out>

</counters>

</state>

</transmit>

</agent>

</interface>

</interfaces>

</lldp>

Restrictions

Only the counter frame-out is supported.

Neighbors

This command is used to display neighbors.

OpenConfig Filter

Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

</filter>

OpenConfig get result

Here is a NetConf validation response that provides detailed information on the configuration and runtime.

</config>

<state><id>b86a.97be.193e</id><system-description>Hardware Model:EC_AS5912-54X</system-description>1<ttl>121</ttl><port-id-type>MAC_ADDRESS</port-id-type><port-description>xe1</port-description><port-id>b86a.97be.193e</port-id><chassis-id-type>NETWORK_ADDRESS</chassis-id-type><chassis-id>10.12.89.136</chassis-id><system-name>7031</system-name><management-address>b86a.97a7.253c</management-address><management-address-type>MAC Address</management-address-type></state>

<name>oc-lldp-types:MAC_BRIDGE</name>

<state>

<name>oc-lldp-types:MAC_BRIDGE</name>

</state>

</capability>

<name>oc-lldp-types:ROUTER</name>

<state>

<name>oc-lldp-types:ROUTER</name>

</state>

</capability>

</capabilities>

<custom-tlvs>

<tlv>

<oui-subtype>4</oui-subtype>

<state>

<oui-subtype>4</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>2</oui-subtype>

<state>

<oui-subtype>2</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

</custom-tlvs>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

OcNOS get result

Here is the NetConf response in IPI datamodel representation.

</config>

<name>oc-lldp-types:MAC_BRIDGE</name>

<state>

<name>oc-lldp-types:MAC_BRIDGE</name>

</state>

</capability>

<name>oc-lldp-types:ROUTER</name>

<state>

<name>oc-lldp-types:ROUTER</name>

</state>

</capability>

</capabilities>

<custom-tlvs>

<tlv>

<oui-subtype>4</oui-subtype>

<state>

<oui-subtype>4</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>2</oui-subtype>

<state>

<oui-subtype>2</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

</custom-tlvs>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

Neighbors name and description

This command is used to display neighbors' name and description.

OpenConfig Filter

Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.

<state>

<system-name/>

<id/>

<ttl/>

</state>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

</filter>

OpenConfig get result

Here is a NetConf validation response that provides detailed information on the configuration and runtime.

</config>

<state>

<system-description>HPE OfficeConnect Switch 1920S 24G 2SFP JL381A PD.01.05 Linux 3.6.5-ac96795c U-Boot 2012.10-00118-g3773021 (Oct 11 2016 - 15:39:54)</system-description>

<system-name>LAB1-SW13</system-name>

</state>

</neighbor>

</neighbors>

</interface>

</config>

<state>

<system-description>Hardware Model:EC_AS5912-54X</system-description>

<system-name>7031</system-name>

</state>

</neighbor>

</neighbors>

</interface>

</config>

<state>

<system-description>Hardware Model:EC_AS5912-54X</system-description>

<system-name>7031</system-name>

</state>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

OcNOS get result

Here is the NetConf response in IPI datamodel representation.

<agent>

<agent-type>default</agent-type>

<mac-address>b86a.97be.193e</mac-address>

<state>

<mac-address>b86a.97be.193e</mac-address>

<system-capabilties-enabled>Bridge Router</system-capabilties-enabled>

<system-capabilties>Bridge Router</system-capabilties>

<system-description>Hardware Model:EC_AS5912-54X</system-description>

<max-frame-size>1518</max-frame-size>

<operational-mau-type>54</operational-mau-type>

<auto-negotiation-capability>16</auto-negotiation-capability>

<auto-negotiation-support>1</auto-negotiation-support>

<management-vlan>0</management-vlan>

<vid-usage-digest>0</vid-usage-digest>

<pp-vlanid>0</pp-vlanid>

<port-vlan-id>0</port-vlan-id>

<port-sub-type>3</port-sub-type>

<port-description>xe1</port-description>

<port-id>b86a.97be.193e</port-id>

<chassis-id-type>5</chassis-id-type>

<chassis-component>10.12.89.136</chassis-component>

<system-name>7031</system-name>

<management-list>

<interface-number>10001</interface-number>

<interface-number-sub-type>ifindex</interface-number-sub-type>

<address-sub-type>MAC Address</address-sub-type>

</management-list>

</state>

</neighbor>

</agent>

</neighbors>

</interface>

</interfaces>

</lldp>

Neighbors chassis-id, type and ttl

This command is used to display neighbors' chassis-id, type and ttl.

OpenConfig Filter

Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.

<state>

<chassis-id/>

<chassis-id-type/>

<id/>

<ttl/>

</state>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

</filter>

OpenConfig get result

Here is a NetConf validation response that provides detailed information on the configuration and runtime.

</config>

<state>

<chassis-id>08f1.ea53.dbf0</chassis-id>

<chassis-id-type>MAC_ADDRESS</chassis-id-type>

</state>

</neighbor>

</neighbors>

</interface>

</config>

<state>

<chassis-id>b86a.97a7.253c</chassis-id>

<chassis-id-type>MAC_ADDRESS</chassis-id-type>

</state>

</neighbor>

</neighbors>

</interface>

</config>

<state>

<chassis-id>10.12.89.136</chassis-id>

<chassis-id-type>NETWORK_ADDRESS</chassis-id-type>

</state>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

OcNOS get result

Here is the NetConf response in IPI datamodel representation.

<agent>

<agent-type>default</agent-type>

<mac-address>b86a.97be.193e</mac-address>

<state>

<mac-address>b86a.97be.193e</mac-address>

<system-capabilties-enabled>Bridge Router</system-capabilties-enabled>

<system-capabilties>Bridge Router</system-capabilties>

<system-description>Hardware Model:EC_AS5912-54X</system-description>

<max-frame-size>1518</max-frame-size>

<operational-mau-type>54</operational-mau-type>

<auto-negotiation-capability>16</auto-negotiation-capability>

<auto-negotiation-support>1</auto-negotiation-support>

<management-vlan>0</management-vlan>

<vid-usage-digest>0</vid-usage-digest>

<pp-vlanid>0</pp-vlanid>

<port-vlan-id>0</port-vlan-id>

<port-sub-type>3</port-sub-type>

<port-description>xe1</port-description>

<port-id>b86a.97be.193e</port-id>

<chassis-id-type>5</chassis-id-type>

<chassis-component>10.12.89.136</chassis-component>

<system-name>7031</system-name>

<management-list>

<interface-number>10001</interface-number>

<interface-number-sub-type>ifindex</interface-number-sub-type>

<address-sub-type>MAC Address</address-sub-type>

</management-list>

</state>

</neighbor>

</agent>

</neighbors>

</interface>

</interfaces>

</lldp>

Neighbors port-id, type and description

This is used to display neighbors' port-id, port-id-type and port-description.

OpenConfig Filter

Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.

<state>

<port-id/>

<port-id-type/>

<port-description/>

<management-address/>

<management-address-type/>

</state>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

</filter>

OpenConfig get result

Here is a NetConf validation response that provides detailed information on the configuration and runtime.

</config>

<state>

<port-id>08f1.ea53.dbf2</port-id>

<port-id-type>MAC_ADDRESS</port-id-type>

<port-description>19</port-description>

</state>

</neighbor>

</neighbors>

</interface>

</config>

<state>

<port-id>b86a.97be.193f</port-id>

<port-id-type>MAC_ADDRESS</port-id-type>

<port-description>xe2</port-description>

</state>

</neighbor>

</neighbors>

</interface>

</config>

<state>

<port-id>b86a.97be.193e</port-id>

<port-id-type>MAC_ADDRESS</port-id-type>

<port-description>xe1</port-description>

</state>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

OcNOS get result

Here is the NetConf response in IPI datamodel representation.

<agent>

<agent-type>default</agent-type>

<mac-address>b86a.97be.193e</mac-address>

<state>

<mac-address>b86a.97be.193e</mac-address>

<system-capabilties-enabled>Bridge Router</system-capabilties-enabled>

<system-capabilties>Bridge Router</system-capabilties>

<system-description>Hardware Model:EC_AS5912-54X</system-description>

<max-frame-size>1518</max-frame-size>

<operational-mau-type>54</operational-mau-type>

<auto-negotiation-capability>16</auto-negotiation-capability>

<auto-negotiation-support>1</auto-negotiation-support>

<management-vlan>0</management-vlan>

<vid-usage-digest>0</vid-usage-digest>

<pp-vlanid>0</pp-vlanid>

<port-vlan-id>0</port-vlan-id>

<port-sub-type>3</port-sub-type>

<port-description>xe1</port-description>

<port-id>b86a.97be.193e</port-id>

<chassis-id-type>5</chassis-id-type>

<chassis-component>10.12.89.136</chassis-component>

<system-name>7031</system-name>

<management-list>

<interface-number>10001</interface-number>

<interface-number-sub-type>ifindex</interface-number-sub-type>

<address-sub-type>MAC Address</address-sub-type>

</management-list>

</state>

</neighbor>

</agent>

</neighbors>

</interface>

</interfaces>

</lldp>

Neighbors custom TLVs type/subtype

This command is used to display neighbors' custom TLVs type/subtype.

OpenConfig Filter

Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.

<custom-tlvs>

<tlv>

<state>

</state>

</tlv>

</custom-tlvs>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

</filter>

OpenConfig get result

Here is a NetConf validation response that provides detailed information on the configuration and runtime.

</config>

<state><id>08f1.ea53.dbf2</id><system-description>HPE OfficeConnect Switch 1920S 24G 2SFP JL381A PD.01.05 Linux 3.6.5-ac96795c U-Boot 2012.10-00118-g3773021 (Oct 11 2016 - 15:39:54)</system-description>0<ttl>120</ttl><port-id-type>MAC_ADDRESS</port-id-type><port-description>19</port-description><port-id>08f1.ea53.dbf2</port-id><chassis-id-type>MAC_ADDRESS</chassis-id-type><chassis-id>08f1.ea53.dbf0</chassis-id><system-name>LAB1-SW13</system-name><management-address>10.12.89.123</management-address><management-address-type>IP Address</management-address-type></state>

<name>oc-lldp-types:MAC_BRIDGE</name>

<state>

<name>oc-lldp-types:MAC_BRIDGE</name>

</state>

</capability>

<name>oc-lldp-types:ROUTER</name>

<state>

<name>oc-lldp-types:ROUTER</name>

<enabled>false</enabled>

</state>

</capability>

</capabilities>

<custom-tlvs>

<tlv>

<oui-subtype>4</oui-subtype>

<state>

<oui-subtype>4</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>2</oui-subtype>

<state>

<oui-subtype>2</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

</custom-tlvs>

</neighbor>

</neighbors>

</interface>

</config>

<state><id>b86a.97be.193f</id><system-description>Hardware Model:EC_AS5912-54X</system-description>1<ttl>121</ttl><port-id-type>MAC_ADDRESS</port-id-type><port-description>xe2</port-description><port-id>b86a.97be.193f</port-id><chassis-id-type>MAC_ADDRESS</chassis-id-type><chassis-id>b86a.97a7.253c</chassis-id><system-name>7031</system-name><management-address>b86a.97a7.253c</management-address><management-address-type>MAC Address</management-address-type></state>

<name>oc-lldp-types:MAC_BRIDGE</name>

<state>

<name>oc-lldp-types:MAC_BRIDGE</name>

</state>

</capability>

<name>oc-lldp-types:ROUTER</name>

<state>

<name>oc-lldp-types:ROUTER</name>

</state>

</capability>

</capabilities>

<custom-tlvs>

<tlv>

<oui-subtype>4</oui-subtype>

<state>

<oui-subtype>4</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>2</oui-subtype>

<state>

<oui-subtype>2</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

</custom-tlvs>

</neighbor>

</neighbors>

</interface>

</config>

<name>oc-lldp-types:MAC_BRIDGE</name>

<state>

<name>oc-lldp-types:MAC_BRIDGE</name>

</state>

</capability>

<name>oc-lldp-types:ROUTER</name>

<state>

<name>oc-lldp-types:ROUTER</name>

</state>

</capability>

</capabilities>

<custom-tlvs>

<tlv>

<oui-subtype>4</oui-subtype>

<state>

<oui-subtype>4</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>2</oui-subtype>

<state>

<oui-subtype>2</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

</custom-tlvs>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

OcNOS get result

Here is the NetConf response in IPI datamodel representation.

<agent>

<agent-type>default</agent-type>

<mac-address>b86a.97be.193e</mac-address>

<state>

<mac-address>b86a.97be.193e</mac-address>

<pp-vlanid>0</pp-vlanid>

</state>

</neighbor>

</agent>

</neighbors>

</interface>

</interfaces>

</lldp>

Neighbors custom TLVs

This command is used to display neighbors' custom TLVs.

OpenConfig Filter

Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.

<custom-tlvs>

<tlv>

</tlv>

</custom-tlvs>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

</filter>

OpenConfig get result

Here is a NetConf validation response that provides detailed information on the configuration and runtime.

</config>

<name>oc-lldp-types:MAC_BRIDGE</name>

<state>

<name>oc-lldp-types:MAC_BRIDGE</name>

</state>

</capability>

<name>oc-lldp-types:ROUTER</name>

<state>

<name>oc-lldp-types:ROUTER</name>

</state>

</capability>

</capabilities>

<custom-tlvs>

<tlv>

<oui-subtype>4</oui-subtype>

<state>

<oui-subtype>4</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>2</oui-subtype>

<state>

<oui-subtype>2</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

</custom-tlvs>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

OcNOS get result

Here is the NetConf response in IPI datamodel representation.

<agent>

<agent-type>default</agent-type>

<mac-address>b86a.97be.193e</mac-address>

<state>

<mac-address>b86a.97be.193e</mac-address>

<port-vlan-id>0</port-vlan-id>

</state>

</neighbor>

</agent>

</neighbors>

</interface>

</interfaces>

</lldp>

Neighbors capabilities

This command is used to display neighbors' capabilities.

OpenConfig Filter

Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.

<name/>

</capability>

</capabilities>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

</filter>

OpenConfig get result

Here is a NetConf validation response that provides detailed information on the configuration and runtime.

</config>

<state><id>b86a.97be.193e</id><system-description>Hardware Model:EC_AS5912-54X</system-description>1<ttl>121</ttl><port-id-type>MAC_ADDRESS</port-id-type><port-description>xe1</port-description><port-id>b86a.97be.193e</port-id><chassis-id-type>NETWORK_ADDRESS</chassis-id-type><chassis-id>10.12.89.136</chassis-id><system-name>7031</system-name><management-address>b86a.97be.193e</management-address><management-address-type>MAC Address</management-address-type></state>

<name>oc-lldp-types:MAC_BRIDGE</name>

<state>

<name>oc-lldp-types:MAC_BRIDGE</name>

</state>

</capability>

<name>oc-lldp-types:ROUTER</name>

<state>

<name>oc-lldp-types:ROUTER</name>

</state>

</capability>

</capabilities>

<custom-tlvs>

<tlv>

<oui-subtype>4</oui-subtype>

<state>

<oui-subtype>4</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>4</oui-subtype>

<state>

<oui-subtype>4</oui-subtype>

<value>Rapid-Spanning-Tree-Protocol</value>

</state>

</tlv>

<tlv>

<oui-subtype>2</oui-subtype>

<state>

<oui-subtype>2</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>1</oui-subtype>

<state>

<oui-subtype>1</oui-subtype>

</state>

</tlv>

<tlv>

<oui-subtype>3</oui-subtype>

<state>

<oui-subtype>3</oui-subtype>

<value>1default</value>

</state>

</tlv>

</custom-tlvs>

</neighbor>

</neighbors>

</interface>

</interfaces>

</lldp>

OcNOS get result

Here is the NetConf response in IPI datamodel representation.

<agent>

<agent-type>default</agent-type>

<mac-address>b86a.97be.193e</mac-address>

<state>

<mac-address>b86a.97be.193e</mac-address>

<port-vlan-id>0</port-vlan-id>

</state>

</neighbor>

</agent>

</neighbors>

</interface>

</interfaces>

</lldp>