Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

Cisco 3750 & Pro-curve 1800-24G vlan issue

athlon_crazy
Occasional Visitor

Cisco 3750 & Pro-curve 1800-24G vlan issue

Firsly, please forgive me for my little knowledge on network part.

I connected cisco 3750 to pro-curve 1800-24G as below :

Cisco 0/15|vlan 10,11,12,13,14|untagged - gateway 168.171.1.254
Pro-curve 0/1| Traffic=ALL |PVID=1 - IP 168.171.1.236

Result:
Pro-curve -> ping -> cisco gateway = pingable
Pro-curve -> ping -> cisco | VLAN 10,11,12,13,14 = pingable
Server A (VLAN 10) > ping -> cisco (VLAN 10) = not pingable
Server A (168.171.1.114) | gateway=168.171.1.254 > ping -> cisco VLAN 10,11,12,13,14 = pingable

So, any server using vlan 10,11,12,13,14 cannot reach cisco except pro-curve. But if I change server ip same subnet as pro-curve (168.171.1.0/24) & using gateway 168.171.1.254, I can ping any VLAN 10,11,12,13,14

Hope someone can help me..

Thanks
2 REPLIES
bolli
Frequent Advisor

Re: Cisco 3750 & Pro-curve 1800-24G vlan issue

Hello
you must assign the Port 1 to the other VLANs.
At the moment the interface can only handle packets from VLAN 1.

Set the port to tagged member on any VLAN.

Regards
athlon_crazy
Occasional Visitor

Re: Cisco 3750 & Pro-curve 1800-24G vlan issue

Sorry, forgot to update! Yep, after I assigned pro-curve port 0/1 (which connecting to cisco) as VLAN member 10,11,12,13,14, all running fine now.

BTW, one more question. how can I connect 2x pro-curve to each other. Everytime I do bridge as per attachment, cisco block the port for spanning tree.

If possible, I want some connection go straight:
server A --> pro-curve --> server B
instead,
server A->pro-curve ->cisco->pro-curve-> server B

Thanks