Warning!

Make sure you are in root@pod01-srv2 during these steps.

Configure LLDPd for adjacency

LLDP is a tool that was born as a standard from the CDP protocol. LLDP is a vendor-neutral link layer protocol (transmitted via L2 broadcasts ) used by devices to share identity and capabilities to each other. This makes it easier to identify device locations across networks.

LLDP is also available in servers and can interact with Cisco ACI to make it possible to see the adjacency location of servers in relation to ports in the ACI fabric. This relationship can assist you in the Contiv configuration because ACI can use this location information to remove the requirements to configure the location of compute hosts.

While it might seem a little confusing at this point of the lab, consider LLDP as a way to assist you in your Contiv deployment to configure ports in the ACI fabric to compute hosts. This is identical to the mechanism required to identify location in ACI with VMware vSphere integration.

Finally even if you don't use LLDP for the integration of Contiv to configure the access policies in ACI, having LLDP assist you with the ACI fabric as an operator. This provides you an easy way that you could script the locations of every device attached to the ACI fabric. ACI keeps a database of adjacencies that you can easily request and parse to get a list of CDP or LLDP entries of all ports in the ACI fabric. In all using LLDP is very useful for the network operator.

Step 1 - Add special repository for LLDPd

The best LLDPd package for integration with ACI is available on OpenSUSE repositories. You will add the following repository link to YUM such that it can pull the package and install easily.

pod01-srv2
1
# This is the copy group: 1
cd /etc/yum.repos.d/ wget http://download.opensuse.org/repositories/home:vbernat/RHEL_7/home:vbernat.repo

Step 2 - Install LLDPd

pod01-srv2
2
# This is the copy group: 2
yum -y install lldpd

Step 3 - Enable and Start LLDPd

After LLDPd is installed in the system, use systemctl to enable the daemon so that it starts after reboots and then start it to that it is enabled now.

pod01-srv2
3
# This is the copy group: 3
systemctl enable lldpd systemctl start lldpd

Step 4 - Check LLDP Neighbor

Now that LLDP is functional, you can get the neighbor list with the command lldpcli show neighbor.

pod01-srv2
4
# This is the copy group: 4
lldpcli show neighbor

The output of the command should show only one active neighbor relationship that is to the adjacent ACI FEX port that is used in the lab for the management port of the hosts.

Note: You might need to re-run the command above (waiting for LLDP packet to arrive)

pod01-srv2

# lldpcli show neighbor


    [root@pod01-srv1 ~]# lldpcli show neighbor
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface:    eth0, via: LLDP, RID: 2, Time: 0 day, 00:01:12
  Chassis:
    ChassisID:    mac 54:75:d0:21:0c:21
    SysName:      L3
    SysDescr:     topology/pod-1/node-203
    TTL:          120
    MgmtIP:       10.0.226.33
    Capability:   Bridge, on
    Capability:   Router, off
  Port:
    PortID:       local Eth111/1/32
    PortDescr:    topology/pod-1/paths-203/extpaths-111/pathep-[eth1/32]
  Unknown TLVs:
    TLV:          OUI: 00,01,42, SubType: 1, Len: 1 01
    TLV:          OUI: 00,01,42, SubType: 202, Len: 1 01
-------------------------------------------------------------------------------
Interface:    eth1, via: LLDP, RID: 1, Time: 0 day, 00:01:16
  Chassis:
    ChassisID:    mac 64:12:25:75:0e:3a
    SysName:      L2
    SysDescr:     topology/pod-1/node-202
    TTL:          120
    MgmtIP:       10.0.226.32
    Capability:   Bridge, on
    Capability:   Router, on
  Port:
    PortID:       local Eth1/32
    PortDescr:    topology/pod-1/paths-202/pathep-[eth1/32]
  Unknown TLVs:
    TLV:          OUI: 00,01,42, SubType: 1, Len: 1 00
    TLV:          OUI: 00,01,42, SubType: 201, Len: 1 01
    TLV:          OUI: 00,01,42, SubType: 216, Len: 2 00,00
    TLV:          OUI: 00,01,42, SubType: 215, Len: 2 4C,32
    TLV:          OUI: 00,01,42, SubType: 212, Len: 11 53,41,4C,31,38,31,34,50,54,42,55
    TLV:          OUI: 00,01,42, SubType: 214, Len: 11 4E,39,4B,2D,43,39,33,39,36,50,58
    TLV:          OUI: 00,01,42, SubType: 210, Len: 14 6E,39,30,30,30,2D,31,32,2E,31,28,31,68,29
    TLV:          OUI: 00,01,42, SubType: 206, Len: 11 41,43,49,20,46,61,62,72,69,63,31
    TLV:          OUI: 00,01,42, SubType: 202, Len: 1 01
    TLV:          OUI: 00,01,42, SubType: 211, Len: 2 0F,7F
    TLV:          OUI: 00,01,42, SubType: 205, Len: 2 00,01
    TLV:          OUI: 00,01,42, SubType: 203, Len: 4 00,00,00,CA
    TLV:          OUI: 00,01,42, SubType: 208, Len: 4 0A,09,F0,3A
    TLV:          OUI: 00,01,42, SubType: 207, Len: 123 01,0A,09,00,01,33,66,39,64,30,64
-------------------------------------------------------------------------------

   
© Copyright Cisco Systems 2017