Thursday, December 05, 2013

Link Layer Discovery Protocol (LLDP)

Introduction
The Cisco Discovery Protocol (CDP) is a device discovery protocol that runs over Layer 2 (the Data Link layer) on all Cisco-manufactured devices (routers, bridges, access servers, and switches). CDP allows network management applications to automatically discover and learn about other Cisco devices connected to the network.
To support non-Cisco devices and to allow for interoperability between other devices, the Cisco CRS Router also supports the IEEE 802.1AB LLDP. LLDP is also a neighbour discovery protocol that is used for network devices to advertise information about themselves to other devices on the network. This protocol runs over the Data Link Layer, which allows two systems running different network layer protocols to learn about each other.
LLDP supports a set of attributes that it uses to learn information about neighbour devices. These attributes have a defined format known as a Type-Length-Value (TLV). LLDP supported devices can use TLVs to receive and send information to their neighbours. Details such as configuration information, device capabilities, and device identity can be advertised using this protocol.
LLDP is a one-way protocol. The basic operation of LLDP consists of a device enabled for transmit of LLDP information sending periodic advertisements of information in LLDP frames to a receiving device. Devices are identified using a combination of the Chassis ID and Port ID TLVs to create an MSAP (MAC Service Access Point). The receiving device saves the information about a neighbour for a certain amount time specified in the TTL TLV, before ageing and removing the information.
There are a few LLDP timers and these are configurable:
·         Holdtime. This is the length of time that information from an LLDP packet should be held by the receiving device before aging and removing it. The default is 30 Seconds and is configurable between  0 and 65535 seconds. (The recommendation is to keep at default)
·         Reinit. This is the length of time to delay the initialisation of LLDP on an interface. The default is 2 seconds and is configurable between 2-5 seconds. (The recommendation is to keep at default)
·         Timer. This specifies the LLDP packet rate. The default is 30 seconds and is configurable between 5 and 65534 seconds. (The recommendation is to keep at default)
There are a few unsupported LLDP features, mainly:
·         LLDP-MED organizationally unique extension—However, interoperability still exists between other devices that do support this extension.
·         Tunneled neighbors, or neighbors more than one hop away.
·         LLDP TLVs cannot be disabled on a per-interface basis; However, certain optional TLVs can be disabled globally.
·         LLDP SNMP trap LLDPRemTablesChange
·         LLDP is NOT supported on Bundle interfaces. LLDP is supported on physical interfaces which are member of any bundle interface.
LLDP was introduced in XR on the CRS in release 4.2.3 and on the ASR9K in release 4.1.0, However LLDP is not supported on XR enabled 12K’s.
On a XR 12K, the software will let  you enter the configuration, but will bring up an error message when you try to commit it:
RP/0/8/CPU0:router#sh LLDP
Wed Dec  4 22:56:17.337 UTC
% LLDP is not enabled
RP/0/8/CPU0:router#conf t
Wed Dec  4 22:56:25.794 UTC
RP/0/8/CPU0:router(config)#LLDP
RP/0/8/CPU0:router(config-LLDP)#commit
Wed Dec  4 22:56:29.617 UTC

% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed' from this session to view the errors
RP/0/8/CPU0:router(config-LLDP)#show config failed
Wed Dec  4 22:56:37.805 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.


LLDP
!!% 'LLDP' detected the 'fatal' condition 'LLDP is not supported on this platform'
!
end

RP/0/8/CPU0:router(config-LLDP)#

Configuring LLDP


LLDP is disabled by default.
To check if LLDP is enabled use the command:
RP/0/RP1/CPU0:ROUTER#show LLDP
Fri Oct 25 00:59:44.004 EST
% LLDP is not enabled   <<<<<<<<<<<<<LLDP IS NOT ENABLED.
RP/0/RP1/CPU0:ROUTER#

If LLDP is enabled the output would be:

RP/0/RP1/CPU0:ROUTER#sh LLDP
Fri Oct 25 01:09:08.964 EST
Global LLDP information:
        Status: ACTIVE
        LLDP advertisements are sent every 30 seconds
        LLDP hold time advertised is 120 seconds
        LLDP interface reinitialisation delay is 2 seconds

To enable LLDP use the global command LLDP:
RP/0/RP1/CPU0:ROUTER#conf t
Fri Oct 25 01:08:34.221 EST
RP/0/RP1/CPU0:ROUTER(config)#LLDP
RP/0/RP1/CPU0:ROUTER(config-LLDP)#commit
Fri Oct 25 01:08:45.538 EST

This will enable LLDP on all supported interfaces for both transmit and receive directions. It will also enable the default timers as indicated above with the command ‘show LLDP’

To confirm what interfaces have been enabled with the command ‘LLDP’ use the command ‘show LLDP interface’:

RP/0/RP1/CPU0:ROUTER#show LLDP interface
Fri Oct 25 01:26:48.389 EST


GigabitEthernet0/2/1/0:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME


GigabitEthernet0/2/1/1:
        Tx: enabled
        Rx: enabled
        Tx state: INIT
        Rx state: WAIT PORT OPER


GigabitEthernet0/2/1/2:
        Tx: enabled
        Rx: enabled
        Tx state: INIT
        Rx state: WAIT PORT OPER


GigabitEthernet0/2/1/3:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME


GigabitEthernet0/2/1/4:
        Tx: enabled
        Rx: enabled
        Tx state: INIT
        Rx state: WAIT PORT OPER


TenGigE0/2/3/0:
        Tx: enabled
        Rx: enabled
        Tx state: INIT
        Rx state: WAIT PORT OPER


TenGigE0/2/0/0:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME


TenGigE0/2/0/0.101:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME


TenGigE0/2/0/0.102:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME


TenGigE0/2/0/0.103:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME
Etc

Disabling LLDP at interface level


If you are required to disable LLDP on any interfaces then you can override the default LLDP operation at interface level by disabling receive and/or transmit operations. (Remember LLDP is a one way protocol). For example:


RP/0/RP1/CPU0:ROUTER#sh LLDP int
Thu Dec  5 05:20:20.960 EST


GigabitEthernet0/2/1/0:
        Tx: enabled <<<<<<<<<<<<<<<<<<<<<<<<<
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME

RP/0/RP1/CPU0:ROUTER#conf t
Thu Dec  5 05:20:41.954 EST
RP/0/RP1/CPU0:ROUTER(config)#int GigabitEthernet0/2/1/0
RP/0/RP1/CPU0:ROUTER(config-if)#LLDP
RP/0/RP1/CPU0:ROUTER(config-LLDP)#receive disable
RP/0/RP1/CPU0:ROUTER(config-LLDP)#transmit disable
RP/0/RP1/CPU0:ROUTER(config-LLDP)#commit
Thu Dec  5 05:21:47.946 EST
RP/0/RP1/CPU0:ROUTER(config-LLDP)#
RP/0/RP1/CPU0:ROUTER#
RP/0/RP1/CPU0:ROUTER#
RP/0/RP1/CPU0:ROUTER#sh run int GigabitEthernet0/2/1/0
Thu Dec  5 05:21:55.889 EST
interface GigabitEthernet0/2/1/0
 description connect to puma-6509:9/37 for IXIA
 cdp
 LLDP
  receive disable
  transmit disable
 !
 negotiation auto
!

RP/0/RP1/CPU0:ROUTER#sh LLDP int
Thu Dec  5 05:22:20.366 EST


GigabitEthernet0/2/1/0:
        Tx: disabled <<<<<<<<<
        Rx: disabled           on the interface and this interface only.
        Tx state: INIT
        Rx state: INIT


Modifying LLDP timers


The  LLDP timers can be changed globally with the ‘lld’ command. The below examples shows the default values, the ranges and changing the LLDP advertising timer :
RP/0/RP1/CPU0:ROUTER#sh LLDP
Thu Dec  5 05:28:48.909 EST
Global LLDP information:
        Status: ACTIVE
        LLDP advertisements are sent every 30 seconds
        LLDP hold time advertised is 120 seconds
        LLDP interface reinitialisation delay is 2 seconds
RP/0/RP1/CPU0:ROUTER#conf t
Thu Dec  5 05:29:23.328 EST
RP/0/RP1/CPU0:ROUTER(config)#LLDP ?
  holdtime    Specify the holdtime (in sec) to be sent in packets
  reinit      Delay (in sec) for LLDP initialization on any interface
  timer       Specify the rate at which LLDP packets are sent (in sec)
  tlv-select  Selection of LLDP TLVs to disable
 
RP/0/RP1/CPU0:ROUTER(config)#LLDP holdtime ?
  <0-65535>  Length of time (in sec) that receiver must keep this packet
RP/0/RP1/CPU0:ROUTER(config)#LLDP reinit ?
  <2-5>  Delay (in sec) for LLDP initialization on any interface
RP/0/RP1/CPU0:ROUTER(config)#LLDP timer ?
  <5-65534>  Rate at which LLDP packets are sent (in sec)
RP/0/RP1/CPU0:ROUTER(config)#LLDP timer 25
RP/0/RP1/CPU0:ROUTER(config)#commit
Thu Dec  5 06:27:10.255 EST
RP/0/RP1/CPU0:ROUTER(config)#
RP/0/RP1/CPU0:ROUTER#sh LLDP
Thu Dec  5 06:27:15.362 EST
Global LLDP information:
        Status: ACTIVE
        LLDP advertisements are sent every 25 seconds <<<<
        LLDP hold time advertised is 120 seconds
        LLDP interface reinitialisation delay is 2 seconds
RP/0/RP1/CPU0:ROUTER#

 

Disabling LLDP TVLs


The default is that all TLVs (Type-Length-Values) are sent in LLDP packets. Certain TLV s are mandatory for LLDP operation. These are Chassis ID, Port ID and Time to Live. All other TLVs are optional and the transmission of them can be suppressed. The example below shows how to disable these TLVs:
RP/0/RP1/CPU0:ROUTER#conf t
Fri Oct 25 04:17:34.274 EST
RP/0/RP1/CPU0:ROUTER(config)#LLDP tlv-select ?
  management-address   Management Address TLV
  port-description     Port Description TLV
  system-capabilities  System Capabilities TLV
  system-description   System Description TLV
  system-name          System Name TLV
 
RP/0/RP1/CPU0:ROUTER(config)#LLDP tlv-select management-address ?
  disable  disable Management Address TLV
RP/0/RP1/CPU0:ROUTER(config)#LLDP tlv-select management-address dis
RP/0/RP1/CPU0:ROUTER(config)#LLDP tlv-select port-description  dis
RP/0/RP1/CPU0:ROUTER(config)#LLDP tlv-select system-capabilities dis
RP/0/RP1/CPU0:ROUTER(config)#LLDP tlv-select system-description dis
RP/0/RP1/CPU0:ROUTER(config)#LLDP tlv-select system-name  dis
RP/0/RP1/CPU0:ROUTER(config)#commit
Fri Oct 25 04:19:33.560 EST
RP/0/RP1/CPU0:ROUTER(config)#

Verifying LLDP


The following commands are useful for verifying your LLDP configuration:
Show LLDP entry’ This command displays detailed information about all LLDP neighbours with the * option, or a single neighbour by specifying the name of a specific neighbour. This command displays the far end interface, the name of the far end router, its software version and far end IP addresses.
RP/0/RP1/CPU0:ROUTER#show LLDP entry ?
  *     all LLDP neighbor entries
  WORD  Name of LLDP neighbor entry
RP/0/RP1/CPU0:ROUTER#

RP/0/RP1/CPU0:ROUTER#show LLDP entry *
Thu Dec  5 06:47:15.806 EST
Capability codes:
        (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
        (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other

------------------------------------------------
Local Interface: TenGigE0/7/0/0
Chassis id: 0017.94ba.5221
Port id: Te0/11/0/6
Port Description: TenGigE0/11/0/6
System Name: SL-BB3

System Description:
Cisco IOS XR Software, Version 4.3.2[Default]
Copyright (c) 2013 by Cisco Systems, Inc.

Time remaining: 1996488704 seconds
Hold Time: 120 seconds
System Capabilities: R
Enabled Capabilities: R
Management Addresses:
  IPv4 address: 10.35.35.1
  IPv6 address: ab00::10:35:35:1
Etc
‘show LLDP errors’ This command displays LLDP error and overflow statistics. You can use the optional ‘location’ key word to display information about LLDP neighbours for a specified location. For example:
RP/0/RP1/CPU0:ROUTER#show LLDP errors
Thu Dec  5 07:02:09.801 EST

LLDP errors/overflows:
        Total memory allocation failures: 0
        Total encapsulation failures: 0
        Total input queue overflows: 0
        Total table overflows: 0
RP/0/RP1/CPU0:ROUTER#

‘show LLDP interface’ As detailed with an example previously, this command displays all the interfaces enabled with LLDP and displays whether the transmission or receiving of LLDP packets is disabled or enabled as well as the Tx and Rx state.

‘show LLDP neighbors’ This command displays information about LLDP neighbours. You can use the default ‘detail’ option to receive all available information about the neighbour. For example:
RP/0/RP1/CPU0:ROUTER#sh LLDP neighbors
Thu Dec  5 07:13:56.906 EST
Capability codes:
        (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
        (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other

Device ID       Local Intf          Hold-time  Capability      Port ID
SL-BB3          Te0/7/0/0           120        R               Te0/11/0/6
SL-BB3          Te0/10/0/0          120        R               Te0/8/0/0
SL-BB3          Te0/10/0/1          120        R               Te0/8/0/1
SL-BB3          Te0/10/0/3          120        R               Te0/8/0/3
SL-BB3          Te1/1/0/1           120        R               Te0/11/0/2
SL-BB3          Te1/1/0/2           120        R               Te0/11/0/3

Total entries displayed: 6

RP/0/RP1/CPU0:ROUTER#
And with the detail command:

RP/0/RP1/CPU0:ROUTER#show LLDP neighbors detail
Thu Dec  5 07:15:01.656 EST
Capability codes:
        (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
        (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other

------------------------------------------------
Local Interface: TenGigE0/7/0/0
Chassis id: 0017.94ba.5221
Port id: Te0/11/0/6
Port Description: TenGigE0/11/0/6
System Name: SL-BB3

System Description:
Cisco IOS XR Software, Version 4.3.2[Default]
Copyright (c) 2013 by Cisco Systems, Inc.

Time remaining: 1610612736 seconds
Hold Time: 120 seconds
System Capabilities: R
Enabled Capabilities: R
Management Addresses:
  IPv4 address: 10.35.35.1
  IPv6 address: ab00::10:35:35:1



------------------------------------------------
Local Interface: TenGigE0/10/0/0
Chassis id: 0017.94ba.5221
Port id: Te0/8/0/0
Port Description: TenGigE0/8/0/0
System Name: SL-BB3

System Description:
Cisco IOS XR Software, Version 4.3.2[Default]
Copyright (c) 2013 by Cisco Systems, Inc.

Time remaining: 117 seconds
Hold Time: 120 seconds
System Capabilities: R
Enabled Capabilities: R
Management Addresses:
  IPv4 address: 10.35.35.1
  IPv6 address: ab00::10:35:35:1



------------------------------------------------
Local Interface: TenGigE0/10/0/1
Chassis id: 0017.94ba.5221
Port id: Te0/8/0/1
Port Description: TenGigE0/8/0/1
System Name: SL-BB3

System Description:
Cisco IOS XR Software, Version 4.3.2[Default]
Copyright (c) 2013 by Cisco Systems, Inc.

Time remaining: 92 seconds
Hold Time: 120 seconds
System Capabilities: R
Enabled Capabilities: R
Management Addresses:
  IPv4 address: 10.35.35.1
  IPv6 address: ab00::10:35:35:1



------------------------------------------------
Local Interface: TenGigE0/10/0/3
Chassis id: 0017.94ba.5221
Port id: Te0/8/0/3
Port Description: TenGigE0/8/0/3
System Name: SL-BB3

System Description:
Cisco IOS XR Software, Version 4.3.2[Default]
Copyright (c) 2013 by Cisco Systems, Inc.

Time remaining: 119 seconds
Hold Time: 120 seconds
System Capabilities: R
Enabled Capabilities: R
Management Addresses:
  IPv4 address: 10.35.35.1
  IPv6 address: ab00::10:35:35:1
Etc


‘show LLDP traffic’ displays the statistics for LLDP. For example:
RP/0/RP1/CPU0:ROUTER#show LLDP traffic
Thu Dec  5 07:17:35.520 EST

LLDP traffic statistics:
        Total frames out: 19182197
        Total entries aged: 71
        Total frames in: 388202
        Total frames received in error: 0
        Total frames discarded: 8
        Total TLVs discarded: 0
        Total TLVs unrecognized: 0
Total frames out is the number of LLDP advertisements sent from the device.
Total entries aged are the number of LLDP neighbor entries removed due to expiration of the hold time.
Total frames in is the number of LLDP advertisements received by the device.
Total frames received in error is the number of times the LLDP advertisements contained errors of any type.
Total frames discarded is the number of times the LLDP process discarded an incoming advertisement.
Total TLVs discarded is the number of times the LLDP process discarded a Type Length Value (TLV) from an LLDP frame.
Total TLVs unrecognized are the number of TLVs that could not be processed because the content of the TLV was not recognized by the device or the contents of the TLV were incorrectly specified.

‘clear LLDP’ This command resets LLDP traffic counters or neighbour information. Counters specifies that LLDP traffic counters are cleared and table specifies that information in the LLDP neighbour table is cleared. For example:
RP/0/RP1/CPU0:ROUTER#show LLDP traffic
Thu Dec  5 07:26:35.188 EST

LLDP traffic statistics:
        Total frames out: 19189347
        Total entries aged: 71
        Total frames in: 388310
        Total frames received in error: 0
        Total frames discarded: 8
        Total TLVs discarded: 0
        Total TLVs unrecognized: 0
RP/0/RP1/CPU0:ROUTER#
RP/0/RP1/CPU0:ROUTER#clear LLDP ?
  counters  Clear LLDP counters
  table     Clear and resize the LLDP table
RP/0/RP1/CPU0:ROUTER#clear LLDP counters
Thu Dec  5 07:26:45.698 EST
RP/0/RP1/CPU0:ROUTER#
RP/0/RP1/CPU0:ROUTER#show LLDP traffic
Thu Dec  5 07:26:49.587 EST

LLDP traffic statistics:
        Total frames out: 0
        Total entries aged: 0
        Total frames in: 1
        Total frames received in error: 0
        Total frames discarded: 0
        Total TLVs discarded: 0
        Total TLVs unrecognized: 0
RP/0/RP1/CPU0:ROUTER#

 

Debugging LLDP


There are a variety of LLDP debug commands:
RP/0/RP1/CPU0:ROUTER#debug LLDP ?
  all      All LLDP debugs
  errors   LLDP error information
  events   LLDP events
  packets  LLDP packet-related information
  tlvs     LLDP TLVs
  trace    LLDP trace information
  verbose  LLDP verbose information
The debug headings are self-explanatory, however as with all debugs, they may execute a lot of information and care should be taken when issuing any debug command.
For example, the output from ‘debug LLDP events:
RP/0/RP1/CPU0:ROUTER#sh logging | LC/0/2/CPU0:Oct 28 02:23:49.724 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.101 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:49.727 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.101 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:49.727 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:49.727 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.101 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:49.750 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.128 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:49.750 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.128 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:49.750 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:49.750 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.128 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:49.973 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.116 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:49.973 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.116 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:49.973 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:49.973 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.116 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:49.981 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.130 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:49.981 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.130 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:49.981 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:49.981 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.130 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:49.984 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.180 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:49.984 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.180 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:49.984 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:49.984 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.180 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:49.991 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Gi0/2/1/3 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:49.991 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Gi0/2/1/3 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:49.991 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:49.991 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Gi0/2/1/3 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.024 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.194 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.024 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.194 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.024 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.024 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.194 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.026 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.123 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.026 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.123 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.026 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.026 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.123 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.047 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.125 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.047 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.125 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.047 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.047 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.125 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.047 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.119 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.047 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.119 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.047 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.047 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.119 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.070 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.113 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.070 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.113 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.070 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.070 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.113 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.110 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.114 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.110 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.114 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.110 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.110 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.114 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.132 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.152 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.132 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.152 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.132 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.132 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.152 set to IDLE
LC/1/1/CPU0:Oct 28 02:23:50.138 : LLDP_agent[250]: EVENT[LLDP_timer_handler] Te1/1/0/11 TX TTR event...
LC/1/1/CPU0:Oct 28 02:23:50.139 : LLDP_agent[250]: EVENT[LLDP_set_tx_state] LLDP tx state on Te1/1/0/11 set to INFO FRAME
LC/1/1/CPU0:Oct 28 02:23:50.139 : LLDP_agent[250]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/1/1/CPU0:Oct 28 02:23:50.139 : LLDP_agent[250]: EVENT[LLDP_set_tx_state] LLDP tx state on Te1/1/0/11 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.172 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.138 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.172 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.138 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.172 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.172 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.138 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.177 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.120 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.177 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.120 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.177 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.177 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.120 set to IDLE
LC/0/2/CPU0:Oct 28 02:23:50.188 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.117 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.188 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.117 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.188 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.188 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.117 set to IDLE
LC/1/1/CPU0:Oct 28 02:23:50.194 : LLDP_agent[250]: EVENT[LLDP_timer_handler] Te1/1/0/10 TX TTR event...
iLC/0/2/CPU0:Oct 28 02:23:50.196 : LLDP_agent[248]: EVENT[LLDP_timer_handler] Te0/2/0/0.188 TX TTR event...
LC/0/2/CPU0:Oct 28 02:23:50.196 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.188 set to INFO FRAME
LC/0/2/CPU0:Oct 28 02:23:50.196 : LLDP_agent[248]: EVENT[LLDP_shim_pak_send] SPIO hand off
LC/0/2/CPU0:Oct 28 02:23:50.196 : LLDP_agent[248]: EVENT[LLDP_set_tx_state] LLDP tx state on Te0/2/0/0.188 set to IDLE
LC/1/1/CPU0:Oct 28 02:23:50.194 : LLDP_agent[250]: EVENT[LLDP_set_tx_state] LLDP tx state on Te1/1/0/10 set to INFO FRAME


Etc

0 Comments: