• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

CDP, why?

Duncan Epping · Jan 31, 2008 ·

That’s what I thought at first, why do I need CDP(Cisco Discovery Protocol)? Well yesterday CDP proved to be an excellent option for troubleshooting weird networking problems. One of my customers replaced a faulty NIC and accidentally switched two network cables. One of these cables was part of an etherchannel, this caused all kind of strange routing / connection errors to the virtual machines. CDP was very useful because I could setup a remote connection to the customer and check which vmnic was connected to which port on the switch. So use CDP when in doubt!
Click on the blue cloud next to the vmnic name on the right:

This is the result:

(Screenshots taken from the RTFM Upgrade Guide.)

Related

Server 2.5, 3.0.x, 3.5, cdp, ESX, VMware

Reader Interactions

Comments

  1. Scott Lowe says

    31 January, 2008 at 21:19

    I was excited to see that VMware had added CDP to ESX 3.5, and for all the reasons you just discovered for yourself.

    Your timing, Duncan, is just unbelievable. I was just considering doing a brief write-up of CDP and why it’s beneficial and then I see this! This is probably the second or third time it’s happened. Keep up the good work.

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2025 · Log in