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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VLAN traffic between Cisco 3650G and HP Procurve 2910l

Status
Not open for further replies.

fangerK

IS-IT--Management
Nov 24, 2010
3
US
I am having issues of trying to communicate with my 2 SAN network (which has 2 VLANS 172.16.1.x and 10.250.11.x)from my LAN network. My main switch is a Cisco 3650G. I have a HP Procurve 2910AL which is used for the 2 SAN network.

Physical connections cables are plugged into (Cisco LAN)interface GigabitEthernet 0/33 to (HP SAN) Interface 18

SAN A (172.16.1.x) is plugged into HP Interface 15 & 16
SAN B (10.250.11.x) is plugged into HP Interface 11 & 12

(Cisco)network is as follow:

interface GigabitEthernet0/33
description Access to SAN
switchport access vlan 3

interface Vlan3
ip address 172.16.1.1 255.255.0.0

interface Vlan4
ip address 10.250.11.1 255.255.0.0



HP Procurve network is as follow:

ip default-gateway 172.16.1.1
vlan 1
name "DEFAULT_VLAN"
untagged 1-24,A1
ip address 172.16.1.244 255.255.0.0
jumbo
exit

This configuration was working fine when I only had 1 SAN on my SAN network. I then brought in a 2nd SAN (ip address 10.250.11.x and connect it to my HP procurves and is now unable to communicate with the 2nd SAN from my workstation (LAN). I would like to keep the 2 SANs on seperate VLANS but would still like to have communication go accross these VLAN's as well as able to access it from the LAN side. Thanks and hope anyone can help.

 
Did you make any config change on HP 2910AL for the 2nd SAN? I mean did you add any VLAN
 
The only thing I did on the HP was created a VLAN 4 and gave it a name but I haven't done any tagging or untagging yet. here is whats on the HP:

vlan 4
name "HLB-DR1"
no ip address
exit
 
I would do this:

On the Cisco3560:
- interface 0/33: change to sw mode trunk, sw tr encap dot1q, sw tr vlan allow 1,3,4, sw nat vlan 1

On the HP 2910:
- int 18: change to VLAN 1 untagged, VLAN 3 tagged, VLAN 4 tagged
- int 15,16: change to VLAN 3 untagged
- int 11,12: change to VLAN 4 untagged
 
As Vince said , you have a single port going to the hp and its not trunked so you can't very well get to the other switches because only vlan 3 is being used on that connecting link . Follow Vinces instructions and you should be fine.
 
I am kind of confused for there isn't a VLAN 3 on my HP switch. The actual IP address of my HP switch is VLAN 3 on my cisco switch. Thanks.
 
It goes without saying that you will need to create all the relevant VLANs on each of the switches.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top