Virtual Connect 4.85 and CDP Traffic passtrough

[HPalu]

good morning,

we do have an ESXi 6.7U3 Cluster running on HPE BL460c Gen8/9 in an C7000 chassis.

In VMWare the CDP status is populated, the System is connected to a Nexus fabric switch

In a second datacentre we have the same setup (ESXi 6.7U3, BL460c Gen9 in C7000 Chassis with VirtualConnect FW4.85). Systems are also connected to Nexus and CDP is enabled on the uplink ports (Inside VC i can see the connected ports on the Nexus)

But in VMware the CDP information is missing. For me it looks like the VC is not passing through the CDP information.

Does anyone have an idea where to look, any help is appreciated,

kind regards

[AmRa]

Cisco Discovery Protocol (CDP) is a Cisco proprietary protocol used to exchange device identity and capability information between two directly connected Cisco devices. CDP allows each Cisco device to display, for the administrator, a table showing the identity and capability of other directly connected Cisco devices. One of the primary uses of this information is for troubleshooting purposes. 
Virtual Connect does not support CDP. VC does support the industry standard protocol called Link Layer Discovery Protocol (LLDP) by default. LLDP is functionally equivalent to CDP, although the two protocols are not compatible. Many Cisco switches support LLDP. The global configuration command “lldp run” and the interface commands “lldp transmit” and “lldp receive” are used to enable LLDP on a Cisco switch that supports the protocol. The exec command “show lldp neighbors” displays LLDP neighbor information to the Cisco switch console. 
Virtual Connect provides the LLDP neighbor information for each VC uplink at the bottom of the statistics page for each port.

Please refer HP Virtual Connect for the Cisco Network Administrator guide (page number 44) for more information.

https://support.hpe.com/hpesc/public/docDisplay?cc=us&docId=emr_na-c01386629&lang=en-us

[HPalu]

good morning,

thank yo ufor your reply.

Unfortuanly this is a "basic" information i already gathered from the documentation.

I do not expect the VC to support CDP itself, but i was looking for something like passthrough the CDP information.

[code]

vim-cmd hostsvc/net/query_networkhint --pnic-name=vmnic0

(vim.host.PhysicalNic.NetworkHint) [
(vim.host.PhysicalNic.NetworkHint) {
device = "vmnic0",

.....

(vim.host.PhysicalNic.NetworkHint.IpNetwork) {
vlanId = 15,
ipSubnet = "10.15.57.64-10.15.57.95"
},
network = <unset>,
connectedSwitchPort = (vim.host.PhysicalNic.CdpInfo) {
cdpVersion = 2,
timeout = 60,
ttl = 126,
samples = 114878,
devId = "xxxxxxxxxxxxxxxx(SSI170405VK)",
address = "10.15.xxx.xxx",
portId = "Ethernet1/4",
deviceCapability = (vim.host.PhysicalNic.CdpDeviceCapability) {
router = false,
transparentBridge = false,
sourceRouteBridge = false,
networkSwitch = true,
host = false,
igmpEnabled = true,
repeater = false
},
softwareVersion = "Cisco Nexus Operating System (NX-OS) Software, Version 5.2(1)N1(4)",
hardwarePlatform = "N5K-C5548UP",
ipPrefix = "0.0.0.0",
ipPrefixLen = 0,
vlan = 1,
fullDuplex = true,
mtu = 1500,
systemName = "xxxxxxxxxxxx",
systemOID = "1.3.6.1.4.1.9.12.3.1.3.1084",
mgmtAddr = "1.1.1.1",
location = "xxxxxxxxxxxxxx"
},
lldpInfo = (vim.host.PhysicalNic.LldpInfo) null
}

....

and yes, the blade chassis is connected via VC.

kind regards