Cisco to HP CDP

We had two separate physical LANs, one HP, and one Cisco. Recently the two core switches were connected and we have traffic routing internally and out to the WAN. My issue is we have a third party network that will act as an auditing network; it connects through the firewall, into the Cisco core and can see and connect to anything within the Cisco network. Unfortunately, it can't connect to anything on the HP side. From doing some troubleshooting and research, I'm thinking it's because CDP doesn't recognize the other manufacturer (i.e. The Cisco core can see all connected Cisco devices, but not the HP core, and the HP core can see all connected HP devices but not the Cisco core). I know that CDP is Cisco proprietary and that LLDP is the non-Cisco equivalent, but it seems the Cisco 4503 won't support LLDP.
So, is there anyway to have the core switches recognize each other as switches, to hopefully help traffic from the third party network route from the Cisco core to the HP core and throughout the rest of the network?

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

networker050184

CDP will not stop traffic from routing. I think you have some deeper problems to look into here.

kryolla

flares2 what are you trying to accomplish with layer 2 and/or layer 3.

flares2

Ok, what I'm finding is that if I ping out to the third part network first, they can then connect to that machine, otherwise their connection times out. I'm thinking that because we have two "core" swithes, of different vendors no less, that mac-address-tables, routing tables, etc are getting stuck and/or delayed between the 4503 and the Procurve 4108.
I'm sorry if my questions sound unique and lack common sense, that's simply because our network is unique and lacks common sense. If only the 4503 had 8 spare fiber ports, all the distro switches could connect to it and I think this would all be alleviated.

networker050184

There is not really much help we can give you with out a better understanding of the set up and configs. Sounds like it could be something with IPSec tunnels.......

scheistermeister

flares2 wrote:

Ok, what I'm finding is that if I ping out to the third part network first, they can then connect to that machine, otherwise their connection times out.

That sounds like a reflexive ACL to me.

kryolla

Mac address tables are unique to the switch so thats not the problem
Routes not being exchanged what routing protocol are you using and are you checking how long the routes been in the routing table and are the neighbors flapping? Did you talk to your next level of support. How does this third party fit in your topology