cmpwat Posted January 29, 2013 Posted January 29, 2013 Evening... now bear with me while I try and explain the problem! We have 2 HP ProCurve 2910al-48G switches (Sender for ease), connected via CX4 cable at the back. We are trying to connect the Sender switches to 2x HP ProCurve 2910al-24G switches (receiver) via a fibre cable. The fibre cable from the sender terminates in the comms rack. The receiver is connected to a fibre connection that terminates in the same comms rack. The 2 connections are connected with an ST to ST fibre patch cable. The idea is that we have one part of a SAN connected to the sender switches and one SAN on the receiver switches and create an iSCSI network over the fibre. I have created a vlan on the sender switches, vlan 10 and have ports 1-30 & 48 untagged. I have A1 (CX4) tagged and jumbo frames switched on. Port 48 has the SFP connected. This vlan is replicated to the second of the sender switches. I have also created a vlan on the receiver switches, again vlan 10 and have ports 1-22 & 24 untagged. I have A1 (CX4) tagged and jumbo frames switched on. Port 24 has the SFP connected. This vlan is also replicated to the second switch. It looks like the vlan is configured correctly but when we try and ping the SAN at the receiver end we get no reply. We have broken into the network at the comms cab with a PowerConnect 2824 and we can ping the SANs at both the sender and receiver ends but with the ST Patch connecting the 2 connections nothing seems to get through. The ST Patch cable is brand new (62.5/125). I have also tried another brand new patch cable (again 62.5/125) and nothing seems to be talking. Can anyone think of anything else we are missing here?
SchoolsBroadband Posted January 29, 2013 Posted January 29, 2013 Ummm this may seem way too simple but are both devices at each end in the same subnet mask? Dave
cmpwat Posted January 29, 2013 Author Posted January 29, 2013 Hi Dave Nope not a simple question at all! We have an ip of 192.168.130.230:255.255.255.0 on the sender and 192.168.130.231:255.255.255.0 on the receiver. I have attached the config of the switches below: Running configuration - Sender Switches ; J9147A Configuration Editor; Created on release #W.14.70 hostname "ProCurve 2910al-48G Switch" module 1 type J9147A module 2 type J9165A no stack ip default-gateway 10.107.71.254 vlan 1 name "DEFAULT_VLAN" untagged 47,A1 ip address 10.107.64.88 255.255.248.0 no untagged 1-46,48 exit vlan 10 name "iSCSI" untagged 1-30,48 ip address 192.168.130.231 255.255.255.0 tagged A1 jumbo exit vlan 50 name "vMotion" untagged 31-46 tagged A1 no ip address exit snmp-server community "public" unrestricted spanning-tree no autorun password manager Running configuration - Receiver Switches ; J9145A Configuration Editor; Created on release #W.14.49 hostname "SVS HP2910-24 iSCSI 2" module 1 type J9145A module 2 type J9165A ip default-gateway 10.107.71.254 vlan 1 name "DEFAULT_VLAN" untagged 23,A1 ip address 10.107.64.86 255.255.248.0 no untagged 1-22,24 exit vlan 10 name "iSCSI" untagged 1-22,24 ip address 192.168.130.230 255.255.255.0 tagged A1 jumbo exit snmp-server community "public" unrestricted snmp-server contact "Wayne Tuckwell" location "Science Prep" spanning-tree no autorun password manager Wayne
twin--turbo Posted January 30, 2013 Posted January 30, 2013 what device is "10.107.71.254" and does it have knowledge of the vlan10 and it's ip range. You should not need IP's on anything other than your router with the exception of the management address for the switch although I doubt it is the cause of the probelm. As always a diagram paints a thousand words. Also is Spanning treee enabled and is the bridge priority correctly set? Rob
cmpwat Posted January 30, 2013 Author Posted January 30, 2013 Hi Rob 10.107.71.254 is the default gateway of the entire network. Spanning Tree is enabled on all switches and Jumbo Frames is on all ports on the vlans. Bridge Priority? I don't know what this is? Wayne
cmpwat Posted January 30, 2013 Author Posted January 30, 2013 --UPDATE-- By removing the management cable from Port 47 on the sender, we now have the switches talking???? Considering Port 47 is in the default Vlan why would this be the case? We have also tried with the port connected and spanning tree off on both the sender and receiver and this also works? Confused now thought that vlans were meant to be apart?
twin--turbo Posted January 30, 2013 Posted January 30, 2013 As I say a diagram would be very helpful, I am also not familiar with the term "Sendre/Reciver" Switch? Rob
cmpwat Posted January 30, 2013 Author Posted January 30, 2013 Sorry Rob, Sender is server room a, receiver is server room b. Looks like a leaky vlan and spanning tree causing the issue.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now