Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco vs HP "trunk port"

Status
Not open for further replies.

m4rc00

Technical User
Sep 9, 2009
22
GB
Hi, i have some issue with cisco and hp switch.

Trying to configure trunk ports (tagged one).
On cisco i configured :

interface GigabitEthernet0/1
switchport trunk encapsulation dot1q
switchport mode trunk

on HP (HP ProCurve Switch 2424M):

Port DEFAULT_VLAN Wireless
A4 | Untagged Tagged


I do not see port Gig0/1 on cisco as trunk when i typed : sh int trunk

Do you have any idea why ? Whay im doing wrong ?

Thank you in advance
 
Yes i created a vlan on Cisco and its up, the same Gi0/1 is up :

Interface IP-Address OK? Method Status Protocol
Vlan1 10.16.2.8 YES NVRAM up up
Vlan30 10.16.4.1 YES NVRAM up up
GigabitEthernet0/1 unassigned YES unset up up

I strongly believe that fault is on HP side, but no idea how to solve this, especialy this switch does not have CLI, only menu mode

 
I vaguely remember the 2424s, and their menu mode is fine as long as what you want to configure exists in the menu. In this case, all you need is to configure the two VLANs as being on the interface, so you should be fine.

Can the switches see each other? I can't remember is 2424s had CDP on them or if that came later - check the HP website and get the latest firmnware you can for that switch and update it - you might get LLDP, if so, enable that on the Cisco.

Can you get a link up between the two switches: an access port in each VLAN patched to ports each in that VLAN untagged on the HP. Give the 2424 an IP address in each subnet in turn and check the switches will ping each other in both VLANs.

Then all you have to do is get both VLANs on the same physical link, which should be as simple as what you've already done. Maybe try to be more specific on the Cisco: add in a line specifying the native VLAN (actually, if it's 1, then it doesn't take, does it?) and another line to specifically allow the two VLANs. Maybe don't use VLAN1 and use two different VLANs, and have both of them tagged.

Sorry, I know I'd fiddle with this until I discovered what was wrong, but I can't really think of anything specific.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top