Switches, Hubs, and Modems
1752802 Members
5003 Online
108789 Solutions
New Discussion юеВ

Re: Vlans Cisco to 2824

 
Ron-O
New Member

Vlans Cisco to 2824

I'm trying to trunk a 2824 to a Cisco 4006 Chassis. I set the trunk lines but as soon as I plug the trunk line in I can no longer see the 2824...Here's the main parts of the configs...Port 1 will trunk to the cisco 4006 6/1.


Cisco
#module 6 : 48-port 10/100/1000 Ethernet
set trunk 6/1 on dot1q 1-1005,1025-4094
set trunk 6/2 on dot1q 1-1005,1025-4094
set trunk 6/3 on dot1q 1-1005,1025-4094
set trunk 6/4 on dot1q 1-1005,1025-4094
set spantree portfast 6/1-10 disable



HP
; J4903A Configuration Editor; Created on release #I.10.43

hostname "ProCurve Switch 2824"
web-management management-url ""
interface 1
no lacp
exit
interface 21
no lacp
exit
trunk 1,21 Trk1 Trunk
ip default-gateway xxx.xxx.xxx.xx
snmp-server community "public" Unrestricted snmp-server host 198.185.xxx.xxx "public"
snmp-server host 198.185.xxx.xxx "public"
vlan 1
name "DEFAULT_VLAN"
untagged 2-20,22-24,Trk1
ip address xxx.xxx.xxx.xxx 255.255.255.0
exit
vlan 3
name "internal"
tagged 2
exit
vlan 4
name "classrooms"
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity
high spanning-tree Trk1 priority 4
2 REPLIES 2
Christian Bor├йn
New Member

Re: Vlans Cisco to 2824

on HP Procurve devices you need to use tagged ports instead of trunking. Trunking in Procurve is used for load-sharing/bonding ports.

So if you want to use several vlan's on a port you set it up as tagged.

ie

vlan1
tagged 1
vlan2
tagged 1
vlan3
tagged 1

Regards,
Chris
Ron-O
New Member

Re: Vlans Cisco to 2824

That worked. Thanks.

ps. Also found out that you need to do it from the menu interface, not the web interface. For some reason the web interface shows they are tagged and the conf is correct even though they are not. Had to telnet into the switch, run menu, tag and untag then save. Then everythign was correct.