Hi,
AS you sure know "sh mac addr" reports mac addresses on Po interface, but "sh cdp neighb" reports neighbors on physical interfaces.
Although Port-channels are usually used on uplinks and mac addr reports should not be interesting on uplink ports, but they are also used on connections to ESXs and WLCs, and here the mac addr data is interesting.
How about adding NDs from Po members to Po interfaces themselves?
This can be added to the neighbor table by modifying updatenetdb.pl, or by modifying netdb.cgi.pl to extract the neighbor from Po member switches and showing it in WEB interface for the Po.
I think the first approach is more consistent and convenient.
Best Regards,
Hossein Badbanchi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've considered adding ND data to port-channels, but decided against it
because CDP/LLDP data doesn't actually correlate to port-channels. The
physical port information on each member port is best kept to the physical
interfaces since the data is different. One option might be to combine the
data from all port-channel members in to one Port-channel ND entry, but if
we were going to do that, I'd like to expand the port-channel information
all-together, such as showing which interfaces are bundled in the
port-channel.
Anyway, let me think about this some more but I stopped short of doing this
before because I couldn't decide how best to implement port-channels,
especially across vPC Nexus gear.
Jonathan
On Sat, May 23, 2015 at 8:37 AM, Hossein Badbanchi hbdbn@users.sf.net
wrote:
Hi,
AS you sure know "sh mac addr" reports mac addresses on Po interface, but
"sh cdp neighb" reports neighbors on physical interfaces.
Although Port-channels are usually used on uplinks and mac addr reports
should not be interesting on uplink ports, but they are also used on
connections to ESXs and WLCs, and here the mac addr data is interesting.
How about adding NDs from Po members to Po interfaces themselves?
This can be added to the neighbor table by modifying updatenetdb.pl, or
by modifying netdb.cgi.pl to extract the neighbor from Po member switches
and showing it in WEB interface for the Po.
I think the first approach is more consistent and convenient.
Hi,
AS you sure know "sh mac addr" reports mac addresses on Po interface, but "sh cdp neighb" reports neighbors on physical interfaces.
Although Port-channels are usually used on uplinks and mac addr reports should not be interesting on uplink ports, but they are also used on connections to ESXs and WLCs, and here the mac addr data is interesting.
How about adding NDs from Po members to Po interfaces themselves?
This can be added to the neighbor table by modifying updatenetdb.pl, or by modifying netdb.cgi.pl to extract the neighbor from Po member switches and showing it in WEB interface for the Po.
I think the first approach is more consistent and convenient.
Best Regards,
Hossein Badbanchi
Hey,
I've considered adding ND data to port-channels, but decided against it
because CDP/LLDP data doesn't actually correlate to port-channels. The
physical port information on each member port is best kept to the physical
interfaces since the data is different. One option might be to combine the
data from all port-channel members in to one Port-channel ND entry, but if
we were going to do that, I'd like to expand the port-channel information
all-together, such as showing which interfaces are bundled in the
port-channel.
Anyway, let me think about this some more but I stopped short of doing this
before because I couldn't decide how best to implement port-channels,
especially across vPC Nexus gear.
Jonathan
On Sat, May 23, 2015 at 8:37 AM, Hossein Badbanchi hbdbn@users.sf.net
wrote: