Re: [IM-Talk] Wish List

[Jakob Peterh�nsel]

Hi,

On 02/06/2005, at 1:07, David Fernandes wrote:

CDP discovery via a seed device with a filter setting against the hostname or ip so only certain devices can be displayed

per map.


domain names that contain net would pickup B.net, C.net, D.net.

So start with seed A.net. Has cdp neighbors B.net, C.net, D.net, E.com. A CDP discovery via that seed with a filter on

CDP messages contain specific information about the CSS, such as:

Device ID (CSS base MAC address)
IP address (CSS management port IP address)
Ethernet port ID name
CSS functional capability flag (Router, Transparent Bridge, or Switch)
CSS software version
CSS platform


Default CDP broadcast is done every 60 sec.

Well, the CDP system does not contain .net or .com info, it contains a very basic information about any CDP-enabled neibour on an active interface. Cisco documentation has this to say: Holdtime is default set to 180 sec. so at any given time you will be able to do a 'show cdp nei' to get a list of devices the host has seen broadcasts from during the last 3 minutes. You will also see double enties for neibours that have changed name during this periode.

Also, if cdp could only pickup active neighbors and not display all the interfaces of a switch device that are cdp capable.

Or at least the ability to easily hide these interfaces.

Add the the Wish List:
Preference to Initially Hide LINK DOWN interfaces discovered.
Preference to Initially Hide ADMIN DOWN interfaces discovered.

This will happen automatic, as CDP does not broadcast an interface list, it broadcasts something like 'Hi, I'm device ABC and you're connected to my interface called FastEthernet0/1. My management IP is 1.1.1.1 on VLAN 901'. It's then up to the device in the receiving end to make a list of devices it has discovered on each interface. Normally you will only see One pr. interface, unless you swapped cables during the last 180 sec. or changed name on the remote device.

Finally, if the interface info could be displayed cleanly on the map. So for discovery on A.net you could possibly see on

the map:

B - Gi0/1 ---- Gi1/2 - A - Gi1/1 ---- Gi0/1 - C
                       |
                     Gi1/3
                       |
                       |
                       |
                     Gi0/1
                       |
                       D

Device_A#show cdp nei


Device_B#show cdp nei




Hope it makes sense..  ;-)

    Jakob Peterh�nsel

"Tell me why, don't we try, not to break our hearts
  and make it so hard for our selfs"
P.S.B. 1987

Email:     [EMAIL PROTECTED]
AIM:         Marook
Phone:     +45 22684961

This is what it should all be used for, I think. This is spot-on what CDP is ALL about - but you have to ask each device what iy 'sees' around it, and then use that info. Like, ask device A & B above an you will get two lists where each contain an entry that should be like this: Device ID Local Intrfce Holdtme Capability Platform Port ID Device_B Gig 1/2 179 S I WS- C2950-2Gig 0/1 Device ID Local Intrfce Holdtme Capability Platform Port ID Device_A Gig 0/1 179 S I WS- C2950-2Gig 1/2 Matching these two lists received from each device will then tell us to inter-connect Device_A Gi1/2 with Device_B Gi0/1

smime.p7s
Description: S/MIME cryptographic signature