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

http://www.cisco.com/en/US/partner/docs/routers/crs/software/crs_r4.3/interfaces/command/reference/b_interfaces_cr43xcrs_chapter_0100.html#wp3786135060

‘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#

http://www.cisco.com/en/US/partner/docs/routers/crs/software/crs_r4.3/interfaces/command/reference/b_interfaces_cr43xcrs_chapter_0100.html#wp1222064210

‘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.

http://www.cisco.com/en/US/partner/docs/routers/crs/software/crs_r4.3/interfaces/command/reference/b_interfaces_cr43xcrs_chapter_0100.html#wp1222064210

‘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

http://www.cisco.com/en/US/partner/docs/routers/crs/software/crs_r4.3/interfaces/command/reference/b_interfaces_cr43xcrs_chapter_0100.html#wp4078259891

‘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.

http://www.cisco.com/en/US/partner/docs/routers/crs/software/crs_r4.3/interfaces/command/reference/b_interfaces_cr43xcrs_chapter_0100.html#wp3208752942

‘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#

http://www.cisco.com/en/US/partner/docs/routers/crs/software/crs_r4.3/interfaces/command/reference/b_interfaces_cr43xcrs_chapter_0100.html#wp1663846998

 

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

Amazing Wallpaper

Linux Mint Wallpaper

Rare Pic of Amazing Talents

Don I Hindi Movie Stills

Make USB bootable for Windows 7 & Vista

Dual Boot setup

Question:

What is the need for having a dual OS in a PC? For instance, if I have installed both Win XP and Win 98, and I browse in Win 98, are there chances of a virus attack?

With regard to my system, of late I have been facing this problem: after I surf for some time, the name of a virus is displayed.

I have tried to heal it with AVG antivirus and the PC starts rebooting automatically. Before shutting down, it also displays the system restore screen.

I also have not been able to access the task manager. My PC time also keeps getting changed to some random time, but the date is correct. Please suggest a solution.

Answer:

If more than one person is using a particular computer,and each one has a different preference of OS, then more than one OS is installed. Thus each one's preference is met.

Dual OS installation happens mostly with regard to home PCs. The other scenario is if you want to evaluate a new OS version you can install the new one along with the existing one. Once you get familiar with the new OS and are satisfied with the features, you can migrate entirely to the new OS.

If it does not suit your requirements, the new version of OS can be uninstalled.

The recommended practice when installing dual OS is to install the second OS in a different partition or in a second hard disk if available.

This will protect your existing working OS. If at any point of time one OS crashes or suffers a virus attack it is possible to boot from the other OS and do the recovery of the infected OS or retrieve important data from it.

If Windows XP and Windows 98 are installed in a single computer it is advisable to browse the Internet from XP. Windows XP has more features compared to Win 98 for Internet browsing. Windows XP has a firewall installed, which will protect the computer from unauthorised network access.

As for the second part of your query, it looks like your computer has been infected by viruses such as Sasser or Blaster. These are viruses that get the PC rebooting automatically.

To remove them, you need to first install the latest service packs and the Windows updates.

Without the service packs or Windows updates, the antivirus programs (removal tools) will not be successful. Separate virus removal tools are available for Sasser worm and Blaster worms.

For Sasser worm, you can download the tool (FxSasser.exe) from this URL: http://www.symantec.com/security_response/writeup.jsp?docid=2004-050114-1706-99.

For more information about the Blaster worm removal tool, please look up this URL: http://www.symantec.com/security_response/writeup.jsp?docid=2003-081119-5051-99

System Restore in XP

Question:

I`m using a Dell desktop machine loaded with Windows XP with latest service packs and virus definitions. I had earlier used Windows 2000 and am not familiar with Windows XP. My friends keep talking of a feature available in Windows XP called system restore. Please explain what it is and in which context it could be useful.

Answer:

System Restore is a new feature in Windows XP. This is useful to restore the computer to an earlier state, before a system or application crash, without losing the data that was created before the crash and after the restoration point. To put it more simply: Imagine there is a change in the application or system, say some new drivers installed. We have saved some data after the change. At some point of time, we face some problem in the computer's functionality due to this new application or system change. We want to go back to the earlier state and also need the data. This is possible through system restore.

System Restore can be opened from Start -{gt} Programs -{gt} Accessories -{gt} System Tools -{gt} System Restore.

As one opens it, the system will prompt the user whether to Restore to an earlier point or create a Restore Point.

The system will monitor the system and application files. It identifies the changes made and creates a system restore point. By default, it will be created daily and at the time of new driver installation or application configuration changes. When we create a system restore point, it will prompt for a description to be given. We can give a suitable description so that it will be useful at some later date to identify the status of the computer. It can be before a new application installation and changes made to the existing one. This description is displayed when we do a restore to an earlier point.

By default, Windows XP installation will enable system restore in all the disk partitions. In each partition, a maximum of 12 per cent of its size is set for System restore. Selecting the System Restore Settings in the System Restore GUI can change this. System restore can be turned off in selected drives or on all the drives. But it is not recommended to do so.

Sun's new Java promises $US30 Internet cellphone - An old stuff

Contributed by Stuart Corner                                                                   Wednesday, 09 May 2007

Sun Microsystems has unveiled a new version of its Java cellphone software saying it will enable the manufacture of Internet capable cellphones for less than $US50 and positioning such devices as the means of bringing the Internet to developing countries.

{mosloadposition stuart}At the JavaOne conference in San Francisco, Rich Green, Sun Microsystems' executive vice president, software previewed a mobile phone prototype with a rich, graphical interface, made possible by JavaFX

Mobile. Sun CEO, Jonathan Schwarz, was reported saying he believed such phones could be sold for $US30-$US50.

Sun's announcement quoted Dr Djibril Diallo, director of the United Nations New York Office of Sport for Development

and Peace, and chair of the UN Youth Summit series, offering his support for Sun's technology for developing countries

by saying: "Bringing the Internet to people through mobile handsets can greatly expand access, and it is imperative that

the technology industry continues to innovate to make that a reality worldwide."

This would suggest the devices as a possible alternative to the One Laptop per Child initiative which aims to deliver low

cost computers to developing countries, but as iTWire reported recently the $US100 target price keeps receding.

Sun also previewed JavaFX Script, a new scripting language targeted at creative professionals, which it claims "will help

to radically simplify the process of creating and distributing interactive content that spans all Java technology enabled

platforms, from handsets to set tops, laptops to dashboards."

According to Green, "With JavaFX, Sun is leveraging the security and pervasiveness of the world's most widely deployed

technology platform to allow creative professionals to easily author and deliver on any device. This is a major step

towards helping consumers access the best content on the Internet from every device and a significant opportunity for

Sun and its partners to deliver a whole new line of products."

JavaFX Script applications will run on any JavaSE technology-based platform including all of the upcoming JavaFX

software systems for mobile handsets, TVs and other embedded applications from automobiles to game systems. Sun

claims that JavaFX Script is unique in providing close integration with Java components that run on the server or the

client, resulting in a richer end-to-end experience.

All JavaFX software will be available free via the GNU General Public License (GPL) license.{moscomment}

Courtesy: iTWire http://www.itwire.com.au Powered by Joomla! Generated: 10 May, 2007, 20:57

Google Culture

Some old screen shots

Google Old Logos

Google says - Our Philosophy

Never settle for the best

"The perfect search engine," says Google co-founder Larry Page, "would understand exactly what you mean and give back exactly what you want." Given the state of search technology today, that's a far-reaching vision requiring research, development and innovation to realize. Google is committed to blazing that trail. Though acknowledged as the world's leading search technology company, Google's goal is to provide a much higher level of service to all those who seek information, whether they're at a desk in Boston, driving through Bonn, or strolling in Bangkok.

---

---

• The interface is clear and simple.

• Pages load instantly.

• Placement in search results is never sold to anyone.

• Advertising on the site must offer relevant content and not be a distraction.

To that end, Google has persistently pursued innovation and pushed the limits of existing technology to provide a fast, accurate and easy-to-use search service that can be accessed from anywhere. To fully understand Google, it's helpful to understand all the ways in which the company has helped to redefine how individuals, businesses and technologists view the Internet.

Ten things Google has found to be true

1. Focus on the user and all else will follow.

From its inception, Google has focused on providing the best user experience possible. While many companies claim to put their customers first, few are able to resist the temptation to make small sacrifices to increase shareholder value. Google has steadfastly refused to make any change that does not offer a benefit to the users who come to the site:

By always placing the interests of the user first, Google has built the most loyal audience on the web. And that growth has come not through TV ad campaigns, but through word of mouth from one satisfied user to another.

2. It's best to do one thing really, really well.

Google does search. With one of the world's largest research groups focused exclusively on solving search problems, we know what we do well, and how we could do it better. Through continued iteration on difficult problems, we've been able to solve complex issues and provide continuous improvements to a service already considered the best on the web at making finding information a fast and seamless experience for millions of users. Our dedication to improving search has also allowed us to apply what we've learned to new products, including Gmail, Google Desktop, and Google Maps. As we continue to build new products* while making search better, our hope is to bring the power of search to previously unexplored areas, and to help users access and use even more of the ever-expanding information in their lives.

3. Fast is better than slow.

Google believes in instant gratification. You want answers and you want them right now. Who are we to argue? Google may be the only company in the world whose stated goal is to have users leave its website as quickly as possible. By fanatically obsessing on shaving every excess bit and byte from our pages and increasing the efficiency of our serving environment, Google has broken its own speed records time and again. Others assumed large servers were the fastest way to handle massive amounts of data. Google found networked PCs to be faster. Where others accepted apparent speed limits imposed by search algorithms, Google wrote new algorithms that proved there were no limits. And Google continues to work on making it all go even faster.

4. Democracy on the web works.

Google works because it relies on the millions of individuals posting websites to determine which other sites offer content of value. Instead of relying on a group of editors or solely on the frequency with which certain terms appear, Google ranks every web page using a breakthrough technique called PageRank™. PageRank evaluates all of the sites linking to a web page and assigns them a value, based in part on the sites linking to them. By analyzing the full structure of the web, Google is able to determine which sites have been "voted" the best sources of information by those most interested in the information they offer. This technique actually improves as the web gets bigger, as each new site is another point of information and another vote to be counted.

5. You don't need to be at your desk to need an answer.

The world is increasingly mobile and unwilling to be constrained to a fixed location. Whether it's through their PDAs, their wireless phones or even their automobiles, people want information to come to them. Google's innovations in this area include Google Number Search, which reduces the number of keypad strokes required to find data from a web-enabled cellular phone and an on-the-fly translation system that converts pages written in HTML to a format that can be read by phone browsers. This system opens up billions of pages for viewing from devices that would otherwise not be able to display them, including Palm PDAs and Japanese i-mode, J-Sky, and EZWeb devices. Wherever search is likely to help users obtain the information they seek, Google is pioneering new technologies and offering new solutions.

6. You can make money without doing evil.

Google is a business. The revenue the company generates is derived from offering its search technology to companies and from the sale of advertising displayed on Google and on other sites across the web. However, you may have never seen an ad on Google. That's because Google does not allow ads to be displayed on our results pages unless they're relevant to the results page on which they're shown. So, only certain searches produce sponsored links above or to the right of the results. Google firmly believes that ads can provide useful information if, and only if, they are relevant to what you wish to find.

Google has also proven that advertising can be effective without being flashy. Google does not accept pop-up advertising, which interferes with your ability to see the content you've requested. We've found that text ads (AdWords) that are relevant to the person reading them draw much higher clickthrough rates than ads appearing randomly. Google's maximization group works with advertisers to improve clickthrough rates over the life of a campaign, because high clickthrough rates are an indication that ads are relevant to a user's interests. Any advertiser, no matter how small or how large, can take advantage of this highly targeted medium, whether through our self-service advertising program that puts ads online within minutes, or with the assistance of a Google advertising representative.

Advertising on Google is always clearly identified as a "Sponsored Link." It is a core value for Google that there be no compromising of the integrity of our results. We never manipulate rankings to put our partners higher in our search results. No one can buy better PageRank. Our users trust Google's objectivity and no short-term gain could ever justify breaching that trust.

Thousands of advertisers use our Google AdWords program to promote their products; we believe AdWords is the largest program of its kind. In addition, thousands of web site managers take advantage of our Google AdSense program to deliver ads relevant to the content on their sites, improving their ability to generate revenue and enhancing the experience for their users.

7. There's always more information out there.

Once Google had indexed more of the HTML pages on the Internet than any other search service, our engineers turned their attention to information that was not as readily accessible. Sometimes it was just a matter of integrating new databases, such as adding a phone number and address lookup and a business directory. Other efforts required a bit more creativity, like adding the ability to search billions of images and a way to view pages that were originally created as PDF files. The popularity of PDF results led us to expand the list of file types searched to include documents produced in a dozen formats such as Microsoft Word, Excel and PowerPoint. For wireless users, Google developed a unique way to translate HTML formatted files into a format that could be read by mobile devices. The list is not likely to end there as Google's researchers continue looking into ways to bring all the world's information to users seeking answers.

8. The need for information crosses all borders.

Though Google is headquartered in California, our mission is to facilitate access to information for the entire world, so we have offices around the globe. To that end we maintain dozens of Internet domains and serve more than half of our results to users living outside the United States. Google search results can be restricted to pages written in more than 35 languages according to a user's preference. We also offer a translation feature to make content available to users regardless of their native tongue and for those who prefer not to search in English, Google's interface can be customized into more than 100 languages. To accelerate the addition of new languages, Google offers volunteers the opportunity to help in the translation through an automated tool available on the Google.com website. This process has greatly improved both the variety and quality of service we're able to offer users in even the most far flung corners of the globe.

9. You can be serious without a suit.

Google's founders have often stated that the company is not serious about anything but search. They built a company around the idea that work should be challenging and the challenge should be fun. To that end, Google's culture is unlike any in corporate America, and it's not because of the ubiquitous lava lamps and large rubber balls, or the fact that the company's chef used to cook for the Grateful Dead. In the same way Google puts users first when it comes to our online service, Google Inc. puts employees first when it comes to daily life in our Googleplex headquarters. There is an emphasis on team achievements and pride in individual accomplishments that contribute to the company's overall success. Ideas are traded, tested and put into practice with an alacrity that can be dizzying. Meetings that would take hours elsewhere are frequently little more than a conversation in line for lunch and few walls separate those who write the code from those who write the checks. This highly communicative environment fosters a productivity and camaraderie fueled by the realization that millions of people rely on Google results. Give the proper tools to a group of people who like to make a difference, and they will.

10. Great just isn't good enough.

Always deliver more than expected. Google does not accept being the best as an endpoint, but a starting point. Through innovation and iteration, Google takes something that works well and improves upon it in unexpected ways. Search works well for properly spelled words, but what about typos? One engineer saw a need and created a spell checker that seems to read a user's mind. It takes too long to search from a WAP phone? Our wireless group developed Google Number Search to reduce entries from three keystrokes per letter to one. With a user base in the millions, Google is able to identify points of friction quickly and smooth them out. Google's point of distinction however, is anticipating needs not yet articulated by our global audience, then meeting them with products and services that set new standards. This constant dissatisfaction with the way things are is ultimately the driving force behind the world's best search engine.