Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1006
  • Last Modified:

Catalyst 3560 to HP managed switch

I am trying to connect to an HP managed switch from my Cisco Catalyst 3560 but when I plug in to cable the light lights up and then dies. it shows under the interface: down, line protocol is down (notconnect)

Has anyone ever run into this issue before?
0
dufff
Asked:
dufff
1 Solution
 
that1guy15Commented:
Are you using a cross-over cable? For switch to switch connection you need a cross-over.
They also could be trying to negotiate a trunk link and failing. On the cisco set the link to either access or trunk interface
int f1/0
 switchport mode access
switchport mode trunk
0
 
Rick_O_ShayCommented:
Some switches can be configured to kill a port if another switch is detected on it by receiving its spanning tree packets. What does the config for your ports look like? Particularly spanning tree settings?
0
 
compbattyCommented:
My suggestion would be to try another cross-over cable or if possible another port on the 3560. It sounds to me like it could be a single pair inside the cable that hasn't quite been terminated correctly which would show the light come up but no traffic.

If this does not work if you can post the output of "show run int fa0/xx" and also "show spanning-tree" for the port that the HP is connected to.

Regards,
Doug
0
New Tabletop Appliances Blow Competitors Away!

WatchGuard’s new T15, T35 and T55 tabletop UTMs provide the highest-performing security inspection in their class, allowing users at small offices, home offices and distributed enterprises to experience blazing-fast Internet speeds without sacrificing enterprise-grade security.

 
CoreyMacCommented:
Depending on the age of the HP software in the switch there can be compatibility issues.  In the earlier firmware on some of the HP models they support Cisco CDP while in later versions this was removed.  

The newer HP firmware tends to work better and you can use the industry standard protocols.  Check to make sure you are configuring spanning tree and any trunking for the switches using the same protocols.  802.1s/w, 802.1q, etc...

Also note that there are certain configurations where an HP <-> switch link can melt a netowrk with redundant links if the configurations are not compatible.

Carefully read some of the interoperability documents like these and you find what applies to your configuration.  Things might just pop up and work, but if they do not or if they melt later, it would be useful to have a solid understanding of what you are working with and how it should behave....

http://www.hp.com/rnd/support/manuals/pdf/release_06628_07110/Bk2_Ch5_STP.pdf
http://www.tecnocael.it/ftp/docs/ProCurve_Cisco.pdf

It would also help if you would post the exact model numbers and software versions on the switches involved.  There are many models of 3560 and of HP Procurve switches.
0
 
that1guy15Commented:
Did this help solve your issue?
0
 
dufffAuthor Commented:
I had to disable spanning tree on the HP switch and it worked.
0
 
that1guy15Commented:
Interesting, Im glade you got it going.
0
 
dufffAuthor Commented:
thanks
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now